[
https://issues.apache.org/jira/browse/FLINK-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005360#comment-15005360
]
Vasia Kalavri commented on FLINK-3002:
--------------------------------------
Here's my first take on this:
https://github.com/vasia/flink/tree/either-java-type.
I created an Either class with an empty constructor and 2 static methods to
create Left and Right. I also have an initial implementation for the
EitherTypeInfo and EitherSerializer. Feedback and ideas are welcome! If you
think that's a nice way to go, I'll clean up the code and write tests. In my
view, the problem with Either not being abstract is semantic, i.e. an Either
that is neither Left nor Right shouldn't be allowed.
> Add an EitherType to the Java API
> ---------------------------------
>
> Key: FLINK-3002
> URL: https://issues.apache.org/jira/browse/FLINK-3002
> Project: Flink
> Issue Type: New Feature
> Components: Java API
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Assignee: Vasia Kalavri
> Fix For: 1.0
>
>
> Either types are recurring patterns and should be serialized efficiently, so
> it makes sense to add them to the core Java API.
> Since Java does not have such a type as of Java 8, we would need to add our
> own version.
> The Scala API handles the Scala Either Type already efficiently. I would not
> use the Scala Either Type in the Java API, since we are trying to get the
> {{flink-java}} project "Scala free" for people that don't use Scala and o not
> want to worry about Scala version matches and mismatches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
