mirror of
https://github.com/apache/impala.git
synced 2026-01-24 15:00:45 -05:00
a007e3caf8
When a runtime filter has remote target, coordinator will Disable the FilterState upon arrival of the last filter update to prevent another update towards that filter. As consequence, such runtime filter will always be displayed as disabled in runtime profile (Enabled column is equal to false in Final filter table), when in reality the runtime filter has heard back from all pending backends and complete. The Enabled column should correctly distinguish between failed runtime filter vs complete runtime filter. To do so, we add all_updates_received_ flag in FilterState class and set it to true after filter received enough filter update from pending backends to proceed. If all_updates_received_ is true, then that runtime filter is considered as enabled. Testing: - Add row regex in runtime_filters.test, query 6, to verify REMOTE runtime filter is marked as enabled in final filter table - Run and pass test_runtime_filters.py - Run and pass core tests Change-Id: I82a5a776103abd0a6d73336bebc65e22b4e13fef Reviewed-on: http://gerrit.cloudera.org:8080/15308 Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
This directory contains Impala test workloads. The directory layout for the workloads should follow: workloads/ <data set name>/<data set name>_dimensions.csv <- The test dimension file <data set name>/<data set name>_core.csv <- A test vector file <data set name>/<data set name>_pairwise.csv <data set name>/<data set name>_exhaustive.csv <data set name>/queries/<query test>.test <- The queries for this workload