[
https://issues.apache.org/jira/browse/FLINK-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009354#comment-15009354
]
ASF GitHub Bot commented on FLINK-3002:
---------------------------------------
GitHub user vasia opened a pull request:
https://github.com/apache/flink/pull/1371
[FLINK-3002] Add Either type to the Java API
Implemented as discussed in the corresponding JIRA.
I haven't added this type to the docs yet. The data types section in the
programming guide contains the following categories:
- Java Tuples and Scala Case Classes
- Java POJOs
- Primitive Types
- Regular Classes
- Values
- Hadoop Writables
I don't think `Either` belongs to any of these. Shall I add it as its own
category?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vasia/flink either-java-type
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1371.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1371
----
----
> 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.0
> Reporter: Stephan Ewen
> Assignee: Vasia Kalavri
> Fix For: 1.0.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)
