phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4882) The client re-resolves the table for every projected non-indexed column when there's a local index.
Date Thu, 06 Sep 2018 18:32:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars Hofhansl updated PHOENIX-4882:
-----------------------------------
    Fix Version/s: 5.1.0

> 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, 5.1.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)

Mime
View raw message