[DISCUSS] SBOM (Software Bill of Materials)

In the wake of the log4j CVEs [1], people are asking how to improve the security of open source projects, and one idea is to provide a SBOM (Software Bill of Materials) [2] along with each release. I had not heard of SBOM until a couple of days ago. Is anyone on this list familiar with SBOMs and

Re: How to obtain metadata for tables in sub-schemas?

That looks right. So we may have a bug. Also try md.getTables(null, null, "%", new String[] {“TABLE”})); and md.getTables(“", null, "%", new String[] {“TABLE”})); Julian > On Dec 28, 2021, at 1:45 PM, Gunnar Morling > wrote: > > Hi, > > I have created a custom Calcite schema factory

Re: Converting GraphQL query predicates AST -> Calcite "RelNode" mostly working, but "RelBuilder.or()" incorrectly generating an AND condition

I can think of three possibilities: * You are calling the wrong overload of RelBuilder.or and you are passing it a single argument (therefore a trivial OR). * RelBuilder.or does the right thing, but Calcite has a bug in simplifying SEARCH (see https://issues.apache.org/jira/browse/CALCITE-4173

Re: [ANNOUNCE] Apache Calcite 1.29.0 released

Thanks for being RM, Rui! I made a few fix-ups: * I made a force push to ensure that https://github.com/apache/calcite/commit/cbfe0609edcc4a843d71497f159e3687a834119e is still on the master branch. * I

Re: [Calcite Release] Finalizing 1.29.0 release

At https://repository.apache.org/#stagingRepositories I see that there are repositories orgapachecalcite-1123, orgapachecalcite-1124, orgapachecalcite-1125, orgapachecalcite-1126. I believe that the repository that was actually released was

Re: Clean up Metadata type boiler plate and removing generic from MetadataHandler

+1 to everything here. * Thanks to James for starting with a design discussion rather than a PR * And also thanks for starting it on the mailing list (where the most people will see it) * As Jacques says, now is a good time to move the discussion to a Jira case * Thank you both for keeping up the

Re: Why not make the "test" namespace public, or move to a separate Maven module that main pulls in as a "testOnly" dependency?

Gavin, I’m working on this in https://issues.apache.org/jira/browse/CALCITE-4885 . Take a look at FixtureTest [1] to get an idea of how parser, validator, sql-to-rel or rule tests would look in your project. My one concern is that once we

Re: Release notes preparation via release-drafter

-1 Please don’t commit anything just yet. Rather than adding tools, can we discuss what’s wrong and right about the current process. > On Dec 22, 2021, at 3:36 AM, Vladimir Sitnikov > wrote: > > Hi, > > I suggest we start using Release Drafter [1] for the preparation of the > release

[DISCUSS] Trolls and community

Hey community, I need your help. You might have noticed that Vladimir and I are fighting it out in a long email thread [1]. I find it stressful and time-consuming to be involved in threads such as this with Vladimir. And I find myself taking out my frustrations on my family. I should not have to

Re: Use Calcite to generate queries for different data sources

In the test suite, we use Hook.QUERY_PLAN to add handlers. You could do the same. The Elasticsearch adapter will call the handler with the query. See https://github.com/apache/calcite/blob/4bc916619fd286b2c0cc4d5c653c96a68801d74e/core/src/main/java/org/apache/calcite/runtime/Hook.java#L95

Re: [DISCUSS] Java 16 and 17 support

Vladimir, Apparently there *is* a need to raise mail threads. Your comments in https://issues.apache.org/jira/browse/CALCITE-4575 indicated that you were not prepared to accept simple solutions: > If you absolutely want `howto` page to

Re: [DISCUSS] Java 16 and 17 support

For Gradle upgrades, there’s only one place to modify. Add a comment in gradle/wrapper/gradle-wrapper.properties reminding people to also howto.md. For Java upgrades, there aren’t many places to modify. But supporting a new Java version warrants a Jira case (whose headline is the Java upgrade)

Re: [DISCUSS] Extends RelDistribution to support more distribution types

I think you should contribute a change that adds a new value to the enum. I know that enums are not easily extensible, but in cases like this, that can be a feature rather than a bug. There are not very many distribution types, and new distribution types are rarely invented. Requiring people

Re: [DISCUSS] Java 16 and 17 support

I’m happy to do those tasks. > Just one question, where or how can I ensure CI tests for JDK16 and JDK17. > > > Best, > > | > Zhe Hu > | > ---- Replied Message > | From | Julian Hyde | > | Date | 12/22/2021 07:37 | > | To | dev@calcite.apache.org | > | Sub

[DISCUSS] Java 16 and 17 support

Does Calcite now support Java 16 and 17? If think it probably does, because of these three commits: * https://github.com/apache/calcite/commit/6d51d277b158ff7073f29ada4a96a7a74c0b46fc * https://github.com/apache/calcite/commit/dff775d24ae6f8b2e0f3b68fd727ef16fc9cb428 *

Re: [VOTE] Release apache-calcite-1.29.0 (release candidate 0)

> > What is the proper way to fix release note/documentation > suggestions given RC0 is under voting (I guess that does not require a RC1 > cut)? > > just push a new commit later to fix those things? > > -Rui > > On Mon, Dec 20, 2021 at 8:29 PM Julian Hyde

Re: [VOTE] Release apache-calcite-1.29.0 (release candidate 0)

Fixing the problem in the vote email previously noted by xiong duan: [ ] +1 Release this package as Apache Calcite 1.29.0 +1 Downloaded, checked hashes and signatures; compared files with git; checked LICENSE, NOTICE; ensured no binaries in the tarball; built on Ubuntu Linux, JDK 15 and

Re: [DISCUSS] JIRA vs GitHub Issues

Stamatis, You use the word ‘patch’ to describe all code changes, but code changes are different in nature, and to be successful need to be accompanied by more than code. A bug fix needs a good description of the bug. Not ‘I changed these lines and the problem I was having went away and so I

Re: [Calcite Release] Preparing for 1.29.0 Release

Ah, I see Stamatis has Log4j covered: https://issues.apache.org/jira/browse/CALCITE-4950 <https://issues.apache.org/jira/browse/CALCITE-4950>. > On Dec 18, 2021, at 10:17 AM, Julian Hyde wrote: > > I think we should skip CALCITE-4907. There’s still discussion in its PR, >

Re: [Calcite Release] Preparing for 1.29.0 Release

how, >>>>> as all the comments are addressed. This issue forced us to create a >>> copy >>>> of >>>>> the AggregateUnionTransposeRule in our project. >>>>> >>>>> Regards, >>>>> Vladimir &

Re: [Calcite Release] Preparing for 1.29.0 Release

those >> will make the 1.29.0 release. >> >> >> -Rui >> >> On Fri, Dec 17, 2021 at 11:57 AM Ruben Q L wrote: >> >> Hello, >> >> FYI https://issues.apache.org/jira/browse/CALCITE-4737 has been >> merged. >> >> Reg

Re: Creating a parser for Big query

Or use Babel parser. > On Dec 17, 2021, at 9:35 AM, Maxim Gramin wrote: > > It looks like the parser needs to be extended > https://calcite.apache.org/docs/adapter.html#extending-the-parser > > On Fri, Dec 17, 2021 at 5:34 PM Arash Bizhan zadeh > wrote: > >> This is my test query >> >>

Re: [Calcite Release] Preparing for 1.29.0 Release

Rui, Even though https://issues.apache.org/jira/browse/CALCITE-4898 is marked fixed, there’s some fallout regarding maven repositories and category X. That needs to be sorted out before RC0. See [1]. I’m working on getting

[jira] [Created] (CALCITE-4946) Add method RelBuilder.size()

Julian Hyde created CALCITE-4946: Summary: Add method RelBuilder.size() Key: CALCITE-4946 URL: https://issues.apache.org/jira/browse/CALCITE-4946 Project: Calcite Issue Type: Bug

Re: [jira] [Created] (CALCITE-4898) Upgrading Elasticsearch version from 7.0.1 to 7.15 in Elasticsearch Adapter

This is a useful change (just committed in https://github.com/apache/calcite/commit/d6a36fc08715eba31d1d6bc26ef1ff5558d04b8d ) but it introduces a new package repository. Are we OK with that? The ConJars.org

Re: Build failed in Jenkins: Calcite » Calcite-snapshots #13

I hope this isn’t going to be typical now we’ve enabled snapshots. We don’t need any more noise on the dev list. > On Dec 14, 2021, at 2:25 PM, Apache Jenkins Server > wrote: > > See > > >

Re: [DISCUSS] Do we need a Avatica release before Calcite 1.29.0 release?

gt; > > > > > > CALCITE-4152 is a big performance improvement to Avatica with > > > > SPNEGO/Kerberos, but not at all about correctness/datatypes that > > Calcite > > > > needs. > > > > > > > > I'd agree with Julian. > >

[jira] [Created] (CALCITE-4938) Upgrade SQLLine to 1.12.0

Julian Hyde created CALCITE-4938: Summary: Upgrade SQLLine to 1.12.0 Key: CALCITE-4938 URL: https://issues.apache.org/jira/browse/CALCITE-4938 Project: Calcite Issue Type: Bug

[ANNOUNCE] Apache Calcite Avatica 1.20.0 released

this issue. We take your security seriously! Julian Hyde, on behalf of the Apache Calcite team

[jira] [Created] (CALCITE-4937) Upgrade Calcite to Avatica 1.20

Julian Hyde created CALCITE-4937: Summary: Upgrade Calcite to Avatica 1.20 Key: CALCITE-4937 URL: https://issues.apache.org/jira/browse/CALCITE-4937 Project: Calcite Issue Type: Bug

[RESULT] [VOTE] Release apache-calcite-avatica-1.20.0 (release candidate 0) (second vote)

hours from now. Julian On Dec 13, 2021, at 7:40 AM, Josh Elser wrote: (sorry for the belated..) +1 (binding) * xsums/sigs are good * Can build from source * CALCITE-4395 a non-blocker, agreed * Git commit looks to be in order On 12/12/21 9:45 PM, Julian Hyde wrote: Hi all, Yesterday I started

Re: RelNode semantic evolution vs adapter implementations

Vladimir's points are correct in theory, but in practice I fear that it will introduce a lot of red tape and false negatives, and not yield benefits in proportion to that effort. Maybe we can improve how we report breaking changes. I don't recall any feedback (positive or otherwise) about how we

Re: Automatic maven snapshot releases

ter (as opposed to their > own fork), they are more likely to push for a release to help them > accommodate their own releasing needs. > > Of course, these are all just my own theories about this stuff. I > unfortunately don't have any numbers to back this up. Nonetheless, I think > th

[VOTE] Release apache-calcite-avatica-1.20.0 (release candidate 0) (second vote)

Hi all, Yesterday I started a vote for Apache Calcite Avatica 1.20.0, release candidate 0, and then canceled it due to CALCITE-4935. (See https://issues.apache.org/jira/browse/CALCITE-4935.) Note that the subject of this email ends "(release candidate 0) (second vote)". The artifacts are the

Re: Automatic maven snapshot releases

I have no problems with the technical side of this. And I am supportive of one-off snapshots, e.g. a snapshot for testing made a week or two ahead of a release. But there are some downsides with regular, automated snapshots, and I am concerned that projects and companies will become dependent

[CANCEL] [VOTE] Release apache-calcite-avatica-1.20.0 (release candidate 0)

Vote canceled due to https://issues.apache.org/jira/browse/CALCITE-4935.

Re: [VOTE] Release apache-calcite-avatica-1.20.0 (release candidate 0)

gt; runc: > >> >Version: 1.0.2 > >> >GitCommit:v1.0.2-0-g52b36a2 > >> > docker-init: > >> >Version: 0.19.0 > >> >GitCommit:de40ad0 > >> > > >> > &g

[VOTE] Release apache-calcite-avatica-1.20.0 (release candidate 0)

Hi all, I have created a build for Apache Calcite Avatica 1.20.0, release candidate 0. Thanks to everyone who has contributed to this release. You can read the release notes here: https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/docs/history.html The commit to be

Re: Using LogicalCalc in ProjectCalcMergeRule and FilterCalcMergeRule

Comments inline. > On Dec 10, 2021, at 4:34 AM, Максим Грамин wrote: > > 1. In FilterCalcMergeRule get rid of casting to LogicalCalc and LogicalFilter: > > @Override public void onMatch(RelOptRuleCall call) { >final Filter filter = call.rel(0); >final Calc calc = call.rel(1); Yes.

Re: Question about RexLiteral.getValueAs() returning an unscaled long for decimal literals

f the literal as its javadoc says and asking for > a Long because integers are represented as longs in our app. Are you > suggesting always asking for BigDecimal when it's an exact numeric type and > converting it to Long in our app? > > On Wed, Dec 8, 2021 at 4:00 PM Julian Hyde wro

Re: [DISCUSS] Do we need a Avatica release before Calcite 1.29.0 release?

Probably not. * 4cf769f8e - (HEAD -> master, origin/master, origin/HEAD) Disable Travis job that uses Calcite master until [CALCITE-4877] is fixed (4 weeks ago) * 434cf002f - [CALCITE-4877] Make the exception information more explicit for instantiate plugin. (5 weeks ago) * 57c254f24 -

Re: Question about RexLiteral.getValueAs() returning an unscaled long for decimal literals

When Calcite generates enumerable code, it represents each SQL DECIMAL value as a scaled Java Long. (Just as it represents SQL DATE values as Java Integer.) If you want that ‘raw’ value, ask for a BigDecimal. That’s how DECIMAL values are stored at prepare time (i.e. inside the RexLiteral).

Re: RexNode to Disjunctive Normal Form (DNF)

My first reaction was ‘search for DNF in the tests’ but then I see that RexProgramTest has several testCnf methods [1] but no testDnf methods. There is a RexUtil.toDnf method [2] but unlike RexUtil.toCnf it is not tested. With luck you can call RexUtil.toDnf in the same way that you would call

Re: calcite-core 1.28.0 now depends on kotlin-stdlib?

; Michael Mior > mm...@apache.org > > Le sam. 4 déc. 2021 à 01:27, Jacques Nadeau a écrit : >> >> Any opinions on whether we should formalize into some kind of release >> verification step (manual or automatic)? >> >> On Thu, Dec 2, 2021 at 5:22 PM Juli

Re: Snowflake VARIANT support

7c51740ef733fd4f9bde41b0c25e5b0 > [5] > https://github.com/apache/calcite/commit/cc20ca13db4d506d9d4d1b861dd1c7ac3944e56e > [6] > https://github.com/apache/calcite/blob/2317f4ea7779a38d128a756baa5ad21797f2eb6c/core/src/main/java/org/apache/calcite/rel/type/RelDataTypeFactory.java > > O

Re: [DISCUSS] Calcite 1.29.0 release

ulian. That sounds good. I will revisit the release process at the >> beginning of Dec to check what preparation work I need to do. >> >> >> -Rui >> >> On Tue, Nov 23, 2021 at 8:34 AM Julian Hyde >> wrote: >> >>> In my opinion, the more ofte

Re: Feedback on a generic return type version of RelShuttle?

> On Dec 4, 2021, at 9:41 PM, Jacques Nadeau wrote: > > A few thoughts: > > Algebra approach. > > > If I understand the model correctly, I actually implemented this in a > different project last year (not knowing it was now a design pattern). My > main finding was that while it had certain

Re: [VOTE] Move to GitHub PR-centric development workflow, phase out JIRA

-1 I’m happy with the status quo. > On Dec 3, 2021, at 9:34 AM, Vladimir Sitnikov > wrote: > > Hi, > > Let us have a vote for PR-centric workflow for Calcite. > > [ ] +1, let's move to GitHub PRs/Issues for change management. > [ ] -1, keep using JIRA because, > > Here's my vote: > +1

Re: [GITHUB-HELP] The Committer how to merge a PR correctly

Did you search for an answer before posting this question? What did you find? > On Dec 2, 2021, at 5:24 PM, xiong duan wrote: > > Hi, PMC and Committers. As a newcomer, I have one problem want to know. > > Do we have a procedure about The Committer how to merge a PR correctly? > > Every time

Re: Snowflake VARIANT support

Work has not started, and I don’t know of anyone who is planning to work on this. I have logged https://issues.apache.org/jira/browse/CALCITE-4918 and https://issues.apache.org/jira/browse/CALCITE-4919

[jira] [Created] (CALCITE-4919) Add a function to parse a JSON string into a VARIANT object

Julian Hyde created CALCITE-4919: Summary: Add a function to parse a JSON string into a VARIANT object Key: CALCITE-4919 URL: https://issues.apache.org/jira/browse/CALCITE-4919 Project: Calcite

[jira] [Created] (CALCITE-4918) Add a VARIANT data type

Julian Hyde created CALCITE-4918: Summary: Add a VARIANT data type Key: CALCITE-4918 URL: https://issues.apache.org/jira/browse/CALCITE-4918 Project: Calcite Issue Type: Bug

Re: Enable "squash and merge" button in GitHub UI

It definitely makes sense to track who commits what. We want to give credit to active committers! To see the committer, I use ‘--format=fuller’, e.g. $ git --format=fuller origin/master commit 7c423ef23878271b1c50c03629ebfff674985681 Author: huzhe AuthorDate: Sun Nov 14 11:27:55

Re: [DISCUSS] Writing rules in dependent projects without depending on Immutables

onfig or > subclasses of other concrete rule config subclasses. > > [1] https://github.com/Randgalt/record-builder > [2] > https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/CalciteImmutable.java#L30 > > On Thu, Dec 2, 2021 at 12:20 PM Julian Hyd

[DISCUSS] Writing rules in dependent projects without depending on Immutables

I’m trying to write a planner rule in a dependent project. (What what it’s worth, the project is not open source, and is implemented in Kotlin.) I don’t want to make the dependent project depend on the Immutables library, because that introduces an annotation processor and might destabilize our

Re: [DISCUSS] JIRA vs GitHub Issues

For what it’s worth, I actually prefer JIRA’s workflow model. I strongly believe that people should log a JIRA case before starting work on a bug or feature. Then discussion can happen before coding starts. And I like making holistic reviews - reviewing the whole change, its goals, its impact,

Re: calcite-core 1.28.0 now depends on kotlin-stdlib?

This is a surprise to me too. Vladimir? > On Nov 29, 2021, at 4:45 PM, Zoltan Farkas > wrote: > > I see that the latest release of calcite-core brings in kotlin-stdlib as a > dependency., > > > org.jetbrains.kotlin > kotlin-stdlib-jdk8 > 1.5.31 > > > I looked over the

Re: Possible SqlConverter issue?

Yes, it’s a Calcite issue. The correct plan would create two Correlate instances, because the correlating variables are set by different outer-loops. I think you can defer decorrelation until after SqlToRel. That might work better. In your test, add ".withDecorrelate(false)”. Then add another

Re: Re: [DISCUSS] Apache Calcite Online Meetup January 2022

+1 for Jan 19 It would be great if Stamatis repeated one or two of the segments of his tutorial at BOSS. (I was co-presenter but you've all heard enough from me.) The material about adapters is foundational to understanding Calcite. It could happen on Jan 19 or at another meetup in a couple of

Re: [DISCUSS] Calcite 1.29.0 release

In my opinion, the more often we release, the better. A release around 15th of December would be 2 months since the previous release, and probably not too much work, as things have been fairly quiet since 1.28. Thanks for volunteering to be RM. As always, we should make a push to get any PRs

Re: Support for more data types

Riccardo, There is no technical reason for Avatica to not support those data types. If someone contributed support for those data types (or any other standard data types), we would gladly accept. Julian On Mon, Nov 22, 2021 at 3:01 AM Ricardo Peres wrote: > > Hi all, > > Our team is currently

Re: [DISCUSS] Upgrading Elasticsearch in Calcite from 7.0.1 to 7.15

+1 Sounds like a good idea. > On Nov 22, 2021, at 6:40 AM, Zhe Hu wrote: > > Hi, community. > > > Recently, when I tried to fix bugs in Elasticsearch Adapter, I’ve found that > some new features in released Elasticsearch cannot be applied in Calcite, > since the Elasticsearch version in

Re: [DISCUSS] Apache Calcite Online Meetup January 2022

+1 Thanks for suggesting this, Stamatis. Julian > On Nov 22, 2021, at 7:12 AM, Zhe Hu wrote: > > Got it. Thanks！ > | > > > | > Replied Message > | From | xiong duan | > | Date | 11/22/2021 23:09 | > | To | dev | > | Subject | Re: [DISCUSS] Apache Calcite Online Meetup January

Re: binding of boolean literals in SQL

It’s possible, and I would think desirable, to simplify “clean” = true and for that matter “clean” is true to “clean” and based on your experiments it looks as if we do it already. Julian > On Nov 16, 2021, at 18:06, Gavin Nicol wrote: > > I'm writing a FilterableTable

[DISCUSS] Refactoring tests

I am working on https://issues.apache.org/jira/browse/CALCITE-4885, "Fluent test fixtures so that dependent projects can write parser, validator and rules tests". I wanted to give you all a heads up, because it's going to change quite a few lines of code. Here's the problem I'm trying to solve.

[jira] [Created] (CALCITE-4885) Fluent test fixtures so that dependent projects can write parser, validator and rules tests

Julian Hyde created CALCITE-4885: Summary: Fluent test fixtures so that dependent projects can write parser, validator and rules tests Key: CALCITE-4885 URL: https://issues.apache.org/jira/browse/CALCITE-4885

Re: Extracting field identifiers (SqlScopedShuttle / SqlValidator)

You shouldn't need to solve this without dealing with SqlScopedShuttle. If the validator does its job (and yes, it uses SqlScopedShuttle to do its job) then all identifiers will be resolved to the objects they reference. If I were you I would start by running SqlValidatorTest.testFieldOrigin in a

Re: Snowflake JSON suport

I wasn’t aware of this Snowflake functionality. It looks very nice. First, note that Calcite already has JSON support consistent with the SQL standard. See https://calcite.apache.org/docs/reference.html#json-functions . If we were

Re: Calcite for macro parsing in SQL ?

No worries. Thanks for following up and sharing what worked for you. It will help other people who are facing similar problems in future. I’m pleased that you found an example that you could copy! Julian > On Nov 10, 2021, at 7:03 AM, Cyril Catheu wrote: > > Also sorry Julian Hyde

Re: DISCUSS: merge calcite-avatica and calcite repositories

wrote: > > Actually, it is possible to preserve the history of commits when you merge > two repos - > https://stackoverflow.com/questions/17371150/moving-git-repository-content-to-another-repository-preserving-history > > On Tue, Nov 9, 2021 at 11:24 PM Julian Hyde wrote: >

Re: DISCUSS: merge calcite-avatica and calcite repositories

Merging the repositories is unnecessary, and a massive waste of time. Any supposed “time savings” due to the the merged repositories will be eaten up by dozens of small issues that will crop up long after the merge. I was release manager for Calcite and Avatica this time around and it took me

Re: DISCUSS: merge calcite-avatica and calcite repositories

There are many reasons to divide code into modules. To allow separate communities, to allow separate release schedules, to reduce coupling, to make it easier to contribute (because contributors don’t need to understand a large code base), to increase adoption (because people perceive that they

Re: Query across schemas in same database

I think you meant to write “tab1.id = tab2.id”. Based on your description I think there are a couple of things going wrong in the JDBC adapter. It should be putting the tables from different MySQL databases into different calcite schemas. (A calcite schema is a namespace. It may map onto a

Fwd: [jira] [Commented] (CALCITE-2040) Create adapter for Apache Arrow

Karshit has a Gradle question. Is there someone on this list who knows Gradle and can help him out? Julian -- Forwarded message - From: Karshit Shah (Jira) Date: Thu, Nov 4, 2021 at 11:26 AM Subject: [jira] [Commented] (CALCITE-2040) Create adapter for Apache Arrow To:

Re: Calcite for macro parsing in SQL ?

Calcite already has something called macros. They work like Lisp macros (substituting the AST) rather than C macros (your model of string replacement). See JdbcTest.testTableMacro [1]. Does this approach solve your problem? Julian [1]

Re: Job postings on the dev list ?

> On Oct 29, 2021, at 11:15 AM, Michael Mior wrote: > > Somewhat off-topic, but I think your characterization of recruiting as > a zero sum game misses out on the candidate. Presumably a candidate > takes a new position because they benefit in some way. Yes, that’s valid. My characterization

Re: Job postings on the dev list ?

I think Apache has some kind of policy on this, but I couldn’t find a link. It’s a difficult question. If a company making a big investment in Calcite (say rewriting their engine’s query optimizer) then it is good for Calcite if someone is able to get a full-time job working on it. But we don’t

SQLLine

Calcite developers, The SQLLine community is having a conversation about project governance, with options including moving to ASF or an ASF-like PMC model. SQLLine has many users but very few active developers. If you are a SQLLine user, then you are part of the community, and we would like to

Re: Is there a mechanism for constant folding in Calcite?

Chunwei is correct. If there are expressions that you would expect to constant-folded by that rule that aren’t, please log a bug. > On Oct 25, 2021, at 7:10 PM, Chunwei Lei wrote: > > Hi, Ian. > > ReduceExpressionsRule is always used to do constant folding. > > > Best, > Chunwei > > > On

Calcite on Apple silicon (M1 processor)

Has anyone run Calcite on Apple silicon (M1 processor)? Any issues? I noticed that JLine (and therefore SQLLine) has an issue: https://github.com/julianhyde/sqlline/issues/444 Julian

Re: Pseudocolumn support

There’s already an issue logged for this: https://issues.apache.org/jira/browse/CALCITE-4362 . I commented on that case with a sketch of how to approach it. As I understand it, these columns do “belong to the table” in some sense. If you are

[ANNOUNCE] Apache Calcite 1.28.0 released

, and to get involved, visit the project website at: https://calcite.apache.org/ Thanks to everyone involved! Julian Hyde, on behalf of the Apache Calcite Team

Re: CALCITE-4833 review request.

As I said in https://issues.apache.org/jira/browse/CALCITE-4833 , the PR does not solve the whole problem, in fact solves only a very special case of the problem, and therefore we should not accept it. Bug 4833 is valid. I’m sure that there

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

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, Haisheng Yuan, Jacques Nadeau, Julian Hyde, Ruben Q L, Vladimir Sitnikov 4 non-binding +1s: Xiong Duan, Chunwei Lei, Sergey Nuyanzin, Zhaohui Xu

Re: [MongoDB Adapter] How to filter collection based on field in deep nested data

I believe that the JSON_EXISTS function [1] can do this kind of filtering, and Calcite supports it [2]. Julian [1] https://docs.oracle.com/en/database/oracle/oracle-database/12.2/adjsn/condition-JSON_EXISTS.html#GUID-8A0043D5-95F8-4918-9126-F86FB0E203F0

[jira] [Created] (CALCITE-4859) Tableau connector for Calcite

Julian Hyde created CALCITE-4859: Summary: Tableau connector for Calcite Key: CALCITE-4859 URL: https://issues.apache.org/jira/browse/CALCITE-4859 Project: Calcite Issue Type: Bug

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

Since this vote overlaps a weekend, I'll give you all some extra time. The vote will last for 96 hours (or until there is a majority of 3). It will end at 12 noon pacific (1900 UTC) on Tuesday 19th October. Still, early votes are appreciated. Julian On Fri, Oct 15, 2021 at 11:01 AM Julian Hyde

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

Hi all, I have created a build for Apache Calcite 1.28.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.28.0-rc0/site/_docs/history.md The commit to be voted upon:

[jira] [Created] (CALCITE-4856) Gradle prepareVote fails with 'not authorized'

Julian Hyde created CALCITE-4856: Summary: Gradle prepareVote fails with 'not authorized' Key: CALCITE-4856 URL: https://issues.apache.org/jira/browse/CALCITE-4856 Project: Calcite Issue

Re: [DISCUSS] Next releases

I'm ready to produce the first release candidate, but I am blocked by a Gradle issue. Vladimir, I'd be grateful if you could take a look. https://issues.apache.org/jira/browse/CALCITE-4853 Julian On Thu, Oct 14, 2021 at 10:37 AM Julian Hyde wrote: > > I have written a first

[jira] [Created] (CALCITE-4853) Gradle could not determine the dependencies of task ':syncPreviewSiteRepo'

Julian Hyde created CALCITE-4853: Summary: Gradle could not determine the dependencies of task ':syncPreviewSiteRepo' Key: CALCITE-4853 URL: https://issues.apache.org/jira/browse/CALCITE-4853 Project

Re: [DISCUSS] Draft board report for Oct 2021

> > - No new PMC members. Last addition was Ruben Q L on 2020-08-09. > > - No new committers. Last addition was Vladimir Ozerov on 2021-06-23. > > > > ## Project Activity: > > No new version was released. > > > > At ApacheCon 2021, September 22, 20

Re: [DISCUSS] Next releases

is still open for commits, but please be careful not to break the build. I'll probably start a vote today or tomorrow. On Sat, Oct 9, 2021 at 11:24 PM Julian Hyde wrote: > > Now that Avatica’s release 1.19 is final, the master branch is open for > commits. I’ll make the official release ann

Downloads page

Can someone please volunteer to fix https://issues.apache.org/jira/browse/CALCITE-4639, to fix broken links on the downloads page. Because this case concerns the web site, it doesn't need to be fixed BEFORE 1.28 but it needs to be fixed VERY SOON AFTERWARDS. Julian

Re: Request Update the Jirs ISSUE lABEL

Done; see https://issues.apache.org/jira/projects/CALCITE/versions/12350203. On Tue, Oct 12, 2021 at 2:47 PM xiong duan wrote: > As we know. The Avatica-1.19.0 has been released. So the label needs to > update. > > [image: 截屏2021-10-13 05.42.04.png] >

Re: Disable the subquery

Have you considered disabling JoinConditionPushRule? > On Oct 12, 2021, at 12:26 AM, JiaTao Tao wrote: > > Do you use the RelToSqlConverter to convert plan to sql? > > Regards! > > Aron Tao > > > luoc 于2021年10月11日周一 下午4:30写道： > >> Hello Calcite team, >> >> >> I am going to develop a

[jira] [Created] (CALCITE-4847) Parse SQL with BigQuery-style quoted identifiers and character literals

Julian Hyde created CALCITE-4847: Summary: Parse SQL with BigQuery-style quoted identifiers and character literals Key: CALCITE-4847 URL: https://issues.apache.org/jira/browse/CALCITE-4847 Project

[ANNOUNCE] Apache Calcite Avatica 1.19.0 released

website at: https://calcite.apache.org/avatica/ or the Apache Calcite project website: https://calcite.apache.org/ Thanks to everyone involved! Julian Hyde, on behalf of the Apache Calcite team

Re: [DISCUSS] Next releases

dd helpful comments in a couple of key >>> javadoc locations. >>> >>> On Wed, Oct 6, 2021 at 1:02 PM Julian Hyde >>> wrote: >>> >>>> Thanks for following through on this large change, Jacques. Be sure to >>>> document

[RESULT] [VOTE] Release apache-calcite-avatica-1.19.0 (release candidate 0)

; > > >Version: 20.10.8 > > > >API version: 1.41 (minimum version 1.12) > > > >Go version: go1.16.6 > > > >Git commit: 75249d8 > > > >Built:Fri Jul 30 19:52:31 2021 > > > >OS/

<    3   4   5   6   7   8   9   10   11   12   >