[
https://issues.apache.org/jira/browse/HIVE-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666114#comment-13666114
]
Sebastian commented on HIVE-4598:
---------------------------------
Another odd result in context of subqueries/views I assume is related:
> SELECT max(daily_signups) FROM temp_aggrusers
result = 2
temp_aggrusers is a view
> CREATE TABLE temp_aggrusers_mat AS SELECT * FROM temp_aggrusers
> SELECT max(daily_signups) FROM temp_aggrusers_mat
result = 1200
Needless to say 1200 is the correct result.
The table has 113000 entries, I haven't been able to reproduce this with a
minimal sample.
Is there something I'm missing or is this a massive bug?
> Incorrect results when using subquery in multi table insert
> -----------------------------------------------------------
>
> Key: HIVE-4598
> URL: https://issues.apache.org/jira/browse/HIVE-4598
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.10.0, 0.11.0
> Reporter: Sebastian
>
> I'm using a multi table insert like this:
> FROM <x>
> INSERT INTO TABLE t PARTITION (type='x')
> SELECT * WHERE type='x'
> INSERT INTO TABLE t PARTITION (type='y')
> SELECT * WHERE type='y';
> Now when <x> is the name of a table, everything works as expected.
> However if I use a subquery as <x>, the query runs but it inserts all results
> from the subquery into each partition, as if there were no "WHERE" clauses in
> the selects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
