[
https://issues.apache.org/jira/browse/CALCITE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359486#comment-15359486
]
Aman Sinha commented on CALCITE-872:
------------------------------------
[~julianhyde] the proposal for the cancelFlag sounds reasonable to me. It
wasn't obvious to me why CALCITE-1227 (streaming CSV reader) would be related,
but I see that it adds functionality for cancel there. I would have thought
some additional change would be needed in the VolcanoPlanner and HepPlanner to
check for the cancel flag to interrupt planning for the 3 things mentioned in
this JIRA description. Any thoughts ?
> Add support for aborting the query optimization process
> -------------------------------------------------------
>
> Key: CALCITE-872
> URL: https://issues.apache.org/jira/browse/CALCITE-872
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.4.0-incubating
> Reporter: Aman Sinha
> Assignee: Julian Hyde
>
> We should have the facility to abort the query optimization process. There
> are several motivations for having this:
> 1. The optimizer's join planning may take too long (order of minutes) when
> working with larger number of tables.
> 2. Certain sequence of rule applications may cause a cycle.
> 3. Operations related to metadata could potentially introduce a dependency
> cycle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
