[
https://issues.apache.org/jira/browse/PHOENIX-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486148#comment-14486148
]
Maryann Xue commented on PHOENIX-1749:
--------------------------------------
[~jamestaylor], I agree with you that the easiest (and the best I think) way is
to get the ParseNode right from the "SELECT" node list. And that would require
least changes to the existing code.
But I am thinking to expand wildcard beforehand (maybe in StatementNormalizer)
instead. This would benefit and simplify some other issues as well. For
example, with index column replacement, we could remove methods like
projectAllIndexTableColumns() and projectAllIndexFamilyColumns(). And we would
be able to support wildcard in derived table (currently we don't know the
column names until we start to compile the query). We still need to keep the
wildcard information somewhere though in order to project the entire family (or
all families) in HBase Scan.
What do you think? Shall we file a different JIRA for this?
> ORDER BY should support ordinal position as well as expression
> --------------------------------------------------------------
>
> Key: PHOENIX-1749
> URL: https://issues.apache.org/jira/browse/PHOENIX-1749
> Project: Phoenix
> Issue Type: Bug
> Reporter: Serhiy Bilousov
> Assignee: Alicia Ying Shu
> Attachments: PHOENIX-1749-v1.patch, PHOENIX-1749.patch,
> Phoenix-1749-v2.patch
>
>
> In postgreSQL (and many others DBs) you can specify not only column name for
> the ORDER BY but column number (position in SELECT part) as well as column
> alias.
> see:
> http://www.postgresql.org/docs/9.4/static/queries-order.html
> http://www.postgresql.org/docs/9.4/static/sql-select.html#SQL-GROUPBY
> Adding such support would be very helpful and sometimes necessary.
> I can provide real queries example if required but basically we want
> something like this
> given query
> SELECT a, b, TRUNC(current_date(),'HOUR') AS date_truncated FROM table
> we want
> ORDER BY 1 ASC, 2 DESC
> ORDER BY date_truncated
> Having just column number would cover both but having column alias would make
> queries more readable and human friendly. Plus make it one little stem closer
> to postgreSQL and SQL standard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
