Two problems recently reported in Flink

Hi all, I'd like to present two Calcite-related problems recently reported in the Flink community. 1. Using NULL literal causes NPE. It seems that the constant NULL in Calcite is represented as a RexLiteral with a (null: Comparable) value. In RexUtil.gatherConstraint(), the equals() method is inv

Question about join plan optimization in Flink

Hi all, I got a question about selecting the best plan for join in Flink. For instance, given the logical plan below: LogicalProject(c=[$2], g=[$6]) LogicalFilter(condition=[AND(=($1, +($7, 1)), =(-($0, 1), +($3, 2)))]) LogicalJoin(condition=[true], joinType=[inner]) LogicalTableScan(

Re: Question about join plan optimization in Flink

he join condition contains an equality predicate > on expressions that do not access a field (i.e., expressions that compute a > value). > This would prevent such plans from being translated and only leave the plan > with pushed down expressions. > > Best, Fabian > > 2017-10-

Confusion about the GeoFunctions

Hi all, Recently, the flink community aims to add some OpenGIS functions (see FLINK-9219 ) provided in CALCITE-1968 . For some reasons, we plan to implement some Flink Geom types (as illustrated i

Re: Confusion about the GeoFunctions

> >> In Calcite we are extremely short of development resources. All of the >> spatial work in Calcite has been done by me, on my own time. It is >> depressing to see someone use it and immediately decide they are going to >> re-implement it all in their own project. &g

[jira] [Created] (CALCITE-2004) The TableFunction left outer join was improperly translated

Xingcan Cui created CALCITE-2004: Summary: The TableFunction left outer join was improperly translated Key: CALCITE-2004 URL: https://issues.apache.org/jira/browse/CALCITE-2004 Project: Calcite