[
https://issues.apache.org/jira/browse/HIVE-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972443#comment-15972443
]
Matt McCline commented on HIVE-16467:
-------------------------------------
I think the rule of thumb is if the query has a LIMIT clause you need to add an
ORDER BY clause so the correct N rows are chosen. Otherwise, adding
SORT_QUERY_RESULTS should do the trick.
> Flaky test: TestCliDriver.testCliDriver[vector_order_null]
> ----------------------------------------------------------
>
> Key: HIVE-16467
> URL: https://issues.apache.org/jira/browse/HIVE-16467
> Project: Hive
> Issue Type: Sub-task
> Reporter: Peter Vary
>
> Seems to me, that we have to add a {{-- SORT_QUERY_RESULTS}} to the query
> test.
> The error message is
> {code}
> Client Execution succeeded but contained differences (error code = 1) after
> executing vector_order_null.q
> 153a154
> > 2 B
> 156d156
> < 2 B
> 247a248
> > 2 B
> 250d250
> < 2 B
> 531a532
> > 2 B
> 534d534
> < 2 B
> 626a627
> > 2 B
> 629d629
> < 2 B
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
