dianfu opened a new pull request #11414: [FLINK-16606][python] Throw exceptions 
for the data types which are not currently supported
URL: https://github.com/apache/flink/pull/11414
 
 
   
   ## What is the purpose of the change
   
   *Currently, there are still cases where a data type isn't supported as the 
Python data type will be firstly converted to TypeInformation which will lose a 
few information, e.g,*
    - the precision for TimeType could only be 0
    - the length for VarBinaryType/VarCharType could only be 0x7fffffff
    - the precision/scale for DecimalType could only be 38/18
    - the precision for TimestampType/LocalZonedTimestampType could only be 3
    - the resolution for DayTimeIntervalType could only be `SECOND` and the 
fractionalPrecision could only be 3
    - the resolution for YearMonthIntervalType could only be `MONTH` and the 
`yearPrecision` could only be 2
    - the CharType/BinaryType/ZonedTimestampType is not supported
   
   We should throw exceptions for the cases not supported.
   
   ## Brief change log
   
     - *Update the types.py to throw exceptions when a data type is not 
supported*
   
   
   ## Verifying this change
   
   This change is a trivial rework without any test coverage.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to