[jira] [Created] (CALCITE-4663) JoinConditionBasedPredicateInference doesn't simplify childPredicates which causes JoinPushTransitivePredicatesRule pulls up predicates infinitely and StackOverflowErro

yanjing.wang created CALCITE-4663: - Summary: JoinConditionBasedPredicateInference doesn't simplify childPredicates which causes JoinPushTransitivePredicatesRule pulls up predicates infinitely and StackOverflowError Key:

Re: geometry type support problem

Thanks for your reply. I had create a jira: CALCITE-4662 On 6/23/21 4:02 AM, Julian Hyde wrote: It’s possible that the problem is with the JDBC adapter. Calcite would need to connect to PostGIS via its JDBC driver, read the column types,

[jira] [Created] (CALCITE-4662) geometry type support problem

TaoJIn created CALCITE-4662: --- Summary: geometry type support problem Key: CALCITE-4662 URL: https://issues.apache.org/jira/browse/CALCITE-4662 Project: Calcite Issue Type: Bug

Re: Error encountered during build on ppc64le architecture

It looks as if the Redis adapter test is trying to get an unavailable port. See whether the build succeeds if the Redis adapter test is skipped: ./gradlew clean test -x :redis:test If that passes, it indicates that Calcite is sound. (The Redis adapter is probably sound, too, and its test would

Error encountered during build on ppc64le architecture

Hi Team, I encountered an issue while building calcite on ppc64le architecture. For the build I followed the steps provided on official site [ https://calcite.apache.org/docs/howto.html#building-from-git], but failing to do so. Hence need your support in fixing the issue. Logs can be found

Re: geometry type support problem

It’s possible that the problem is with the JDBC adapter. Calcite would need to connect to PostGIS via its JDBC driver, read the column types, and deduce that the column is of GEOMETRY type. JDBC does not have a type-id for GEOMETRY, so this process would be a little ad hoc. (Probably using

geometry type support problem

hi folks, I'm using calcite with postgis, and found the support of geometry type is not very good. Firstly,  geometry was not added to enum "SqlTypeName" as a jdbc type, geometry type  read from postgresql jdbc will convert to ANY type. Since 1.27.0, the hepPlanner will add a