You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Daniel Wong (Jira)" <ji...@apache.org> on 2020/07/10 04:25:00 UTC
[jira] [Comment Edited] (PHOENIX-5990) Delete statements don't
honor index hints
[ https://issues.apache.org/jira/browse/PHOENIX-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154999#comment-17154999 ]
Daniel Wong edited comment on PHOENIX-5990 at 7/10/20, 4:24 AM:
----------------------------------------------------------------
I spent some time looking at this. DELETE statements ignore hints for the select portion of their execution with the exception of /*+ USE_INDEX_OVER_DATA_TABLE */. That hint does cause the optimizer to choose index path for deletes. [~gjacoby] do you want to change the scope of this to include having the optimizer choose index path or do you want to close as no change needed?
was (Author: dbwong):
I spent some time looking at this. DELETE statements ignore hints for the select portion of their execution with the exception of /*+ USE_INDEX_OVER_DATA_TABLE */. That hint does cause the optimizer to choose index path for deletes. [~gjacoby] do you want to change the scope of this to include having the optimizer choose index path or do you want to close as no change needed?{{}}{{}}{{}}
> Delete statements don't honor index hints
> -----------------------------------------
>
> Key: PHOENIX-5990
> URL: https://issues.apache.org/jira/browse/PHOENIX-5990
> Project: Phoenix
> Issue Type: Bug
> Reporter: Geoffrey Jacoby
> Priority: Major
>
> While investigating a perf issue with a delete statement, we noticed that the query optimizer wasn't using an index with a better (though not complete) match for the WHERE clause than the base table PK was. Even using a query hint to specify the index did not seem to change the EXPLAIN plan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)