[
https://issues.apache.org/jira/browse/PHOENIX-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410959#comment-17410959
]
ASF GitHub Bot commented on PHOENIX-6365:
-----------------------------------------
stoty commented on pull request #1133:
URL: https://github.com/apache/phoenix/pull/1133#issuecomment-914045838
Some more analysis on possible alternative ways to solve this problem:
(I think that the current patch is still correct, if not the most elegant
way to do it)
The pre-patch resolver will always (at least in every case in the tests)
will (incorrectly) include the data table, and will return the ProjectedColumn
object that was generated when projecting the table.
With the current patch, the resolver will not consider the data table in
some cases, and the Column object will be re-generated by ColumnRef, and will
be a straight PColumnImpl instance.
--
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]
> Bogus AmbiguousTableException in query with aliases on local indexed tables
> ---------------------------------------------------------------------------
>
> Key: PHOENIX-6365
> URL: https://issues.apache.org/jira/browse/PHOENIX-6365
> Project: Phoenix
> Issue Type: Task
> Components: core
> Affects Versions: 5.1.0, 4.16.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> Certain queries with aliases on tbales with local indexes throw
> AmbiguousTableException
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
