Github user chrajeshbabu commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/3#discussion_r14898287
--- 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 --
bq. why do we need this to be different for local indexes? Seems like we
could run parallel scans over part of each region just like we do with other
scans, no?
Index table rows have region start key as prefix so even if we split region
key ranges into multiple and scan parallelly,only first scanner gives the
results and remaining all the scanners just return nothing. So number of splits
of local index region setting to 1.
if we want to start multiple scanners for local index into multiple parts
then we need to split the scan ranges into multiple.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
