[ 
https://issues.apache.org/jira/browse/CALCITE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397736#comment-17397736
 ] 

Julian Hyde commented on CALCITE-4568:
--------------------------------------

[~botong], Thank you for rebasing. I know that the onus is now on us committers 
to review in a timely manner. My plate is full for the next couple of weeks 
(traveling, with [~zabetak], to Copenhagen for VLDB 2021 -- maybe I will see 
you there?!) but I'll start reviewing when I get back. If other committers can 
start reviewing now, that would be much appreciated.

> Tempura: extending Calcite into an incremental query optimizer
> --------------------------------------------------------------
>
>                 Key: CALCITE-4568
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4568
>             Project: Calcite
>          Issue Type: New Feature
>            Reporter: Botong Huang
>            Priority: Major
>
> As discussed in the email thread, this is an attempt to extend the Calcite 
> optimizer into a general incremental query optimizer, based on our research 
> paper published in VLDB 2021:
> Tempura: a general cost-based optimizer framework for incremental data 
> processing
> To our best knowledge, this is the first general cost-based incremental 
> optimizer that can find the best plan across multiple families of incremental 
> computing methods, including IVM, Streaming, DBToaster, etc. Experiments (in 
> the paper) shows that the generated best plan is consistently much better 
> than the plans from each individual method alone.
> In general, incremental query planning is central to database view 
> maintenance and stream processing systems, and are being adopted in active 
> databases, resumable query execution, approximate query processing, etc. We 
> are hoping that this feature can help widening the spectrum of Calcite, 
> solicit more use cases and adoption of Calcite.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to