[
https://issues.apache.org/jira/browse/HIVE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remus Rusanu updated HIVE-5817:
-------------------------------
Attachment: HIVE-5817.5.patch
This patch fixes the regression with vectorization_part_project.q
I added vectorized_context_regression_5817.q but I'm unable to create an
expected .out file because mvn test fails on my Windows enlistment:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hive.cli.TestCliDriver
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 32.067 sec <<<
FAILURE! - in org.apache.hadoop.hive.cli.TestCliDriver
initializationError(org.apache.hadoop.hive.cli.TestCliDriver) Time elapsed:
0.006 sec <<< FAILURE!
java.lang.AssertionError: null
at
org.apache.hadoop.hive.ql.QTestUtil.getHdfsUriString(QTestUtil.java:288)
at
org.apache.hadoop.hive.ql.QTestUtil.convertPathsFromWindowsToHdfs(QTestUtil.java:276)
at org.apache.hadoop.hive.ql.QTestUtil.initConf(QTestUtil.java:233)
at org.apache.hadoop.hive.ql.QTestUtil.<init>(QTestUtil.java:317)
at
org.apache.hadoop.hive.cli.TestCliDriver.<clinit>(TestCliDriver.java:39)
> column name to index mapping in VectorizationContext is broken
> --------------------------------------------------------------
>
> Key: HIVE-5817
> URL: https://issues.apache.org/jira/browse/HIVE-5817
> Project: Hive
> Issue Type: Bug
> Components: Vectorization
> Reporter: Sergey Shelukhin
> Assignee: Remus Rusanu
> Priority: Critical
> Attachments: HIVE-5817-uniquecols.broken.patch,
> HIVE-5817.00-broken.patch, HIVE-5817.4.patch, HIVE-5817.5.patch
>
>
> Columns coming from different operators may have the same internal names
> ("_colNN"). There exists a query in the form {{select b.cb, a.ca from a JOIN
> b ON ... JOIN x ON ...;}} (distilled from a more complex query), which runs
> ok w/o vectorization. With vectorization, it will run ok for most ca, but for
> some ca it will fail (or can probably return incorrect results). That is
> because when building column-to-VRG-index map in VectorizationContext,
> internal column name for ca that the first map join operator adds to the
> mapping may be the same as internal name for cb that the 2nd one tries to
> add. 2nd VMJ doesn't add it (see code in ctor), and when it's time for it to
> output stuff, it retrieves wrong index from the map by name, and then wrong
> vector from VRG.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
