[
https://issues.apache.org/jira/browse/PHOENIX-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173134#comment-14173134
]
Hudson commented on PHOENIX-1149:
---------------------------------
SUCCESS: Integrated in Phoenix | 3.0 | Hadoop1 #259 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/259/])
Backport fixes for PHOENIX-1149 (view index ignored if no where clause) and
PHOENIX-933 (IndexMaintainer fixes for view index) (jtaylor: rev
abffd3fc7614ca70e040cdc4c752ee90e4b3b270)
* phoenix-core/src/main/java/org/apache/phoenix/index/IndexMaintainer.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/WhereOptimizer.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/BaseViewIT.java
> Index mutations should be committed as batches while building local index
> -------------------------------------------------------------------------
>
> Key: PHOENIX-1149
> URL: https://issues.apache.org/jira/browse/PHOENIX-1149
> Project: Phoenix
> Issue Type: Bug
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Fix For: 5.0.0, 4.1
>
> Attachments: PHOENIX-1149.patch
>
>
> Currently while building local indexes batchSize is 0 so we are not
> committing the index mutations until full region scan is done and which may
> cause high memory usage or OOM with huge data.
> {code}
> // Commit in batches based on
> UPSERT_BATCH_SIZE_ATTRIB in config
> if (!indexMutations.isEmpty() && batchSize > 0 &&
> indexMutations.size() % batchSize == 0) {
> HRegion indexRegion =
> getIndexRegion(c.getEnvironment());
> // Get indexRegion corresponding to data region
> commitBatch(indexRegion, indexMutations, null);
> indexMutations.clear();
> }
> {code}
> Thanks for finding this [~mujtabachohan].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
