[jira] [Created] (CALCITE-5586) Replace boostport/hbase-phoenix-all-in-one docker image with f21global/hbase-phoenix-all-in-one

Francis Chuang created CALCITE-5586: --- Summary: Replace boostport/hbase-phoenix-all-in-one docker image with f21global/hbase-phoenix-all-in-one Key: CALCITE-5586 URL:

Avatica Go and Phoenix

Hey everyone, I currently maintain the phoenix-hbase-all-in-one docker image [1] for running Avatica Go integration tests against Phoenix. The image itself is pretty old and it's been a long while since I updated it. Recently, Docker has announced that free team organizations will be

Re: [QUESTION] Sonar integration fails, how to understand the reason?

Thanks, Stamatis! Will wait for updates from the INFRA side. On Tue, Mar 14, 2023 at 10:23 PM Stamatis Zampetakis wrote: > I logged INFRA-24340 [1] cause I am suspecting that something changed > from the INFRA side. > > For the record, despite the failure the Sonar report seems to be >

Re: [QUESTION] Sonar integration fails, how to understand the reason?

I logged INFRA-24340 [1] cause I am suspecting that something changed from the INFRA side. For the record, despite the failure the Sonar report seems to be reaching SonarCloud [2] as I can see the latest commits there. Best, Stamatis [1] https://issues.apache.org/jira/browse/INFRA-24340 [2]

Re: [QUESTION] Sonar integration fails, how to understand the reason?

For sure it is not related to the particular commit you mentioned since the same error appears for the run before yours [1]. I tend to look in the raw Jenkins console log since it is usually easier to spot why something fails. It may be that an infra change broke this step but I'm not sure yet.

Re: [QUESTION] Sonar integration fails, how to understand the reason?

seems the reason is in artifacts logs[1] java.lang.NoSuchMethodError: No such DSL method 'cleanWs' found among steps [ArtifactoryGradleBuild, MavenDescriptorStep, ...] However still not clear why and how to fix it [1]

[QUESTION] Sonar integration fails, how to understand the reason?

Hello everyone It seems that sonar integration failed for the commit [1]. However inside in logs[2] it tells that build is successful... Could anyone please tell me how to understand what the issue is? In logs I noticed this (not sure if it is related) Project not found. Please check the

[jira] [Created] (CALCITE-5585) Add STRPOS() Function (Enabled for BigQuery)

Tanner Clary created CALCITE-5585: - Summary: Add STRPOS() Function (Enabled for BigQuery) Key: CALCITE-5585 URL: https://issues.apache.org/jira/browse/CALCITE-5585 Project: Calcite Issue

[ANNOUNCE] Apache Calcite 1.34.0 released

The Apache Calcite team is pleased to announce the release of Apache Calcite 1.34.0. Calcite is a dynamic data management framework. Its cost-based optimizer converts queries, represented in relational algebra, into executable plans. Calcite supports many front-end languages and back-end data

Re: [DISCUSS] Towards Calcite 1.34.0

I raised a small PR [1] with few updates in the release process in case someone wants to have a look before I merge it. [1] https://github.com/apache/calcite/pull/3112 On Tue, Mar 14, 2023 at 3:31 PM Stamatis Zampetakis wrote: > > While running the `./gradlew publishDist -Prc=0 -Pasf` task I

Re: [DISCUSS] Towards Calcite 1.34.0

While running the `./gradlew publishDist -Prc=0 -Pasf` task I encountered the problem reported in [1] and was forced to complete the remaining steps manually; hopefully I didn't miss anything. For future reference, I outlined the manual steps that I took under [1]. I also encountered a small

[jira] [Created] (CALCITE-5584) Publish website action only triggers for the last commit in the chain

Stamatis Zampetakis created CALCITE-5584: Summary: Publish website action only triggers for the last commit in the chain Key: CALCITE-5584 URL: https://issues.apache.org/jira/browse/CALCITE-5584

[jira] [Created] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

libopeng created CALCITE-5583: - Summary: Rel2Sql will get an error when select * and join is present Key: CALCITE-5583 URL: https://issues.apache.org/jira/browse/CALCITE-5583 Project: Calcite

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

Thanks for being release manager, Stamatis! On Tue, Mar 14, 2023 at 1:21 PM Stamatis Zampetakis wrote: > I accidentally put Ruben in non-binding votes; sorry about that. Here is > the corrected version: > > N binding +1s: > Stamatis Zampetakis > Benchao Li > Julian Hyde > Francis Chuang > Ruben

Re: [DISCUSS] Towards Calcite 1.34.0

The main branch is open again. On Fri, Mar 10, 2023 at 12:11 PM Stamatis Zampetakis wrote: > I am starting the RC process. Please hold off your commits from main. > > Best, > Stamatis > > On Fri, Mar 10, 2023 at 8:28 AM Alessandro Solimando < > alessandro.solima...@gmail.com> wrote: > >> +1

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

I accidentally put Ruben in non-binding votes; sorry about that. Here is the corrected version: N binding +1s: Stamatis Zampetakis Benchao Li Julian Hyde Francis Chuang Ruben Quesada Lopez N non-binding +1s: Sergey Nuyanzin Scott Reynolds On Tue, Mar 14, 2023 at 1:14 PM Stamatis Zampetakis

[RESULT] [VOTE] Release Apache Calcite 1.34.0 (release candidate 0)

Thanks to everyone who has tested the release candidate and given their comments and votes. Special mention to Sergey, Scott, Ruben, and James for taking the extra burden to test with downstream projects; an incredibly valuable step for quality releases. The tally is as follows. N binding +1s:

[jira] [Created] (CALCITE-5582) Not in or not exist subquery can't work with Oracle db

rebey created CALCITE-5582: -- Summary: Not in or not exist subquery can't work with Oracle db Key: CALCITE-5582 URL: https://issues.apache.org/jira/browse/CALCITE-5582 Project: Calcite Issue Type:

Re: [Question]How to match a node with all its parents

Hi Aitozi, The example you posted does not correspond to how the Spool operator is implemented in Calcite. The Calcite plan has a tree structure not a DAG structure. Best, Stamatis On Mon, Mar 13, 2023 at 4:34 PM Aitozi wrote: > Hi Stamatis, > Thanks for your reply. As I understand, for

Re: Automatically publish Calcite SNAPSHOT artefacts?

Hi James, Thanks for starting this discussion. Regarding Calcite snapshots there is already a Jenkins job [1] publishing regularly artifacts to the snapshots repo [2]. Apart from that, having regular integration tests between Drill and Calcite is a very good idea. The tricky part is to decide

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

Thanks and understood Stamatis. At some point in the future (not in the context of this RC) it would be nice to bounce around ideas about making syntax optional. I have no idea what mechanism, if any, might support something like "iff application has set FLAG_FOO then include the parsing logic

Automatically publish Calcite SNAPSHOT artefacts?

Hi Calcite and Drill devs Here's an idea that, while it doesn't equate to the upstreaming of Drill tests to the Calcite test suite, could mean that all of Drill's tests would automatically and frequently be run with the HEAD of the Calcite main branch. Something Drill started doing last