[ https://issues.apache.org/jira/browse/PHOENIX-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049784#comment-16049784 ]
James Taylor commented on PHOENIX-3941: --------------------------------------- FYI, [~lhofhansl] & [~rajeshbabu] - I think this will ofthen help prevent large numbers of RPCs over big tables that use local indexes. > Filter regions to scan for local indexes based on data table leading pk > filter conditions > ----------------------------------------------------------------------------------------- > > Key: PHOENIX-3941 > URL: https://issues.apache.org/jira/browse/PHOENIX-3941 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > Labels: SFDC, localIndex > Fix For: 4.12.0 > > > Had a good offline conversation with [~ndimiduk] at PhoenixCon about local > indexes. Depending on the query, we can often times prune the regions we need > to scan over based on the where conditions against the data table pk. For > example, with a multi-tenant table, we only need to scan the regions that are > prefixed by the tenant ID. > We can easily get this information from the compilation of the query against > the data table (which we always do), through the > statementContext.getScanRanges() structure. We'd just want to keep a pointer > to the data table QueryPlan from the local index QueryPlan. -- This message was sent by Atlassian JIRA (v6.4.14#64029)