[ https://issues.apache.org/jira/browse/PHOENIX-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061127#comment-14061127 ]
ASF GitHub Bot commented on PHOENIX-933: ---------------------------------------- Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/3#discussion_r14899559 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/DefaultParallelIteratorRegionSplitter.java --- @@ -140,7 +142,14 @@ public boolean apply(HRegionLocation location) { // distributed across regions, using this scheme compensates for regions that // have more rows than others, by applying tighter splits and therefore spawning // off more scans over the overloaded regions. - int splitsPerRegion = regions.size() >= targetConcurrency ? 1 : (regions.size() > targetConcurrency / 2 ? maxConcurrency : targetConcurrency) / regions.size(); + PTable table = tableRef.getTable(); --- End diff -- That's what the splitsPerRegion variable and subsequent logic in ParallelIterators does - it creates additional split points within the range so that multiple scans get run over a single region. We'd want to prefix each of these with the same start region key. I'll open a separate JIRA for this too. It's not a big deal - most of the time the parallelization slots would be used up by having to do a scan in each region anyway. > Local index support to Phoenix > ------------------------------ > > Key: PHOENIX-933 > URL: https://issues.apache.org/jira/browse/PHOENIX-933 > Project: Phoenix > Issue Type: New Feature > Reporter: rajeshbabu > > Hindex(https://github.com/Huawei-Hadoop/hindex) provides local indexing > support to HBase. It stores region level index in a separate table, and > co-locates the user and index table regions with a custom load balancer. > See http://goo.gl/phkhwC and http://goo.gl/EswlxC for more information. > This JIRA addresses the local indexing solution integration to phoenix. -- This message was sent by Atlassian JIRA (v6.2#6252)