[
https://issues.apache.org/jira/browse/FLINK-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127992#comment-15127992
]
ASF GitHub Bot commented on FLINK-3049:
---------------------------------------
GitHub user vasia opened a pull request:
https://github.com/apache/flink/pull/1572
[FLINK-3049] move Either type to org.apache.flink.types
I went for option 2, i.e. creating the package in `flink-java`. Let me know
if you think it makes more sense to move the type to `flink-core`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vasia/flink flink-3049
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1572.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 #1572
----
commit 681ca600c209d5f7bfc6f5f27d3f5a53b8159d40
Author: vasia <[email protected]>
Date: 2016-02-02T09:41:56Z
[FLINK-3049] move Either type to org.apache.flink.types
----
> Move "Either" type to package "org.apache.flink.types"
> ------------------------------------------------------
>
> Key: FLINK-3049
> URL: https://issues.apache.org/jira/browse/FLINK-3049
> Project: Flink
> Issue Type: Improvement
> Components: Core, Java API
> Affects Versions: 1.0.0
> Reporter: Stephan Ewen
> Assignee: Vasia Kalavri
> Fix For: 1.0.0
>
>
> Types reside in package "org.apache.flink.types", the type utils in
> "typeutils".
> One can either move the type to "flink-core" or create that package in
> flink-java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
