[jira] [Created] (CALCITE-2066) RelOptUtil.splitJoinCondition() could not split condition with case after applying FilterReduceExpressionsRule

Volodymyr Vysotskyi created CALCITE-2066: Summary: RelOptUtil.splitJoinCondition() could not split condition with case after applying FilterReduceExpressionsRule Key: CALCITE-2066 URL:

Re: Towards Calcite release 1.15

Thanks for reviewing, Michael. Yes, it’s a lot. Materialized views were a big motivation for doing this. You currently have to do some tricky work with APIs to define materialized views (mappings inside the planner, predicates, statistics). I wanted to demonstrate it working using a few lines

Towards Avatica 1.11 and Avatica-Go version ?.?

It’s been a while since we released Avatica. At the very least we could use a new version to upgrade its dependencies. Also, what about a release of Avatica-Go? I don’t think we have done an Apache release yet. Julian

Re: Towards Calcite release 1.15

I’ve just committed 707 and 2061. That leaves the following: https://issues.apache.org/jira/browse/CALCITE-2018 AssertionError: rel has lower cost (julian to review PR #552) https://issues.apache.org/jira/browse/CALCITE-2054 UPDATE with parameters (julian to review PR #568)

[jira] [Created] (CALCITE-2067) RexBuilder can't handle NaN,Infinity double constants

Volodymyr Tkach created CALCITE-2067: Summary: RexBuilder can't handle NaN,Infinity double constants Key: CALCITE-2067 URL: https://issues.apache.org/jira/browse/CALCITE-2067 Project: Calcite

JIRA Github integration

Hi, I see that there is no automatic link between PRs and JIRA. In Apache BookKeeper (I am committer there) we have such link: if you name a PR with for instance CALCITE-Xxx and you cite the issue id in commit messages Apache Github bot is able to copy every comment to JIRA automatically. I think

Re: Towards Avatica 1.11 and Avatica-Go version ?.?

Here's my update for avatica-go: I am currently still accepting PRs and pushing fixes to the original boostport/avatica repository as there is not a release for Avatica-Go yet. Changes to boostport/avatica are currently cherry-picked into Avatica-Go. In regards to the work done on

Re: Towards Calcite release 1.15

Il lun 27 nov 2017, 20:19 Julian Hyde ha scritto: > I’ve just committed 707 and 2061. That leaves the following: > > https://issues.apache.org/jira/browse/CALCITE-2018 AssertionError: rel > has lower cost (julian to review PR #552) >

Re: JIRA Github integration

Sounds fine to me personally although perhaps others have some objections I'm not aware of. -- Michael Mior mm...@apache.org 2017-11-27 15:44 GMT-05:00 Enrico Olivelli : > Hi, > I see that there is no automatic link between PRs and JIRA. > In Apache BookKeeper (I am

Calcite-Master - Build # 154 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #154) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/154/ to view the results.

Re: JIRA Github integration

No objections from me, as long as it doesn’t cause excessive posts to the dev list. As a small project this is an area we have under-invested. Larger projects such as Spark seem to have very nice integration between GitHub, JIRA and various CIs. Julian > On Nov 27, 2017, at 1:15 PM, Michael

Re: Towards Calcite release 1.15

I ran tests for the Cassandra adapter. I'll try to do this for a few others as well. -- Michael Mior mm...@apache.org 2017-11-27 14:19 GMT-05:00 Julian Hyde : > I’ve just committed 707 and 2061. That leaves the following: > > https://issues.apache.org/jira/browse/CALCITE-2018

About the Spatial functionality

Hey there, I'm exploring the new Spatial (https://calcite.apache.org/docs/spatial.html) functionality and i've been trying to figure out what are the minimal requirements for using it with my custom adapter. Following the guidelines i've set LENIENT conformance in my jdbc URL (

Re: About the Spatial functionality

It’s true that you can’t define a GEOMETRY column in a foreign table. But you can define a VARCHAR column and apply the ST_GeomFromText to it, or if you want a point you can define a pair of DOUBLE columns and apply the ST_Point function. In essence, our implementation of GEOMETRY is only an