[ https://issues.apache.org/jira/browse/FLINK-8630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365649#comment-16365649 ]
ASF GitHub Bot commented on FLINK-8630: --------------------------------------- Github user twalthr commented on the issue: https://github.com/apache/flink/pull/5491 Thanks for the review @xccui. I agree that a pure string-based format would be helpful as well. For this we can simply use a string serialization schema later. In a long-term view we will need to implement scalar functions that can handle a json string and allow accessing such a string as type-safe as possible. > To support JSON schema to TypeInformation conversion > ----------------------------------------------------- > > Key: FLINK-8630 > URL: https://issues.apache.org/jira/browse/FLINK-8630 > Project: Flink > Issue Type: Sub-task > Components: Streaming Connectors > Reporter: Xingcan Cui > Assignee: Timo Walther > Priority: Blocker > Fix For: 1.5.0 > > > To support (FLINK-8558), we need to generate a \{{TypeInformation}} from a > standard [JSON schema|http://json-schema.org/] (and maybe vice verse). There > are some problems to be discussed, e.g., how to handle JSON {{Number}} type. > One option would be we always return a specific type, which can be configured > to be double or BigDecimal, for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)