[
https://issues.apache.org/jira/browse/PHOENIX-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606228#comment-16606228
]
Hudson commented on PHOENIX-4882:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1922 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1922/])
PHOENIX-4882 The client re-resolves the table for every projected (larsh: rev
48787d06aa5d8586f4bdf17b99bff4443e2e7196)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/FromCompiler.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/schema/LocalIndexDataColumnRef.java
> The client re-resolves the table for every projected non-indexed column when
> there's a local index.
> ---------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4882
> URL: https://issues.apache.org/jira/browse/PHOENIX-4882
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.14.0
> Reporter: Lars Hofhansl
> Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4882-partial-quick-fix.txt, stacks.txt
>
>
> See TupleProjectionCompiler.ColumnRefVisitor.
> Each non-projected column causes a server roundtrip in
> LocalIndexDataColumnRef.
> For wide tables that can be hundreds of time.
> I generally find that the same table is resolved over and over again for
> other reasons as well (I counted 15-25 times during query compilation!!)
> Put a break point in ConnectionQueryServicesImpl.getTable and you'll see.
> [~tdsilva]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
