[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-v4.patch v4 patch with rebase of PHOENIX-4348 > 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-v2.patch, PHOENIX-4342-v3.patch, > PHOENIX-4342-v4.patch, 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)
[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-v3.patch v3 where the MultiRowDeleteMutationPlan returns the dataPlan as the overall QueryPlan. > 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-v2.patch, PHOENIX-4342-v3.patch, > 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)
[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-v2.patch v2 patch with getQueryPlan added to MutationPlan. > 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-v2.patch, 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)
[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)
