[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332951#comment-16332951
 ] 

ASF subversion and git services commented on ASTERIXDB-2248:
------------------------------------------------------------

Commit 83695b932440628a58148f2551b776503f55c5d3 in asterixdb's branch 
refs/heads/master from [~dlychagin-cb]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=83695b9 ]

[ASTERIXDB-2248][SQLPP] Disallow use of column aliases in GBY/HAVING

- user model changes: yes
- storage format changes: no
- interface changes: no

Details:
- Column aliases defined by SELECT clause should not be referenceable
  from GROUP BY/HAVING clauses because aliases are not variables.
  References from ORDER BY clause are still allowed.

Change-Id: Ieb734f87904e6bf307a04b2328a2fd109151f70f
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2294
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Till Westmann <[email protected]>
Contrib: Till Westmann <[email protected]>


> SQPP: Disallow the use of column aliases in GROUP BY/HAVING clauses 
> --------------------------------------------------------------------
>
>                 Key: ASTERIXDB-2248
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2248
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: SQL - Translator SQL++
>            Reporter: Dmitry Lychagin
>            Assignee: Dmitry Lychagin
>            Priority: Minor
>
> Column aliases introduced by SELECT clause (AS ...) are not variables and 
> therefore should not be referenceable from clauses that are logically 
> processed before SELECT (such as GROUP BY and HAVING). We still allow column 
> aliases to be referenced from ORDER BY clauses.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to