[CALCITE-872] Add support for aborting the query optimization process

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.0-incubating
• Component/s: core
• Assignee: Unassigned
• Reporter: Aman Sinha
• Created: 02/Sep/15 03:49
• Updated: 22/Feb/19 01:19

Description

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.

Issue Links

• is depended upon by: DRILL-4355 Query can not be cancelled when it is in the planning phase
• is depended upon by: CALCITE-30 Implement Statement.cancel method
• is related to: DRILL-2884 Have cancel() cause "query canceled" rather than just "ResultSet closed"
• is related to: CALCITE-1227 Add streaming CSV table