[
https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556096#comment-15556096
]
Hudson commented on PHOENIX-3363:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1433 (See
[https://builds.apache.org/job/Phoenix-master/1433/])
PHOENIX-3363 Join-related IT had problematic usage of generating new
(maryannxue: rev ad99952792b8b119085499d8d0d734c3d2dc053b)
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/SortMergeJoinIT.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/SubqueryIT.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/SubqueryUsingSortMergeJoinIT.java
> 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)
