[
https://issues.apache.org/jira/browse/FLINK-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000208#comment-15000208
]
Stephan Ewen commented on FLINK-3001:
-------------------------------------
That is all up to us to define. I would say yes to both, and not follow the SQL
semantics here. The Table API may want to follow SQL null semantics, but the
programming language APIs should follow Java/Scala semantics, where {{null ==
null}}.
> Add Support for Java 8 Optional type
> ------------------------------------
>
> Key: FLINK-3001
> URL: https://issues.apache.org/jira/browse/FLINK-3001
> Project: Flink
> Issue Type: New Feature
> Components: Java API
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Priority: Minor
> Fix For: 1.0
>
>
> Using {{Optional}} is a good way to handle nullable fields.
> The missing support for null fields in tuples can be easily handled by using
> {{Optional<T>}} for nullable fields and {{T}} directly for non nullable
> fields.
> That also retains best serialization efficiency.
> Since we cannot always assume the presence of {{Optional}} (only introduced
> in Java8), the TypeExtractor needs to analyze and create that TypeInfo with
> reflection.
> Further more, we need to add the OptionalTypeInfo to the flink-java8 project
> and people need to include flink-java8 in their project if they want to use
> the Optional.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
