Re: Can calcite translate Oracle SQL to MySQL

Calcite can do this with some additional effort and Coral leverages Calcite to do exactly that, although it currently supports Hive, Spark, and Trino conversions. There are public APIs to extend to other dialects on the input and output sides. There is also a UI

[jira] [Created] (CALCITE-6138) Parser does not accept TIMESTAMP WITH TIME ZONE as a data type

Mihai Budiu created CALCITE-6138: Summary: Parser does not accept TIMESTAMP WITH TIME ZONE as a data type Key: CALCITE-6138 URL: https://issues.apache.org/jira/browse/CALCITE-6138 Project: Calcite

Re: avatica-go: resultset offset management

Just wanted to quickly update with some investigation I have done with the test project [1]. I am testing against the Avatica HSQLDB server and it appears that the offset is never populated in the frames that are returned from the server, so that might be the cause. [1] https://github.com/F21/

Re: avatica-go: resultset offset management

Hi Egor, As Julian mentioned, please open a jira issue and we can further debug and find the root cause. Can you also switch to the apace/calcite-avatica-go repo (rather than rilldata's), so that we're looking at the same code? Would you be also able to edit your local copy of calcite-avati

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

PQS already uses Avatica 1.23.0 [1], which already had the change to upgrade checkstyle (which in turn required a newer version of Java). I wonder if there's something else causing the issue Istvan is seeing. [1] https://github.com/apache/phoenix-queryserver/blob/master/pom.xml#L88 On 28/11/20

Re: avatica-go: resultset offset management

Egor, I don’t know whether your hypothesis is correct, but it sounds plausible and well-researched. Therefore I think you should put it into a jira case, so the issue and discussion is on the record. If there is a flaw in your argument and the jira case is subsequently closed, there’s no shame

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

Istvan, You must read the build instructions. If you do not read the build instructions, you have no basis for voting -1. Fixing gradle may or may not be the solution. (It might make gradle more complex and fragile.) Julian > On Nov 27, 2023, at 2:08 PM, Sergey Nuyanzin wrote: > > Meanwhil

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

Meanwhile I checked the code the root cause of the behavior above is upgrade of checkstyle version from 6.18 to 10.3.2 [1] which happened in 1.23.0, i.e. it is reproducible with 1.23.0 in this case, please correct me if I'm wrong, this should not be considered as a blocker [1] https://issues.apa

[jira] [Created] (CALCITE-6137) Upgrade gradle to 8.4

Sergey Nuyanzin created CALCITE-6137: Summary: Upgrade gradle to 8.4 Key: CALCITE-6137 URL: https://issues.apache.org/jira/browse/CALCITE-6137 Project: Calcite Issue Type: Bug C

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

I created a PR[1] The main idea is to introduce another property jdk8.checkstyle which is set to 9.3 before resolving dependency for checkstyle it checks the current java version. In case of 1.8 it uses new property otherwise the old one new property also allows to keep ability to change version fo

Re: Can calcite translate Oracle SQL to MySQL

If you're looking for a "translate X-to-Y dialect of SQL" tool, jOOQ does this fairly well. What you have to do is parse the string of SQL into a jOOQ query AST, then render it using a different SQL dialect. You can experiment with the results of this online here: Format, pretty print, and transl

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

Can someone who knows Gradel make a patch to get Gradle to set -Pcheckstyle.version=9.3 when it detects Java 1.8 ? This is super simple in Maven with profiles, I expect that it should not be very hard in Gradle either. Also, I don't think that the exact JVM patch level has anything to do with thi

avatica-go: resultset offset management

Hi all, this exception happens when Apache Druid Avatica protobuf endpoint is used: "Druid can only fetch forward. Requested offset”. I tried to debug that and saw that any simple query fails if it triggers fetching of multiple frames. I speculate that when the first ExucuteRequest is sent

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

Hi, latest jdk 8 is 8u391, 8u371 is two version behind. https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R8u391-BPR On Mon, Nov 27, 2023 at 4:21 AM Istvan Toth wrote: > -1 (non binding) > > I have successfully built and run the PQS test suite with the Avatica RC > with Java

[jira] [Created] (CALCITE-6136) There is an error link in tutorial.md in docs

蔡灿材 created CALCITE-6136: Summary: There is an error link in tutorial.md in docs Key: CALCITE-6136 URL: https://issues.apache.org/jira/browse/CALCITE-6136 Project: Calcite Issue Type: Bug C

[jira] [Created] (CALCITE-6135) BEARER authentication support

Aron Attila Meszaros created CALCITE-6135: - Summary: BEARER authentication support Key: CALCITE-6135 URL: https://issues.apache.org/jira/browse/CALCITE-6135 Project: Calcite Issue Typ

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

-1 (non binding) I have successfully built and run the PQS test suite with the Avatica RC with Java 11. (I had to tweak the PQS maven setup a bit, but that's not Avatica's fault) When I tried to do the same with Java 8, I ran into the issues mentioned above. I was able to hack around the checksty

[jira] [Created] (CALCITE-6134) Can't parse custom function with name 'DATEADD' in babel

SimonAlexs created CALCITE-6134: --- Summary: Can't parse custom function with name 'DATEADD' in babel Key: CALCITE-6134 URL: https://issues.apache.org/jira/browse/CALCITE-6134 Project: Calcite Is