[
https://issues.apache.org/jira/browse/PHOENIX-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor resolved PHOENIX-3472.
-----------------------------------
Resolution: Invalid
Issuing delete markers is necessary to maintain the secondary index. If this is
a problem, then perhaps something can be done at the HBase level to improve
performance.
> Mutable index adds DeleteFamily markers which impacts query performance
> -----------------------------------------------------------------------
>
> Key: PHOENIX-3472
> URL: https://issues.apache.org/jira/browse/PHOENIX-3472
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.9.0
> Reporter: Mujtaba Chohan
>
> {noformat}
> create table M (k varchar not null primary key, v archer);
> create index MI on M(v);
> upsert into M values ('a','b');
> {noformat}
> Raw scan shows the following two kv pair with the first one being a delete
> marker
> {noformat}
> ROW COLUMN+CELL
>
> \x00a column=0:, timestamp=1478801841429, type=DeleteFamily
>
> b\x00a column=0:_0, timestamp=1478801841429, value=_0
> {noformat}
> This severely impacts read query performance as data size grows, the number
> of DeleteFamily markers also grows linearly in the table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
