You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Botong Huang (Jira)" <ji...@apache.org> on 2022/01/19 11:54:00 UTC

[jira] [Comment Edited] (CALCITE-4568) Tempura: extending Calcite into an incremental query optimizer

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

Botong Huang edited comment on CALCITE-4568 at 1/19/22, 11:53 AM:
------------------------------------------------------------------

[~Leo Zhou] yes, it will probably take some time to digest and review considering the amount of code here. See https://github.com/hbtoo/calcite/commits/botong
[~julianhyde] please let us know if there's anything we can help. The first commit CALCITE-4737 is in already, thanks! 


was (Author: botong):
[~Leo Zhou] yes, it will probably take some time to digest and review considering the amount of code here. 
[~julianhyde] please let us know if there's anything we can help. The first commit CALCITE-4737 is in already, thanks! 

> 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.20.1#820001)