[
https://issues.apache.org/jira/browse/PHOENIX-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir Ozdemir updated PHOENIX-7426:
-----------------------------------
Parent: PHOENIX-7562
Issue Type: Sub-task (was: Improvement)
> Generating index mutations for immutable tables on the server side
> ------------------------------------------------------------------
>
> Key: PHOENIX-7426
> URL: https://issues.apache.org/jira/browse/PHOENIX-7426
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Kadir Ozdemir
> Priority: Major
>
> Index mutations for immutable tables are currently generated on the client
> side. This was done to improve the performance of global indexes for
> immutable tables as the consistency model, failure detection, and recovery
> were done differently for mutable and immutable tables. However, after
> redesigning global indexes, this performance optimization is not significant
> anymore as these differences are not there anymore.
> Having client vs server side indexes does not provide any benefit anymore but
> this separation creates implementation challenges. Please also note that
> immutability of a table in Phoenix is not enforced. In other words, one can
> still overwrite a row of an immutable table.
> This Jira is to unify the code for immutable and mutable indexes. Because of
> the backward compatibility concern, we will keep the client side index
> implementation but deprecate it. A new config will be introduced to enable
> server side immutable indexes. By default, server side immutable indexes will
> be disabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
