You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Kadir OZDEMIR (Jira)" <ji...@apache.org> on 2020/01/14 23:50:00 UTC

[jira] [Updated] (PHOENIX-5674) IndexTool to not write already correct index rows/CFs

     [ https://issues.apache.org/jira/browse/PHOENIX-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kadir OZDEMIR updated PHOENIX-5674:
-----------------------------------
    Attachment: PHOENIX-5674.master.001.patch

> IndexTool to not write already correct index rows/CFs
> -----------------------------------------------------
>
>                 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.master.001.patch
>
>
> 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.
> Likewise, during upgrades from old indexing scheme to new consistent indexing scheme, if the index data columns are consistent already, IndexTool should only rewrite the EmptyColumn to mark the row as verified instead of writing the data columns too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)