[
https://issues.apache.org/jira/browse/FLINK-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008499#comment-17008499
]
Jingsong Lee commented on FLINK-15469:
--------------------------------------
Hi [~docete], we need think about the whole story.
If we have "getRecordDataType", how to implement "getOutputType", how to
describe "tuple2" in DataType, or we need find another way.
> UpsertStreamTableSink should support new type system
> ----------------------------------------------------
>
> Key: FLINK-15469
> URL: https://issues.apache.org/jira/browse/FLINK-15469
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Affects Versions: 1.10.0
> Reporter: Zhenghua Gao
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently *UpsertStreamTableSink* can only returns TypeInformation of the
> requested record, which can't support types with precision and scale, e.g.
> TIMESTAMP(p), DECIMAL(p,s).
> A proposal is deprecating the *getRecordType* API and adding a
> *getRecordDataType* API instead to return the data type of the requested
> record.
> {code:java}
> /**
> * Returns the requested record type.
> *
> * @Deprecated This method will be removed in future versions. It's
> recommended to use {@link #getRecordDataType()} instead.
> */
> @Deprecated
> TypeInformation<T> getRecordType();
> /*
> * Returns the requested record data type.
> */
> DataType getRecordDataType();
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
