mirror of
https://github.com/apache/impala.git
synced 2026-01-07 18:02:33 -05:00
06c96e4074
IMPALA-2349: The bug was that we were not adding the parent tuple ids of a relative or correlated table ref to the list of required tuple ids if that table ref itself depended on a relative table ref (nested subplans). This patch simplifies and fixes the planning with straight_join. The required tuple ids are properly set, and the ordering requirement is enforced by adding the last parent table ref's id to the list of required table ref ids. IMPALA-2412: The bug was that we were relying on both the required materialized tuple ids as well as the table ref ids to determine whether a table ref belongs into a subplan at a certain level. However, as the existing comments in the code actually already state, the subplan placement should be determined only based on whether the required parent tuple ids are materilaized. The correct join/subplan ordering is independent, and is handled by the required table ref ids. Change-Id: I922fcbd0039242bf5940534d667926cdbdf72946 Reviewed-on: http://gerrit.cloudera.org:8080/907 Reviewed-by: Alex Behm <alex.behm@cloudera.com> Tested-by: Internal Jenkins
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