[
https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555937#comment-15555937
]
James Taylor commented on PHOENIX-3363:
---------------------------------------
Because of the way the tests are designed, we have a "virtual table name" which
gets replaced by the actual table name (which is created if it doesn't already
exist). We have a map behind the scenes which caches this information.
> Join-related IT had problematic usage of generating new table names
> -------------------------------------------------------------------
>
> Key: PHOENIX-3363
> URL: https://issues.apache.org/jira/browse/PHOENIX-3363
> Project: Phoenix
> Issue Type: Bug
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Priority: Minor
> Fix For: 4.9.0
>
>
> If there are multiple references of the same table, we should only call
> method "getTable()" once for each query or each test case. HashJoinIT.java
> did the right thing while other join-related IT tests did not.
> This was covered by a bug in column resolving. We shouldn't be able to
> resolve a table reference if that table is not mentioned in the from clause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
