Csaba Ringhofer created IMPALA-15457:
----------------------------------------
Summary: GEOMETRY gaps: Think through distinct/equal support
Key: IMPALA-15457
URL: https://issues.apache.org/jira/browse/IMPALA-15457
Project: IMPALA
Issue Type: Sub-task
Components: Backend, Frontend
Reporter: Csaba Ringhofer
Currently GEOMETRY type is considered non-comparable, and disables operators
like = and <.
This also leads not allowing DISTINCT or set operations (e.g. UNION) if the
select list includes a geometry.
Another side effect is not allowing UPDATE optimization where we skip the
update if all columns SET are equal:
https://github.com/apache/impala/blob/40e89e2085d312506607c9572259cf218cbd3cba/fe/src/main/java/org/apache/impala/analysis/UpdateStmt.java#L178
It may be beneficial to add binary comparison . AFAIK engines often don't allow
this to avoid confusion about binary equality vs topological equality. postgis
allow it based on the binary representation of the geometry - this has the
potential side effect though of changing result of queries when internal format
is altered (or needing an extra pass to "normalize" the binary format).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
