[
https://issues.apache.org/jira/browse/PHOENIX-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby resolved PHOENIX-5682.
--------------------------------------
Fix Version/s: (was: 4.17.0)
(was: 5.2.0)
(was: 4.16.2)
Resolution: Won't Do
We use the rewritten index row causing all timestamps to match as a useful
property.
> IndexTool can just update empty_column with verified if rest of index row
> matches
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-5682
> URL: https://issues.apache.org/jira/browse/PHOENIX-5682
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.15.1, 4.14.3
> Reporter: Priyank Porwal
> Priority: Minor
>
> When upgrading from old indexing design to new consistent indexing,
> IndexUpgradeTool kicks off IndexTool to rebuild the index. This index rebuild
> rewrites all index rows. If any index row was already consistent, it is
> rewritten + empty_column is updated with verified flag.
> IndexTool could potentially just update empty_column if rest of the index row
> matches with data rows. This would save the massive writes to the underlying
> dfs, as well as other side effects of these writes to replication.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
