You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2017/11/02 20:49:00 UTC
[jira] [Updated] (PHOENIX-4342) Surface QueryPlan in MutationPlan
[ https://issues.apache.org/jira/browse/PHOENIX-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoffrey Jacoby updated PHOENIX-4342:
-------------------------------------
Attachment: PHOENIX-4342.patch
First cut at this patch.
1. Created "DeleteMutationPlan" which extends MutationPlan and adds a getQueryPlan method
2. Refactored all the anonymous delete MutationPlan classes into real inner classes implementing DeleteMutationPlan
3. Changed DeleteCompiler.compile to return a DeleteMutationPlan.
If all MutationPlans contain a QueryPlan, we can dispense with DeleteMutationPlan and just add a getQueryPlan method to the base interface, but I didn't think that was the case.
[~jamestaylor], fyi.
> Surface QueryPlan in MutationPlan
> ---------------------------------
>
> Key: PHOENIX-4342
> URL: https://issues.apache.org/jira/browse/PHOENIX-4342
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Assignee: Geoffrey Jacoby
> Priority: Minor
> Attachments: PHOENIX-4342.patch
>
>
> For DELETE statements, it'd be good to be able to get at the QueryPlan through the MutationPlan so we can get more structured information at compile time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)