[
https://issues.apache.org/jira/browse/CALCITE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359497#comment-15359497
]
Julian Hyde commented on CALCITE-872:
-------------------------------------
Agreed, further work is needed in VolcanoPlanner and HepPlanner. For the
purposes of CALCITE-1227 and CALCITE-1301 it is sufficient that we agree on the
data type.
Cancel is more important for streaming queries than for regular queries because
it's the only way to stop a streaming query!
> 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)
