[jira] [Created] (CALCITE-2068) throws NPE in RelMdPercentageOriginalRows when getPercentageOriginalRows returns null

godfrey he created CALCITE-2068: --- Summary: throws NPE in RelMdPercentageOriginalRows when getPercentageOriginalRows returns null Key: CALCITE-2068 URL: https://issues.apache.org/jira/browse/CALCITE-2068

Re: About the Spatial functionality

I've tried to cast the Zip's loc column into double like this: SELECT ​ ​ "city", cast("loc" [0] AS DOUBLE) AS "lon", cast("loc" [1] AS DOUBLE) AS "lat" ​ ​ FROM "geode"."Zips" ​ ​ LIMIT 10; ​This seems to work fine. ​But when i try to use the ST_Point function i get: "No match found for

Re: About the Spatial functionality

I believe that should work. I'll let others correct me if I'm missing the boat here. -- Michael Mior mm...@apache.org 2017-11-28 12:31 GMT-05:00 Christian Tzolov : > Thanks @Michael! Can i assume that > ​ ​ > in > ​ ​ > the SchemaFactory > ​#​ > create(SchemaPlus

Re: About the Spatial functionality

Thanks @Michael! Can i assume that ​ ​ in ​ ​ the SchemaFactory ​#​ create(SchemaPlus parentSchema, String name, ​ ...​ ) ​ method ​the root schema is constructed? And can i use the parentSchema ​ like this: ModelHandler.addFunctions(parentSchema, null, ImmutableList.of(), ​ ​

Re: About the Spatial functionality

Unfortunately it didn't help still get " No match found for function signature ST_Point(, )" ​. ​Could it be that i need to ad some schema or other prefix? e.g. "geode"."ST_Point"( Also can i check interactively what are the registered functions? ​ On 28 November 2017 at 18:33, Michael Mior

[jira] [Created] (CALCITE-2069) RexSimplify.removeNullabilityCast() always removes cast for operand with ANY type

Volodymyr Vysotskyi created CALCITE-2069: Summary: RexSimplify.removeNullabilityCast() always removes cast for operand with ANY type Key: CALCITE-2069 URL:

Re: About the Spatial functionality

I believe the geospatial functions are not currently registered by default. You can see an example of how to do this in CalciteAssert.java. Once you have constructed the root schema, the following should be sufficient: ModelHandler.addFunctions(rootSchema, null, ImmutableList.of(),

Re: About the Spatial functionality

​Ok, ​ I think i ​ solved the riddle​ . ​H ad to remove ​the ​ quotes from ​the ​ function name (e.g. use ST_Point instead of "ST_Point"). This ​ is due to the ​ upCase=TURE parameter ​in ​ addFunctions ​ ​ . I don't see the error anymore. Now i'm facing another issue i believe is related with

Handling Functions in custom adapter implementations?

Hey there, I have another question related to ​ ​ handling ​​ spatial ( ​or​ any) functions in custom adapter implementations. For e ​ ​ example the ​ ​ ​rel . plan for the following query ​(​ with ​​ spatial function ​)​ EXPLAIN PLAN FOR SELECT "city", ST_Point( cast("loc" [0] AS

Re: Handling Functions in custom adapter implementations?

Yes, the appropriate solution would be to check the expressions being projected and not to trigger your rule for projections you can't handle. For example, check out CassandraProjectRule#matches which validates that only field references are being projected. -- Michael Mior mm...@apache.org

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

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

Re: Handling Functions in custom adapter implementations?

Yeh, unlike Cassandra, Geode support certain function types (such as CAST and ITEM). To prevent dropping support for those, i've blacklisted just the SqlTypeName.GEOMETRY RexNode for now. It went a step further to hit the ST_Point parameter types issues :) "No applicable constructor/method found

Re: Calcite does not handle NaN, Infinity float values

I’d be open to adding support for NaN and Infinity to Calcite’s SQL dialect (possibly enabled using a flag). But it would be more work than just letting in Double.NaN in RexBuilder and RexLiteral. > On Nov 27, 2017, at 1:22 PM, Volodymyr Tkach wrote: > > 1) As for sql

Re: About the Spatial functionality

Yes, you should not use quotes if upcase is true since all functions are registered with uppercase names and all unquoted literals are also automatically upcased. Glad this helped! -- Michael Mior mm...@apache.org 2017-11-28 14:18 GMT-05:00 Christian Tzolov : > ​Ok, ​ > I

Re: About the Spatial functionality

There are no test data sets, I’m afraid. I would love to add a data set that includes various kinds of geometries (points, lines, polygons). One candidate is the one in the OpenGIS Simple Feature Access spec[1] section C.3.1.2 onwards. There ought to be (but isn’t, right now) an easier way to

Re: About the Spatial functionality

What data sets (types) would we want and need for testing? My colleagues run a very large GIS research center*, and I am sure I can get hold of all kinds of test data. * - https://www.ornl.gov/division/csed/gist On Tue, Nov 28, 2017 at 8:36 PM, Julian Hyde wrote: > There are

Re: About the Spatial functionality

@Julian are there some tests, json datasets? Perhaps in calcite-test-dataset? Also I will try to cast the "loc" from Zips into DOUBLE columns to test the ST_Point On 28 November 2017 at 02:24, Julian Hyde wrote: > It’s true that you can’t define a GEOMETRY column in a foreign