Re: Proposal to extend Calcite into a incremental query optimizer

PS The “editable doc” that Rui refers to is also a good idea. I think we should create it to continue discussion after the first meeting. Julian > On Jan 28, 2021, at 11:16 AM, Julian Hyde wrote: > > I think good next steps would be a PR and a meeting. The PR will allow us to > read the

Re: Proposal to extend Calcite into a incremental query optimizer

I think good next steps would be a PR and a meeting. The PR will allow us to read the code, but I think we should do the first round of questions at the meeting. The meeting could perhaps start with a presentation of the paper (do you have some slides you are planning to present at VLDB,

Re: Proposal to extend Calcite into a incremental query optimizer

For me to participate in the discussion for the above questions, I will need to read a lot more to know relevant context and likely ask lots of questions :-). A editable doc is probably good for questions and back and forward discussion. -Rui On Thu, Jan 28, 2021 at 10:50 AM Rui Wang wrote:

Re: Proposal to extend Calcite into a incremental query optimizer

I am also happy to help push this work into Calcite (review code and doc, etc.). While you can share your code so people can have more idea how it is implemented, I think it would be also nice to have a doc to discuss open questions above. Some points that I copy those to here: 1. Can this

Re: Adding new operators to Calcite

I think your ANY operator's signature is ANY(column_name, )? In this case you might use Descriptor operator as an example to see how does a operator that accepts column name work:

Re: custom Operator or customExpression

I have solve the problem.thank you wang 发自我的iPhone -- Original -- From: Rui Wang