[
https://issues.apache.org/jira/browse/PHOENIX-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604746#comment-16604746
]
Rajeshbabu Chintaguntla edited comment on PHOENIX-4882 at 9/5/18 6:14 PM:
--------------------------------------------------------------------------
[~lhofhansl] +1 on the fix. Still we can also directly get the data table
reference from meta data cache.
was (Author: rajeshbabu):
[~lhofhansl] May be we can directly get the table reference from meta data
cache.
> 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
> Reporter: Lars Hofhansl
> Priority: Major
> 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)
