kasakrisz opened a new pull request, #3155:
URL: https://github.com/apache/hive/pull/3155
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA:
https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
Partially restore the way Project operator's output row resolver is created
before [HIVE-16924](https://issues.apache.org/jira/browse/HIVE-16924) :
When creating the output row resolver schema of the Project operator of a
`select distinct` query append the column information from the input row
resolver.
### Why are the changes needed?
If some column references in the select distinct clause of the query has
alias defined only the alias of the column can be used to reference it in the
Project output RR. However common db engines enables both the column name and
alias in the Order by clause.
In case of a `select distinct` query the input RR of the Project is an
Aggregate which output RR contains only the projected expressions. It is safe
to use these in the order by clause too.
### Does this PR introduce _any_ user-facing change?
Yes, Both column name and alias can be used in the order by clause of
`select distinct` queries.
### How was this patch tested?
```
mvn test -DskipSparkTests -Dtest=TestMiniLlapLocalCliDriver
-Dqfile=distinct_col.q -pl itests/qtest -Dmaven.surefire.debug -Pitests
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
