David Chaava created FLINK-39896:
------------------------------------
Summary: FLIP-XXX: GEOGRAPHY type in Flink SQL and Table API
Key: FLINK-39896
URL: https://issues.apache.org/jira/browse/FLINK-39896
Project: Flink
Issue Type: Improvement
Components: Table SQL / API, Table SQL / Planner
Reporter: David Chaava
This issue tracks the proposal for introducing a first-class GEOGRAPHY type in
Flink SQL and the Table API.
Flink currently has no native geospatial type. Users working with geographic
data have to rely on workarounds such as encoding geometries as strings,
storing binary blobs, or integrating external libraries without SQL-level type
support. These approaches are not ergonomic, interoperable, or type-safe.
The proposal introduces a native GEOGRAPHY logical type for geospatial values
such as points, lines, and polygons. The type is expected to support standard
representations such as WKT and WKB, with proper serialization and catalog
integration.
The proposal also includes built-in geospatial SQL functions, such as
ST_Distance, ST_Contains, and ST_AsText, so users can express spatial
predicates and transformations directly in Flink SQL.
Connector and format support should allow GEOGRAPHY values to be read and
written using standard geospatial encodings such as WKT and WKB where
applicable.
The proposal is currently being discussed as a draft FLIP. The final scope,
APIs, function set, and implementation details are not yet finalized, and this
issue should not be considered ready for implementation until the FLIP
discussion reaches consensus.
DISCUSS thread: [[DISCUSS] FLIP-XXX: GEOGRAPHY type in Flink SQL and Table
API-Apache Mail
Archives|https://lists.apache.org/thread/flbj8dfdfgs26klrxt7xch3r9785ky67]
FLIP draft:
[https://docs.google.com/document/d/1rpOTETT_Ui3TlEGioUr2NKJ1p1dlxjJQudXHndxBpO0/edit?usp=sharing]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
