[
https://issues.apache.org/jira/browse/PHOENIX-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758455#comment-17758455
]
Aron Attila Meszaros commented on PHOENIX-6920:
-----------------------------------------------
While debugging found that this is not a PQS bug but can be reproduced with the
thick client too, and older versions are also affected
> PQS / thin client doesn't distinguish between label and column_name
> -------------------------------------------------------------------
>
> Key: PHOENIX-6920
> URL: https://issues.apache.org/jira/browse/PHOENIX-6920
> Project: Phoenix
> Issue Type: Bug
> Components: queryserver
> Reporter: Istvan Toth
> Assignee: Aron Attila Meszaros
> Priority: Major
>
> While debugging PHOENIX-6917, I found that we receive the aliased column name
> in both the _column_name_ and _label_ fields of the column metadata in
> protobuf.
> This happened with PQS head and Phoenix 5.2.0-SNAPSHOT.
> Apparently, some older version used to work correctly (and returned the
> unaliased name in {_}column_name{_})
> We need to check if this is a Phoenix or Avatica regression first, then fix
> it in the appropriate project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
