Re: [DISCUSS] Best practice for synchronizing master and site branches

I think it is a good idea to provide versioned JavaDocs. However, even if we only provide the JavaDoc of the latest release, there is no need to maintain two branches (IMHO), because the processes of updating the website and JavaDoc are relatively separate processes (according to [1]). With a

Re: [DISCUSS] Best practice for synchronizing master and site branches

t;>>> > >>>>>> The current procedure for updating the website remains unchanged and > >> it > >>>>> is > >>>>>> documented here: > >>>>>> > >>>>> > >>> > >> ht

Re: [DISCUSS] Best practice for synchronizing master and site branches

h the same as master (git reset > --hard master) and force push (git push --force origin site). > > Francis > > On 25/03/2022 3:03 pm, Fan Liya wrote: > > Hi all, > > > > As part of the release process, we need to synchronize the master and > > site branches (Pleas

[DISCUSS] Best practice for synchronizing master and site branches

Hi all, As part of the release process, we need to synchronize the master and site branches (Please see https://calcite.apache.org/docs/howto.html#making-a-release-candidate). Usually, the site is behind the master branch by some commits. If the existing commits in the site branch are in the same

Re: Virtual key signing party

Sorry my public key finger print: Best, Liya Fan pub rsa4096 2022-03-03 [SC] F905 6357 2D7E 336E 0A0A D095 7F99 D307 0C03 7870 uid [ultimate] Liya Fan (CODE SIGNING KEY) sub rsa4096 2022-03-03 [E] Fan Liya 于2022年3月21日周一 18:43写道： > > Hi Stamatis, > > I w

Re: Virtual key signing party

Hi Stamatis, I wan to attend it. Thanks. Best, Liya Fan pub rsa4096 2019-03-15 [SC] [expires: 2023-03-15] 0474 9577 FD93 4674 B9CD 45C5 D77C 3383 F192 7570 uid [ unknown] Stamatis Zampetakis uid [ unknown] Stamatis Zampetakis sub rsa4096 2019-03-15 [E] [expires:

Re: [HELP][Release 1.30.0]

the 1.30.0 release in the reporter tool [1]. > > > > Best, > > Stamatis > > > > [1] https://reporter.apache.org/addrelease.html?calcite > > > > > > On Sun, Mar 20, 2022 at 11:26 AM Fan Liya wrote: > > > > > The problem was worked around by b

Re: [Calcite Release 1.30.0]

Hi all, Code freeze for master branch is over and commits can resume. Thanks a lot for all who have helped in the release process. Best, Liya Fan Fan Liya 于2022年3月5日周六 08:27写道： > > Hi Stamatis, > > Thanks for your kind help and good suggestions. > > Best, > Liya Fan >

Re: [HELP][Release 1.30.0]

. Best, Liya Fan Fan Liya 于2022年3月20日周日 16:54写道： > Hi all, > > When building the web site, I got another problem. > > I followed the instructions in > https://github.com/apache/calcite/blob/master/site/README.md, and each > step finished successfully. > However, aft

Re: [HELP][Release 1.30.0]

. Install concurrent-ruby-1.1.9 manually 3. Add local source in Gemfile 4. Rebuild index: sudo bundle --full-index I changed another machine and restarted the whole process, but the problem persists. Do you have any idea about the problem? Thank you in advance. Best, Liya Fan Fan Liya 于2022年3

Re: [HELP][Release 1.30.0]

I can see that the release has propagated: > https://dlcdn.apache.org/calcite/apache-calcite-1.30.0/ > > We do need to sign your key though, using a virtual key signing party so > that your key is part of the web of trust. > > Francis > > On 19/03/2022 7:28 pm, Fan Liya wrote

Re: [HELP][Release 1.30.0]

): https://dlcdn.apache.org/calcite/ Do you have any idea about the reason? Is it because my key was not signed, as noted by Julian? Thanks in advance Best, Liya Fan Fan Liya 于2022年3月11日周五 21:49写道： > Hi Stamatis, > > Thanks a lot for your clarification and confirmation. > > B

[RESULT] [VOTE] Release apache-calcite-1.30.0 (release candidate 3)

Thanks to everyone who has tested the release candidate and given their comments and votes. The tally is as follows. 6 binding +1s: Francis Chuang Ruben Q L Haisheng Yuan Michael Mior Julian Hyde Stamatis Zampetakis 3 non-binding +1s: Liya Fan Alessandro Solimando Enrico Olivelli No 0s or -1s.

[VOTE] Release Apache Calcite 1.30.0 (release candidate 3)

Hi all, I have created a build for Apache Calcite 1.30.0, release candidate 3. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.30.0-rc3/site/_docs/history.md The commit to be voted upon:

Re: [RESULT] [VOTE] Release apache-calcite-1.30.0 (release candidate 2)

s, and start a > new RC. (Will require a small force-push.) > > Julian > > > On 2022/03/15 05:50:30 Fan Liya wrote: > > Hi Julian, > > > > Thanks for your feedback and your PR. > > > > Best, > > Liya Fan > > > > Julian Hyde 于2022年3月15日周

Re: [RESULT] [VOTE] Release apache-calcite-1.30.0 (release candidate 2)

n’t find time to vote on this RC. I reviewed the release > notes and they look good. > > > On Mar 14, 2022, at 8:24 PM, Fan Liya wrote: > > > > Thanks to everyone who has tested the release candidate and given > > their comments and votes. > > > > The tally is as f

[RESULT] [VOTE] Release apache-calcite-1.30.0 (release candidate 2)

Thanks to everyone who has tested the release candidate and given their comments and votes. The tally is as follows. 2 binding -1s: Ruben, Francis 2 non-binding +1s: Liya, Enrico 1 binding 0: Stamatis Therefore, I think this release candidate should be rejected, until CALCITE-5040 is

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 2)

(binding) > > - Checksum and signature: ok > - Gradle test: ok > - Calcite-based application test suite: ok > > Best, > Ruben > > > On Fri, Mar 11, 2022 at 1:54 PM Fan Liya wrote: > > > Hi all, > > > > I have created a build for Apache Calcite 1.30.0,

Re: Can't find java file for ImmutableCsvProjectTableScanRule

Hi xiaobo, It seems 'ImmutableCsvProjectTableScanRule' is a generated class. You have to build the project first? Best, Liya Fan xiaobo 于2022年3月13日周日 18:47写道： > Hi, > > we are trying to make our adapter projectable now, but we can't find the > Java file for the

[VOTE] Release Apache Calcite 1.30.0 (release candidate 2)

Hi all, I have created a build for Apache Calcite 1.30.0, release candidate 2. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.30.0-rc2/site/_docs/history.md The commit to be voted upon:

Re: [HELP][Release 1.30.0]

gt; available options and that is sufficient. > > Best, > Stamatis > > [1] > > https://github.com/vlsi/vlsi-release-plugins/commit/b8b3c60760f2065d791c0b095e1b675cdbcfacbd > > On Fri, Mar 11, 2022 at 2:09 PM Fan Liya wrote: > > > Hi all, > > > > Whe

[HELP][Release 1.30.0]

Hi all, When preparing a release build, I ran the command according to the document [1]: *./gradlew prepareVote -Prc=2 -Pasf -Pasf.git.pushRepositoryProvider=GITBOX* Then I got the following error message: *Build calcite FAILURE reason:Execution failed for task ':pushRcTag': Caused

Re: Broken history after force pushing to master

> think it's up to you. > > Best, > Ruben > > [1] https://calcite.apache.org/docs/howto.html#making-a-release-candidate > [2] https://github.com/apache/calcite/pull/2741 > > > On Thu, Mar 10, 2022 at 9:50 AM Fan Liya wrote: > > > Hi Stamatis, > > > &g

Re: Broken history after force pushing to master

> >> Hello Liya, > > >> > > >> No worries, we all make mistakes. > > >> I think the sequence of steps that you describe looks like a plausible > > >> explanation for how we get into this situation. Do you know (from step > > >

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 1)

Hi all, I have prepared a PR for the release note, after addressing related problems (https://github.com/apache/calcite/pull/2741). Please take a look. Thanks a lot. Best, Liya Fan Fan Liya 于2022年3月10日周四 08:22写道： > Hi Ruben and Julian, > > Thanks a lot for your feedback, I will pre

Re: Broken history after force pushing to master

ly have to force-push. But force-pushes can be scary. > It would be nice if there were some guidelines for when force-push is > necessary, and when it is not going to do much damage (e.g. is only going > to change 1 commit). > > Julian > > > > On Mar 9, 2022, at 4:19 PM

[CANCEL][VOTE] Release Apache Calcite 1.30.0 (release candidate 1)

Due to the broken history problem, let's cancel this vote. Thanks to all who have voted in this thread. Best, Liya Fan

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 1)

r the respective thread. > >> > >> -1 (binding) > >> > >> Stamatis > >> > >> [1] https://lists.apache.org/thread/pw7q8tqn78rwq0sfxh6o2rxvwrjgjlkq > >> > >> On Mon, Mar 7, 2022 at 12:27 PM Enrico Olivelli > >> wrote: >

Re: Broken history after force pushing to master

f in the future you (or anybody else) get blocked or experience any > >> problem on a certain step during the release process, do not hesitate to > >> send an email to the dev list with subject "[HELP] ..." describing the > >> issue. In my experience, someone fr

Re: Broken history after force pushing to master

Hi all, I think the broken history was caused by this: 1. In document "Making a release candidate [1]", it says "Make sure master branch and site branch are in sync". 2. I checked the two branches, and find they have diverged. Some commits in the site branch are not in the master branch. 3. I

Re: Bugs dropped on the floor

d be able to > > create the 1.31.0 release version in jira. > > > > Francis > > > > On 8/03/2022 10:44 am, Fan Liya wrote: > > > Hi Ruben, > > > > > > Good suggestion. Thanks. > > > > > > I removed the fix version for a

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

h a > commit right after the release). > So, I'd say that for the moment we can just cancel RC0 vote (an email > "[CANCEL] [VOTE] Release Apache Calcite1.30.0 (release candidate 0)" should > be sent to make it official), and keep RC1 vote open. > > Best, > Ruben > >

Re: Bugs dropped on the floor

Hi Ruben, Good suggestion. Thanks. I removed the fix version for above JIRAs because I could not assign 1.31.0 to them. Version 1.31.0 has not been created, and I have no permission to create it. Could someone with permission please create it? Best, Liya Fan Fan Liya 于2022年3月8日周二 07:37写道

Re: Bugs dropped on the floor

Sorry. I will restore the fix-version. It seems CALCITE-4976 is duplicate with CALCITE-5031. So I will close CALCITE-5031. Best, Liya Fan Julian Hyde 于2022年3月8日周二 06:25写道： > Especially https://issues.apache.org/jira/browse/CALCITE-4976 < > https://issues.apache.org/jira/browse/CALCITE-4976>

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

; On Mar 6, 2022, at 10:31 PM, Francis Chuang > wrote: > > > > Thanks so much Liya! Please cancel this vote by sending a [CANCEL] > message as well, to formalize the cancellation of this vote. > > > > Francis > > > >> On 7/03/2022 5:27 pm, Fan Liya wrote: > &g

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 1)

tay the same as JIRA summary or PR commit? > > Fan Liya 于2022年3月7日周一 14:55写道： > > > Hi all, > > > > I have created a build for Apache Calcite 1.30.0, release > > candidate 1. > > > > Thanks to everyone who has contributed to this release. > > > &

[VOTE] Release Apache Calcite 1.30.0 (release candidate 1)

Hi all, I have created a build for Apache Calcite 1.30.0, release candidate 1. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.30.0-rc1/site/_docs/history.md The commit to be voted upon:

[CANCEL][VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

s well, to formalize the cancellation of this vote. > > Francis > > On 7/03/2022 5:27 pm, Fan Liya wrote: > > After some investigation, I could not resolve the 404 issue of the commit > > link (In my computer, it is not 404, but an error with XML format). > > So I have created

[VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

0 [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... Here is my vote: +1 (binding) Best, Liya Fan Fan Liya 于2022年3月7日周一 14:27写道： > After some investigation, I could not resolve the 404 issue of the commit > link (In my compute

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

on the new build. Thanks. Best, Liya Fan Fan Liya 于2022年3月7日周一 09:53写道： > Thanks for your feedback, Francis. > I will check. > > Best, > Liya Fan > > > Francis Chuang 于2022年3月7日周一 09:36写道： > >> Hey Liya, >> >> Thanks for being RM for this release. &g

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

t/a39b9bf8b1cbab8f4462c41f6b4506753f859f96 > > Thanks! > Francis > > On 5/03/2022 8:56 pm, Fan Liya wrote: > > Hi all, > > > > I have created a build for Apache Calcite 1.30.0, release > > candidate 0. > > > > Thanks to everyone who has contributed

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

for the apache repository, which is not "origin"). Now I have manually pushed the tag, so it should be showing the release note of 1.30.0. Please check. Best, Liya Fan Zhe Hu 于2022年3月5日周六 19:11写道： > Hi, Fan Liya. > Thanks for your great job of releasing Calcite 1.30.0. >

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

Since it is during the weekend, let's extend the voting period to at least 96 hours. Best, Liya Fan Fan Liya 于2022年3月5日周六 17:56写道： > Hi all, > > I have created a build for Apache Calcite 1.30.0, release > candidate 0. > > Thanks to everyone who has contributed to this re

[VOTE] Release Apache Calcite 1.30.0 (release candidate 0)

Hi all, I have created a build for Apache Calcite 1.30.0, release candidate 0. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.30.0-rc0/site/_docs/history.md The commit to be voted upon:

Re: [Calcite Release 1.30.0]

.com/jbalint/fe02278549c38ea037af44b3efdb5545 > > > > Jess > > > > On Fri, Mar 4, 2022 at 9:41 AM Fan Liya wrote: > > > > > Hi Stamatis, > > > > > > Thanks for your good suggestion. > > > I have uploaded the updated KEYS file here &g

Re: [Calcite Release 1.30.0]

gt; Export your public key according to the instructions in the KEYS file, > upload it somewhere (e.g., your github repo), and send us the link to the > key. > > Best, > Stamatis > > > On Fri, Mar 4, 2022 at 3:45 PM Fan Liya wrote: > > > Hi all, > > > >

Re: [Calcite Release 1.30.0]

Liya 于2022年3月4日周五 22:28写道： > Opened a PR for the release (https://github.com/apache/calcite/pull/2739). > > Please take a look. Thanks. > > Best, > Liya Fan > > > Fan Liya 于2022年3月4日周五 19:55写道： > >> Done. Thanks for your kind reminder. >> >> Best,

Re: [Calcite Release 1.30.0]

Opened a PR for the release (https://github.com/apache/calcite/pull/2739). Please take a look. Thanks. Best, Liya Fan Fan Liya 于2022年3月4日周五 19:55写道： > Done. Thanks for your kind reminder. > > Best, > Liya Fan > > Ruben Q L 于2022年3月4日周五 17:11写道： > >> Than

Re: [Calcite Release 1.30.0]

ted (remove fix version 1.30) if they are not > going to be part of this release. > > Best, > Ruben > > [1] > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > > On Fri, Mar 4, 2022 at 6:44 AM Fan Liya wrote: > > > Hi all, > &g

[Calcite Release 1.30.0]

Hi all, I am going to start the releasing process for Calcite 1.30.0. The following JIRA items will be included in this release: https://issues.apache.org/jira/browse/CALCITE-1794?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20and%20fixVersion%20%3D%201.30.0 Please check. If

Re: [DISCUSS] Towards Calcite 1.30.0

to release > Calcite 1.31. > > Thanks, > Andrei. > > > > On Tue, Mar 1, 2022 at 9:40 PM Fan Liya wrote: > > > Got it. Thanks for the confirmation. > > > > Best, > > Liya Fan > > > > Stamatis Zampetakis 于2022年3月2日周三 05:30写道： > > &

Re: [DISCUSS] Towards Calcite 1.30.0

Got it. Thanks for the confirmation. Best, Liya Fan Stamatis Zampetakis 于2022年3月2日周三 05:30写道： > Since nobody objects, let's aim for Friday or whichever other day is > convenient for you. > > Best, > Stamatis > > On Sun, Feb 27, 2022 at 2:22 PM Fan Liya wrote:

Re: [DISCUSS] Towards Calcite 1.30.0

it would be the best time for you to cut the first release > candidate so that we plan appropriately and get some PRs inside. > > Best, > Stamatis > > On Fri, Feb 25, 2022 at 7:03 AM Fan Liya wrote: > > > Sure. If Andrei is not available, I think I am OK. > > > > Be

Re: [DISCUSS] Towards Calcite 1.30.0

Sure. If Andrei is not available, I think I am OK. Best, Liya Fan Stamatis Zampetakis 于2022年2月24日周四 19:10写道： > Thanks for driving this Ruben! > > Another alternative if Andrei is unavailable at the moment would be to see > if they can switch places with Liya. Would this be possible Liya? > >

Re: [ANNOUNCE] New Calcite PMC chair: Ruben Q L

Congratulations, Ruben! Haisheng, thanks for your great work! Best, Liya Fan Jing Zhang 于2022年1月24日周一 11:30写道： > Congrats Ruben! > Haisheng, thanks a lot for serving as a chair! > > > Enrico Olivelli 于2022年1月23日周日 05:17写道： > > > Congrats! > > > > Enrico > > > > Il Sab 22 Gen 2022, 03:03

Re: [DISCUSS] Release Managers

Hi Haisheng, I am interested in volunteering. Best, Liya Fan On Fri, Jun 4, 2021 at 6:50 AM Julian Hyde wrote: > Yes, I am release manager for 1.28. I’ll aim to release first week of > August. > > Somewhat related to the call for release managers: we need active > committers. (Stamatis, can

Re: Using Calcite as a Distributed Optimizer

I think you can refer to Flink Best, Liya Fan On Fri, May 14, 2021 at 12:32 PM Atri Sharma wrote: > Is there an example I can refer to? > > On Fri, 14 May 2021, 04:59 Haisheng Yuan, wrote: > > > Yes, definitely. Many distributed big data systems use Apache Calcite to > > optimize queries and

Re: Apache Arrow adapter

Hi Michael, Thanks for sharing the great work. I believe it is important work for both communities. Best, Liya Fan On Thu, Apr 8, 2021 at 3:30 AM Michael Mior wrote: > Hi all, > > I wanted to share some work one of my (now former) students, Karshit > Shah, has done with integrating Apache

Re: TopDown Optimizer Questions

Hi Priyendra, I am not sure if I fully understand your questions, and I want to try to answer this one: "*At what point does the enforcer operator come into play? Is it the RelNodes responsibility * *to add the enforcer operator for cases where it is unable to honor a traitset or does the

Re: Nested loop joins

Hi Priyendra, We have FilterReduceExpressionsRule which reduces filter conditions. It performs the simplification based on org.apache.calcite.rex.RexSimplify. Best, Liya Fan On Mon, Mar 1, 2021 at 1:45 PM Priyendra Deshwal wrote: > Hello friends, > > I am playing around with TPC-DS schema and

Re: [ANNOUNCE] New committer: Liya Fan

Dear all, I want to express my sincere gratitude to you for all your kind help. I feel honored to have the opportunity of working with you in this awesome community. In the past years, I have been working on some different components of the SQL engine, now in Alibaba, and previously in

Re: Need a Jason output if physical tree

ll get [t.a], but miss > [t.b]. > To my knowledge, rules are the only way to reliably. constrain columns > returned from the scan. > > Regards, > Vladimir. > > вт, 22 дек. 2020 г. в 05:14, Fan Liya : > > > Hi Bhavya, > > > > Sorry I am not sure if I

Re: Need a Jason output if physical tree

> the column information for TableScan without the rules. If you have any > specific example where we have used this approach will be really helpful to > me. > > Thanks and regards > Bhavya > > On Mon, Dec 21, 2020 at 5:53 PM Fan Liya wrote: > > > Hi Bhavya, > &g

Re: Need a Jason output if physical tree

Hi Bhavya, IMO, to solve the problem from a global view, the following steps needs to be taken: 1. Generate a physical plan in the original way (without considering column pruning in the table scan) 2. Modify all the table scans in the plan with the RelColumnMDOrigins utility (the details have

Re: Need a Jason output if physical tree

> > When all three prerequisites are ready, the optimizer will produce missing > projects (if any), then push them down the operator tree, and finally merge > into the scan. > > Regards, > Vladimir > > Пт, 18 дек. 2020 г. в 13:34, Fan Liya : > > > Hi B

Re: Need a Jason output if physical tree

"type": "CHAR", > > "nullable": true, > > "precision": 5 > > } > > }, > > { > > "literal": "HELLO", > > "type&quo

Re: Need a Jason output if physical tree

> without using Rules as it will be a lot of rule that we need to implement. > > Thanks and Regards > Bhavya > > On Fri, Dec 18, 2020 at 9:47 AM Fan Liya wrote: > > > Hi Bhavya, > > > > It seems the problem is that the json format provided by Calcite does not

Re: Need a Jason output if physical tree

Hi Bhavya, It seems the problem is that the json format provided by Calcite does not include properties specific to your operator? If so, I think you can override RelNode#explainTerms in your operator to attach the properties. Best, Liya Fan On Thu, Dec 17, 2020 at 10:45 PM Bhavya Aggarwal

Re: [ANNOUNCE] New Calcite PMC chair: Haisheng Yuan

Congratulations, Haisheng! Looking forward to your great work in the coming year! Stamatis, thanks for your great work in the past year! Best, Liya Fan On Fri, Dec 18, 2020 at 11:11 AM Feng Zhu wrote: > Thanks for your work and effort, Stamatis! > Congratulations, Haisheng! > > Stamatis

Re: [HELP] Local build fails

It is working for me too. Thanks for your kind help! Best, Liya Fan On Thu, Dec 10, 2020 at 11:14 AM Chunwei Lei wrote: > Vladimir, Julian, Liya, thank you very much for your help. It works now. > > > > Best, > Chunwei > > > On Thu, Dec 10, 2020 at 4:12 AM Vladimir Sitnikov < >

Re: [HELP] Local build fails

Thanks for the advice. I have tried jdk1.8.0_271 and jdk1.9 (build 9+181), but the problem is still there. Best, Liya Fan On Mon, Dec 7, 2020 at 1:51 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Fan Liya, please update Java. It is the solution. > > Vladimir >

Re: [HELP] Local build fails

Thanks for opening the discussion. I am having the same problem, and my Java version is jdk1.8.0_201. The problem can be reproduced by the simple command gradlew build I have tried to find a solution by Googling, but so far no solution has worked for me. Best, Liya Fan On Sat, Dec 5, 2020 at

Re: [DISCUSS][CALCITE-4199] Ensure nullness verification via checkerframework

Hi Vladimir, Thanks for your effort. I still believe in the value of nullable annotations. Please see my comments below > I'm puzzled. First you say "annotations are beneficial for code > readability", then > you proceed with "annotations does not make the code more readable". For ordinary

Re: [DISCUSS][CALCITE-4199] Ensure nullness verification via checkerframework

Hi Vladimir, Thanks for bringing this up. In general, I believe annotations for nullability are beneficial for code readability and reasoning. However, after reading the PR, I am having the same feelings as Nikolay. Intuitively, the "@Nullable" annotation does not provide much information, and

Re: [DISCUSS] State of the project 2020

Hi Stamatis, Thanks for your great work! I am feeling lucky to have you as our chair in 2020! Concerning the problem of PR reviewing, one method that comes to my mind is to divide Calcite into a few sub-areas, and assign some owners to each sub-area (based on code contribution, etc.). So once a

Re: [DISCUSS] Make SqlNodeList implement ListSqlNode>

IMO, the major advantage of Iterable over List is that we do not need to know all the elements before traversing the collection. According to the current implementation, however, SqlNodeList is internally backed by a List, so the advantage of Iterable no longer exists. Therefore, I think it is

Re: How to parse sql of DDL

) > at org.apache.calcite.sql.parser.SqlParser.parseQuery(SqlParser.java:163) > at org.apache.calcite.sql.parser.SqlParser.parseStmt(SqlParser.java:188) > ——— > > > > > > > 原始邮件 > 发件人: Fan Liya > 收件人: dev > 发送时间: 2020年11月4日(周三) 10:40 > 主题: Re: How to parse sql

Re: How to parse sql of DDL

Hi Xiao, It's hard to diagnose the problem without seeing your code. My suggestion is that you can debug some test cases in our code base (related to SqlParser), and check how it works. Best, Liya Fan On Wed, Nov 4, 2020 at 10:34 AM xiao cai wrote: > Hi > I just want to konw how to parse the

Re: Why ProjectJoinTransposeRule not in Calcite default rule set.

I also think the ProjectJoinTransposeRule should be included in the main optimizer process. Best, Liya Fan On Fri, Oct 23, 2020 at 10:43 AM JiaTao Tao wrote: > This rule is only used in RelOptMaterializations#substitute, is not in > Calcite's main optimizer

Re: DISCUSS: the concept of duplicate insensitive aggregate functions

particular algebraic > structure, and we could exploit the properties of those structures to > perform optimizations. > > Julian > > [1] https://twitter.github.io/algebird/ > > [2] https://en.wikipedia.org/wiki/Monoid > > On Tue, Oct 13, 2020 at 7:26 PM Fan Liya wr

Re: DISCUSS: the concept of duplicate insensitive aggregate functions

, Liya Fan On Wed, Oct 14, 2020 at 2:59 AM Julian Hyde wrote: > I agree. ANY_VALUE and SINGLE_VALUE are duplicate-insensitive. > > > On Oct 13, 2020, at 2:17 AM, Fan Liya wrote: > > > > Hi Julian, > > > > Thanks a lot for your feedback. > > I t

Re: DISCUSS: the concept of duplicate insensitive aggregate functions

PM Julian Hyde wrote: > We already have this concept. See SqlAggFunction.getDistinctOptionality(), > added in https://issues.apache.org/jira/browse/CALCITE-3159 < > https://issues.apache.org/jira/browse/CALCITE-3159>. > > Julian > > > > On Oct 13, 2020, at 12:54 AM

DISCUSS: the concept of duplicate insensitive aggregate functions

Hi all, I would like to introduce the idea of duplicate insensitive aggregate functions. For such functions, the aggregation results remain the same even after deduplication. For example, given a sequence of data {1, 1, 2, 2, 3, 5, 5}, the aggregation results of MIN are the same regardless of

Re: [DISCUSS][CALCITE-4199] Ensure nullness verification via checkerframework

Sounds great! Thanks for your effort. Does it require installing something in the developer's machine? Best, Liya Fan On Sun, Sep 27, 2020 at 7:10 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Here's a sample issue: > >

Re: Disabling JaninoRelMetadataProvider

> output a list of the classes that were missing from the initial > config. > > Julian > > On Mon, Sep 21, 2020 at 4:53 AM Fan Liya wrote: > > > > Hi Julian, > > > > Thank you for the feedback and good suggestions. > > > > The idea of lazy load is

Re: Disabling JaninoRelMetadataProvider

do better. > > Maybe we have a class name and arguments for the metadata provider, which > is loaded on demand. Will work for the test and also in production. > > Julian > > > On Sep 18, 2020, at 12:57 AM, Fan Liya wrote: > > > > Hi Enrico, > > > >

Re: Disabling JaninoRelMetadataProvider

Hi Enrico, We have also observed the problem. Janino compilation is time consuming. For each single Java class, it takes tens of milli-seconds. Moreover, the compilation will take place multiple times, because: 1. We have multiple types of metadata. 2. The class for a particular type of metadata

Re: [ANNOUNCE] New committer: Rui Wang

Congratulations, Rui! Best, Liya Fan On Thu, Sep 10, 2020 at 9:45 AM Danny Chan wrote: > Congrats Rui! > > Best, > Danny Chan > > > > > 在 2020年9月10日，上午6:28，Francis Chuang 写道： > > > > Congrats Rui! > >

Re: [ANNOUNCE] Ruben Quesada Lopez joins Calcite PMC

Congratulations, Ruben! Best, Liya Fan On Fri, Aug 14, 2020 at 2:49 AM Julian Hyde wrote: > Thanks for your hard work on the project and in the community, Ruben. Well > deserved. > > Julian > > > > On Aug 13, 2020, at 6:19 AM, Thomas Rebele > wrote: > > > > Congrats, Ruben! > > > >

Re: [DISCUSS] Sarg (search argument) to generalize and replace IN in RexCall

Hi Julian, Thanks for opening the discussion. In general, I am convinced of the value and importance of the proposal. I want to discuss more about the algebra involved, as the simplified range sets may not have the minimum computational costs. Some examples: 1. Suppose we have expression x in

Re: Re: [ANNOUNCE] New committer: Forward Xu

Congratulations, Forward! Best, Liya Fan On Wed, Apr 29, 2020 at 8:51 PM Wang Yanlin <1989yanlinw...@163.com> wrote: > Congrations! Forward!-- > > Best, > Wang Yanlin > > > > > > At 2020-04-29 10:52:25, "Feng Zhu" wrote: > > Congrations! Forward! > > > >best, > >Feng > > > >Chunwei Lei

Re: Re: [ANNOUNCE] New committer: Jin Xing

Congratulations, Jin! Best, Liya Fan On Wed, Apr 29, 2020 at 8:51 PM Wang Yanlin <1989yanlinw...@163.com> wrote: > Congrats, Jin Xing! > > > -- > > Best, > Wang Yanlin > > > > > > 在 2020-04-29 13:58:53，"Zoltan Haindrich" 写道： > >Congrats! > > > >On 4/29/20 7:32 AM, Enrico Olivelli wrote: > >>

Re: Re: [ANNOUNCE] New committer: Wang Yanlin

Congratulations, Yanlin! Best, Liya Fan On Wed, Apr 29, 2020 at 8:50 PM Wang Yanlin <1989yanlinw...@163.com> wrote: > Hi, guys, thanks for your warm welcome. > > > > I'm working in Ant Finical, Alibaba Group. Currently my team is working > on building a system to process big data in form of

Re: [ANNOUNCE] New committer: Vineet Garg

Congratulations, Vineet! Best, Liya Fan On Sun, Apr 26, 2020 at 10:30 AM Aman Sinha wrote: > Congratulations Vineet ! > > -Aman > > On Sat, Apr 25, 2020 at 7:15 PM Feng Zhu wrote: > > > Congratulations, well deserved! > > > > best, > > Feng > > > > Chunwei Lei 于2020年4月26日周日 上午10:12写道： > > >

Re: The Travis CI build failure

According to my observations, many failures are caused by SocketTimeOut exceptions. So maybe we need to add timeout & retry logic for such test cases. Best, Liya Fan On Mon, Apr 20, 2020 at 11:13 AM Francis Chuang wrote: > Does the Github Actions tests always pass when this happens? > > I

Re: Calcite translates in-subqueries to inner joins

gt; [1] > > https://lists.apache.org/thread.html/ra7d7a309592d327a5e912ded7d541c79a3c587fa2daba950cc463762%40%3Cdev.calcite.apache.org%3E > [2] > > https://lists.apache.org/thread.html/f77bf1f946b8c026989163294a2134e485fe7897201c479bbb528c6d%40%3Cdev.calcite.apache.org%3E > > On M

Calcite translates in-subqueries to inner joins

Hi all, Given a SQL query with an in subquery: select a.name from dept a where a.deptno in ( select b.deptno * 2 from dept b) Calcite translates it to an inner join, but the correct way should be translating it to a left semi join. According to the comments in the code, it seems this behavior

Re: Apply for contribute permission

Thank you so much, Francis. Best, Liya Fan On Mon, Apr 13, 2020 at 12:23 PM Francis Chuang wrote: > Hey, > > I've added you as a contributor in jira. > > Francis > > On 13/04/2020 1:20 pm, Fan Liya wrote: > > Hi all, > > > > I want to contribu

Apply for contribute permission

Hi all, I want to contribute to calcite, could you please give me the contribution permission? My jira id is fan_li_ya (Liya Fan). Thank you! Liya Fan

Re: Set of k-cheapest plans

IMO, there is no easy way, and the algorithm should depends on definition of 'alternative plans'. In general, the algorithm can proceed like this: 1. we use the volcano algoirthm to find the best plan 2. we make the self cost of some node to be infinite, and then apply the volcano algorithm again

  1   2   >