[jira] [Created] (CALCITE-5106) Upgrade to Jekyll 4 and remove github-pages

Francis Chuang created CALCITE-5106: --- Summary: Upgrade to Jekyll 4 and remove github-pages Key: CALCITE-5106 URL: https://issues.apache.org/jira/browse/CALCITE-5106 Project: Calcite Issue

Build failed in Jenkins: Calcite » Calcite-snapshots #123

See Changes: [Francis Chuang] Remove instructions for syncing site and master and fix formatting issue in howto -- [...truncated 281.25 KB...] public

Re: Calcite-Avatica-Go: Default branch renamed from master to main

Thanks, Francis. I followed those steps and they worked for me. On Wed, Apr 20, 2022 at 7:17 PM Francis Chuang wrote: > > Hey everyone, > > The default branch for the calcite-avatica-go repository has been > renamed from master to main. > > For your local checked out copies of the repository,

Calcite-Avatica-Go: Default branch renamed from master to main

Hey everyone, The default branch for the calcite-avatica-go repository has been renamed from master to main. For your local checked out copies of the repository, please do the following to migrate: 1. Ensure you are in the repository's folder in your command line. 2. Stash any uncommitted

[jira] [Created] (CALCITE-5105) Add MEASURE type and AGGREGATE aggregate function

Julian Hyde created CALCITE-5105: Summary: Add MEASURE type and AGGREGATE aggregate function Key: CALCITE-5105 URL: https://issues.apache.org/jira/browse/CALCITE-5105 Project: Calcite Issue

Re: History for unreleased versions being published to site

Great idea regarding commenting out the release notes! I think the instructions for releasing should also be updated to remind the RM that the release notes should be uncommented (if they were commented) when preparing a release as well. On 21/04/2022 7:10 am, Julian Hyde wrote: I pushed a

Re: History for unreleased versions being published to site

I pushed a commit to Avatica that comments out the release notes. https://github.com/apache/calcite-avatica/commit/6de8d796b4c388f7c2019fff2c883b8b7909c97e Julian > On Apr 20, 2022, at 1:23 PM,

Re: History for unreleased versions being published to site

+1 Commented release notes seem to be an easy solution. -- Michael Mior mm...@apache.org Le mer. 20 avr. 2022 à 10:00, Julian Hyde a écrit : > Usually we don’t add release notes to history.md until the RC vote, so > this isn’t a problem. > > But occasionally we want to start writing the

Re: [QUESTION] Window functions and Relational Operator Tree

It’s very interesting that you want to convert ZetaSQL to and from Calcite. I think other people will be interested in this. (It would help some of the things I am doing in my $dayjob at Google.) Would you consider contributing this as a new module in Calcite? Or creating a standalone project

Re: [QUESTION] Window functions and Relational Operator Tree

This might help: https://github.com/apache/calcite/blob/e08ca8c5df5dee154ae1a1e6adfa2f9ce693ccf7/core/src/test/java/org/apache/calcite/plan/RelWriterTest.java#L570-L595 And it's JSON + text representations:

[QUESTION] Window functions and Relational Operator Tree

Hi everyone, I'm currently working on a converter from a ZetaSQL AST to a CalciteSQL Relational Operator Tree as part of a BeamSQL feature for Apache Beam. Right now, I'm trying to build a Relational Operator Tree that represents a window function (e.g. "*select SUM(a) over(), COUNT(b) over()

Re: History for unreleased versions being published to site

+1 on Julian's proposal. On Wed, Apr 20, 2022 at 3:00 PM Julian Hyde wrote: > Usually we don’t add release notes to history.md until the RC vote, so > this isn’t a problem. > > But occasionally we want to start writing the rekease notes early. An > example is my recent change to upgrade

Re: History for unreleased versions being published to site

Usually we don’t add release notes to history.md until the RC vote, so this isn’t a problem. But occasionally we want to start writing the rekease notes early. An example is my recent change to upgrade Avatica’s gradle and Java. For such changes we could add the release notes for the upcoming

Re: History for unreleased versions being published to site

I don't necessarily see this as a problem, although instead of 2022-MM-DD for the release date, it might be nice to clearly indicate this is unreleased. -- Michael Mior mm...@apache.org Le mer. 20 avr. 2022 à 08:00, Francis Chuang a écrit : > I noticed that some changes to Calcite's changelog

Re: History for unreleased versions being published to site

On a second though, the downside with this approach is that the change log will not be visible during a vote. Not sure if this is a blocker or if directing voters to read the change log on Github is okay. On 20/04/2022 10:00 pm, Francis Chuang wrote: I noticed that some changes to Calcite's

History for unreleased versions being published to site

I noticed that some changes to Calcite's changelog was deployed to the website automatically: https://calcite.apache.org/docs/history.html The reason is that in the Github Actions workflow

[jira] [Created] (CALCITE-5104) Select with CURRENT_DATE without alias produces alias that can't be parsed by Calcite itself

Vyacheslav Puzakov created CALCITE-5104: --- Summary: Select with CURRENT_DATE without alias produces alias that can't be parsed by Calcite itself Key: CALCITE-5104 URL: