[jira] [Work logged] (HIVE-26761) Add "-- SORT_QUERY_RESULTS" to complex_alias.q

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-26761?focusedWorklogId=827107&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-827107 ]

ASF GitHub Bot logged work on HIVE-26761:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Nov/22 09:46
            Start Date: 18/Nov/22 09:46
    Worklog Time Spent: 10m 
      Work Description: csebal-at-cloudera opened a new pull request, #3783:
URL: https://github.com/apache/hive/pull/3783

   Change-Id: I6d4f5393bd789427f23ea58de98f4a9703a79360
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   Adding a SORT_QUERY_RESULTS command at the beginning of the complex_alias.q test script to make its results deterministic.
   
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   Without the sort command the results of the query are non-deterministic and can occasionally lead to failed tests.
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description, screenshot and/or a reproducable example to show the behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to the released Hive versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   No
   
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
   If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why it was difficult to add.
   -->
   Executed locally




Issue Time Tracking
-------------------

            Worklog Id:     (was: 827107)
    Remaining Estimate: 0h
            Time Spent: 10m

> Add "-- SORT_QUERY_RESULTS" to complex_alias.q
> ----------------------------------------------
>
>                 Key: HIVE-26761
>                 URL: https://issues.apache.org/jira/browse/HIVE-26761
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Balázs Cseh
>            Assignee: Balázs Cseh
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Without sorting the order in which results are returned is non-deterministic.
> In most runs, it is:
> {code:java}
> 42    42
> 41    41 {code}
> however in some cases it comes back as:
> {code:java}
> 41    41
> 42    42 {code}
> Adding "– SORT_QUERY_RESULTS" eliminates this potential inconsistency.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)