[
https://issues.apache.org/jira/browse/PHOENIX-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599256#comment-16599256
]
Lars Hofhansl commented on PHOENIX-4882:
----------------------------------------
It seems, too, that we should be able to resolve a table only once per
query-compilation, and then reuse that instance (or at least the resolve
timestamp), so it won't get re-resolved.
> 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
>
> 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)
