[ 
https://issues.apache.org/jira/browse/HIVE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phabricator updated HIVE-3923:
------------------------------

    Attachment: HIVE-3923.D8079.1.patch

khorgath requested code review of "HIVE-3923 [jira] join_filters_overlap.q 
fails on 0.23".
Reviewers: JIRA

  Adding order-by to tests to fix 0.23 test breakage

  As with some of the other broken tests on 0.23, this is broken because the 
order of results generated by the query on 0.23 is different from the order in 
the golden output file. However, there appears to be nothing wrong with the 
query itself.

  This can be fixed by adding an order-by clause and regenerating the golden 
file.

TEST PLAN
  Patch attached is a test fix

REVISION DETAIL
  https://reviews.facebook.net/D8079

AFFECTED FILES
  ql/src/test/queries/clientpositive/join_filters_overlap.q
  ql/src/test/results/clientpositive/join_filters_overlap.q.out

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/19485/

To: JIRA, khorgath

                
> join_filters_overlap.q fails on 0.23
> ------------------------------------
>
>                 Key: HIVE-3923
>                 URL: https://issues.apache.org/jira/browse/HIVE-3923
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>         Environment: Hadoop 0.23
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>            Priority: Minor
>         Attachments: HIVE-3923.D8079.1.patch
>
>
> As with some of the other broken tests on 0.23, this is broken because the 
> order of results generated by the query on 0.23 is different from the order 
> in the golden output file. However, there appears to be nothing wrong with 
> the query itself.
> This can be fixed by adding an order-by clause and regenerating the golden 
> file.

--
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

Reply via email to