[
https://issues.apache.org/jira/browse/PHOENIX-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016464#comment-17016464
]
Hudson commented on PHOENIX-5674:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #651 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/651/])
PHOENIX-5674 IndexTool to not write already correct index rows/CFs (kadir: rev
1cccd89fe36e05e08ca2b5058f4d46373c69b327)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/IndexRebuildRegionScanner.java
> IndexTool to not write already correct index rows
> -------------------------------------------------
>
> Key: PHOENIX-5674
> URL: https://issues.apache.org/jira/browse/PHOENIX-5674
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.15.1, 4.14.3
> Reporter: Priyank Porwal
> Assignee: Kadir OZDEMIR
> Priority: Major
> Fix For: 4.15.1, 4.14.4
>
> Attachments: PHOENIX-5674.4.x-HBase-1.5.001.patch,
> PHOENIX-5674.4.x-HBase-1.5.002.patch, PHOENIX-5674.master.001.patch,
> PHOENIX-5674.master.002.patch, PHOENIX-5674.master.003.patch
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> IndexTool can avoid writing index rows if they are already consistent with
> data-table. This will specially be useful when rebuilding index on DR-site
> where indexes are replicated already, but rebuild might be needed for catchup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
