[
https://issues.apache.org/jira/browse/PHOENIX-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-586.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> Use index when more efficient for DML statements
> ------------------------------------------------
>
> Key: PHOENIX-586
> URL: https://issues.apache.org/jira/browse/PHOENIX-586
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 2.1.0-Release
> Reporter: Artur Denysenko
> Assignee: James Taylor
>
> I have an "EVENT_IDX_T" index on "t" column, and it's used during SELECT:
> ```sql
> 0: jdbc:phoenix:localhost> explain SELECT id FROM event WHERE t=1;
> +------------+
> | PLAN |
> +------------+
> | DEGENERATE SCAN OVER EVENT_IDX_T |
> +------------+
> ```
> Why is the index not used during DELETE?:
> ```sql
> 0: jdbc:phoenix:localhost> explain DELETE FROM event WHERE t=1;
> +------------+
> | PLAN |
> +------------+
> | DELETE ROWS |
> | CLIENT PARALLEL 1-WAY FULL SCAN OVER EVENT |
> | SERVER FILTER BY T = [B@6ae2d0b2 |
> +------------+
> ```
> There is no luck with a hint as well:
> ```sql
> 0: jdbc:phoenix:localhost> explain DELETE /*+ INDEX(t EVENT_IDX_T) */ FROM
> event WHERE t=1;
> +------------+
> | PLAN |
> +------------+
> | DELETE ROWS |
> | CLIENT PARALLEL 32-WAY FULL SCAN OVER EVENT |
> | SERVER FILTER BY T = [B@bf2428d |
> +------------+
> ```
--
This message was sent by Atlassian JIRA
(v6.2#6252)
