[
https://issues.apache.org/jira/browse/PHOENIX-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6218:
---------------------------------
Fix Version/s: 5.1.0
> Rows deleted count for client side deletes is incorrect for immutable tables
> with indexes
> -----------------------------------------------------------------------------------------
>
> Key: PHOENIX-6218
> URL: https://issues.apache.org/jira/browse/PHOENIX-6218
> Project: Phoenix
> Issue Type: Bug
> Reporter: Tanuj Khurana
> Assignee: Tanuj Khurana
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6218-master.v1.patch
>
>
> For immutable tables if the best query plan for delete uses the data table
> and it has an index, the rows deleted count reported is #(rows
> updated)/#(tables updated) where # of rows updated only includes data table
> rows but the number of tables includes data + index. This reduces the row
> count than the actual rows deleted count.
> The same problem can also happen if the best query plan uses the index table
> and there are more than one index present on the data table. In this case the
> rows updated will include both data table and the index table (one used by
> the query plan) but because there are other indexes also present the #(tables
> updated) will be more and we will get an inaccurate result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
