[
https://issues.apache.org/jira/browse/PHOENIX-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983404#comment-14983404
]
Alicia Ying Shu edited comment on PHOENIX-2351 at 10/30/15 9:54 PM:
--------------------------------------------------------------------
[~maryannxue] Out of curiosity, having alias/tableName with column name as its
name will avoid name conflict. Restored previous behavior before PHOENIX-1560
should not affect existing functions. Using xml output is an existing behavior
and function, what is the reason to change it? It is a regression.
was (Author: aliciashu):
[~maryannxue] Out of curiosity, having alias/tableName with column name as its
name will avoid name conflict. Restored previous behavior before PHOENIX-1560
should not affect existing functions. Using xml output is an existing behavior
and function, what is the reason to change it?
> Phoenix query table alias name is not coming the output xml file
> ----------------------------------------------------------------
>
> Key: PHOENIX-2351
> URL: https://issues.apache.org/jira/browse/PHOENIX-2351
> Project: Phoenix
> Issue Type: Bug
> Reporter: Alicia Ying Shu
> Assignee: Alicia Ying Shu
> Attachments: PHOENIX-2351.patch
>
>
> Phoenix query table alias name is not coming the output xml file.
> From sqlline:
> !outputformat xmlattr
> SELECT /*+ SORTED_MERGE_JOIN */ * FROM LARGE_TABLE AS L INNER JOIN
> GIGANTIC_TABLE AS G ON L.UNSIG_ID=G.BIG_ID LIMIT 10000;
> When alias name is used in the query (in this example, table alias name is
> “L”) then the expected xml output need to have the alias name,
> Current output:
> <resultset>
> <result ID="0" UNSIG_ID="0" BIG_ID="0" UNSIG_LONG_ID="0" ...
> ......
> Expected output:
> <resultset>
> <result L.ID="0" UNSIG_ID="0" G.BIG_ID="0" UNSIG_LONG_ID="0" ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
