[
https://issues.apache.org/jira/browse/PHOENIX-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117191#comment-17117191
]
Kadir OZDEMIR commented on PHOENIX-5923:
----------------------------------------
[~gjacoby], It does not. IndexScrutiny is a client tool and works at the SQL
level so the storage scheme is not visible to it. IndexTool verification is
done using the HBase client API. However, the way it is implemented should not
require any significant change; at this moment, I cannot think of any change
there but I will not be surprised if there will be some change. This is because
the verification algorithm regenerates the index row mutations from the data
table rows and compare them with the actual index rows. Currently, an index row
is expressed as an array of cells, and after this change, it will be one cell
per CF and an empty column cell.
> Supporting the single cell storage format for mutable global indexes
> --------------------------------------------------------------------
>
> Key: PHOENIX-5923
> URL: https://issues.apache.org/jira/browse/PHOENIX-5923
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Priority: Major
>
> It is known that IMMUTABLE_STORAGE_SCHEME = SINGLE_CELL_ARRAY_WITH_OFFSETS
> leads to performance improvement and storage saving. As the name implies this
> storage scheme is currently supported for immutable tables only. Supporting
> the SINGLE_CELL_ARRAY_WITH_OFFSETS storage format for mutable table requires
> reading existing rows for before mutating them, i.e., read-modify-write.
> However, this storage scheme can be used for mutable global index tables
> without any additional IO operation since for every index table update, we
> always read the corresponding data table row and generate the full index row
> from the current state of the data table row and the pending mutation on this
> row. This full index row can be stored using the
> SINGLE_CELL_ARRAY_WITH_OFFSETS storage format even though the data table can
> continue using a mutable storage format. This will allow index tables to
> enjoy the performance improvement and storage saving due to this storage
> format.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
