davidchaava opened a new pull request, #28680:
URL: https://github.com/apache/flink/pull/28680

   ## What is the purpose of the change
   
   This draft PR adds the initial Java Table API entry point and runtime data
   representation for the proposed native Flink GEOGRAPHY type.
   
   It is part of the prototype for the ongoing FLIP discussion around native
   GEOGRAPHY support in Flink SQL / Table API.
   
   This PR is stacked on top of the GEOGRAPHY logical type model PR and is not
   intended to be merged before the FLIP direction is agreed.
   
   ## Brief change log
   
   - Add `DataTypes.GEOGRAPHY()`.
   - Add `GeographyData`.
   - Add `BinaryGeographyData` backed by raw ISO WKB bytes.
   - Add `GEOGRAPHY` accessors to row and array data structures.
   - Add binary row/array support for `GEOGRAPHY`.
   - Add `GeographyDataSerializer`.
   - Add tests for the Java API, binary representation, and serializer.
   
   ## Verifying this change
   
   This change adds and extends tests for the GEOGRAPHY API and runtime
   representation:
   
   - `DataTypesTest`
   - `SchemaTest`
   - `BinaryGeographyDataTest`
   - `GeographyDataSerializerTest`
   - `RowDataSerializerTest`
   - `TypeSerializerTestCoverageTest`
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies: no
   - Public API: yes, adds `DataTypes.GEOGRAPHY()` as part of the proposed type 
API
   - Serializers: yes, adds `GeographyDataSerializer`
   - Runtime per-record code paths: yes, adds row/array access paths for 
GEOGRAPHY values
   - Deployment or recovery: no
   - S3 file system connector: no
   
   ## Documentation
   
   - Does this pull request introduce a new feature? yes
   - If yes, how is the feature documented? not documented yet; this is a draft 
PR for the FLIP discussion


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to