Re: [DISCUSS] Automated website builds

Okay, so I think the reason we're not seeing changes being deployed to calcite.apache.org is because the Git repo is not syncing via Gitbox. See https://git-wip-us.apache.org/repos/asf?p=calcite-site.git vs https://github.com/apache/calcite-site/commits/master I've triggered a resync using

[jira] [Created] (CALCITE-5072) Index out of range when calling rows.Next()

Francis Chuang created CALCITE-5072: --- Summary: Index out of range when calling rows.Next() Key: CALCITE-5072 URL: https://issues.apache.org/jira/browse/CALCITE-5072 Project: Calcite Issue

[DISCUSS] Automated website builds

Hey everyone, I just pushed [1], [2] and [3] to calcite, calcite-avatica and calcite-avatica-go to implement automated website builds. As a test commit, I fixed the release announcement for Calcite 1.30.0 [4]. It was built by Github actions in run 2068981585 [5] and was deployed to

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

See Changes: [Francis Chuang] Site: Fix release announcement for 1.30.0 -- [...truncated 50.55 KB...] (type "javacc" with no arguments for help) Reading

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

See Changes: -- [...truncated 50.08 KB...] Warning: Output directory

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

See Changes: [Francis Chuang] Test automated website build -- [...truncated 53.43 KB...] > Task :server:javaCCMain File "TokenMgrError.java" does not

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

See Changes: [Francis Chuang] [CALCITE-3129] Automate website builds -- [...truncated 50.79 KB...] File "SimpleCharStream.java" does not exist. Will

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

Thanks for the feedback, everyone. I'll add comments and improve the structure to make things more clear and readable. I will also land similar changes in calcite-avatica and calcite-avatica-go soon so that we can get the first iteration out. Francis On 31/03/2022 6:22 am, Julian Hyde wrote:

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

I had a quick look and it looks like clean well-thought-out code. I couldn’t figure what it was doing at a high level (e.g. what the generated URLs would look like), so I think some high-level comments would help. +1 Thanks for your excellent work, Francis. Julian > On Mar 30, 2022, at

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

Hi Francis, I went over the workflows and rules and everything looks good to me. Great work! I'm +1 on merging this to master and I am OK with your suggestions about Avatica. Thanks a lot for moving this forward. It will certainly save us a lot of time in the future. When this goes in we need

Re: [DISCUSS] Github PR link to JIRA issue

Hi Thomas, I didn't make myself clear. 6789 is just a random number, should be [CALCITE-], as Julian mentioned. The problem happens on github PR. e.g. in https://github.com/apache/calcite/pull/2757, the commit message title is [CALCITE-4401] SqlJoin toString throws RuntimeException

Re: [DISCUSS] Github PR link to JIRA issue

When I visit https://issues.apache.org/jira/browse/CALCITE-6789, I get an error message: You can't view this issue It may have been deleted or you don't have permission to view it. I can view other tickets, though (e.g., https://issues.apache.org/jira/browse/CALCITE-5008). Maybe the link has

Re: [DISCUSS] Github PR link to JIRA issue

It seems to happen sporadically. Maybe the commit message of the PR needs to start with exactly “[CALCITE-]”. > On Mar 30, 2022, at 10:45 AM, Haisheng Yuan wrote: > > Hi all, > > Previously, the JIRA issue e.g. [CALCITE-6789] in Calcite github PR and > commit message will be automatically

Re: Calcite jars with shaded guava

Wow, I had no idea that anyone was on a version of Guava that old. I checked our history of Guava versions: * In https://issues.apache.org/jira/browse/CALCITE-1590 (Calcite 1.12) we changed the default from 19 to 20, but still supported

[DISCUSS] Github PR link to JIRA issue

Hi all, Previously, the JIRA issue e.g. [CALCITE-6789] in Calcite github PR and commit message will be automatically linked to the JIRA site. Now there is no link anymore. Does anyone know what happened? What can we do to add the link back? Thanks, Haisheng Yuan

Re: Calcite jars with shaded guava

Thank you, Alessandro and Stamatis, for the info. Currently, the guava version being used in druid is 16. So simple exclusion is unlikely to work. I will still give it a try. If it doesn't, we will shade the jars on our end. On Tue, Mar 29, 2022 at 3:38 PM Alessandro Solimando <

Call for Presentations now open, ApacheCon North America 2022

[You are receiving this because you are subscribed to one or more user or dev mailing list of an Apache Software Foundation project.] ApacheCon draws participants at all levels to explore “Tomorrow’s Technology Today” across 300+ Apache projects and their diverse communities. ApacheCon showcases