Bulk Operation

IMPALA-9124 Consider using num_rows_fetched instead of fetched_rows in checking whether client has fetched any results in TryQueryRetry

IMPALA-9124 Hit DCHECK when retrying a query in FINISHED state

IMPALA-9124 Impala Doc: Add docs for transparent query retries

IMPALA-9124 Profile log does not include profiles of failed queries

IMPALA-9124 summary and profile command in impala-shell should show both original and retried info

IMPALA-9124 TSAN lock-order-inversion warning in QueryDriver::RetryQueryFromThread

IMPALA-9124 TSAN data race in QueryDriver::CreateRetriedClientRequestState

IMPALA-9124 Fix error reporting when AuxErrorInfoPB is present without an error

IMPALA-9124 ACID-query retry integration

IMPALA-9124 Test that queries are not retried if they cause an impalad to crash

IMPALA-9124 Retried queries that blacklist nodes should ensure they don't run on the blacklisted node

IMPALA-9124 Query progress bar freezes when a query is retried

IMPALA-9124 Avoid copying TExecRequest when retrying queries

IMPALA-9124 Re-factor ImpalaServer, ClientRequestState, Coordinator protocol

IMPALA-9124 Web UI improvements for retried queries

IMPALA-9124 Queries should only be retried if all fragments fail with retryable errors

IMPALA-9124 Add impalad level metrics for query retries

IMPALA-9124 Retried runtime profile should include some information about previous query attempts

IMPALA-9124 Link failed and retried runtime profiles

IMPALA-9124 Test coverage for query retries when there is a network partition

IMPALA-9124 Retryable queries should spool all results before returning any to the client

IMPALA-9124 Client logs should indicate if a query has been retried

IMPALA-9124 Add support for multi query retries on cluster membership changes

IMPALA-9124 Add support for single query retries on cluster membership changes

IMPALA-9124 Classify certain errors as retryable