[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589238#comment-14589238
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user Shiti commented on the pull req
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589239#comment-14589239
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user Shiti closed the pull request a
Github user Shiti closed the pull request at:
https://github.com/apache/flink/pull/834
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user Shiti commented on the pull request:
https://github.com/apache/flink/pull/834#issuecomment-112635882
merged b59c81bc41f0fc4ade5359dfdf42549a76d412fa
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588983#comment-14588983
]
ASF GitHub Bot commented on FLINK-2232:
---
Github user mjsax commented on the pull req
Github user mjsax commented on the pull request:
https://github.com/apache/flink/pull/845#issuecomment-112599473
IHMO, ready to be merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/837
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588860#comment-14588860
]
Robert Metzger commented on FLINK-2220:
---
I would actually do this in the TypeExtract
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/830
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588825#comment-14588825
]
ASF GitHub Bot commented on FLINK-2225:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/843
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588822#comment-14588822
]
ASF GitHub Bot commented on FLINK-2232:
---
GitHub user mjsax opened a pull request:
GitHub user mjsax opened a pull request:
https://github.com/apache/flink/pull/845
[FLINK-2232] StormWordCountLocalITCase fails
increased sleeping time for IT-Cases to make tests more stable
additional bug fix: isRunning was not volatile in AbstractStormSpoutWrapper
You can merge
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588752#comment-14588752
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/834#issuecomment-112566051
Thanks for your work. :smile:
Could you please close the PR manually, I forgot to add a tag for closing
it in the commit.
---
If your project is set up for it
[
https://issues.apache.org/jira/browse/FLINK-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588677#comment-14588677
]
Matthias J. Sax commented on FLINK-2217:
I guess most people see it as a feature.
[
https://issues.apache.org/jira/browse/FLINK-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588645#comment-14588645
]
Flavio Pompermaier commented on FLINK-2217:
---
To me the fact that jars remain the
[
https://issues.apache.org/jira/browse/FLINK-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588562#comment-14588562
]
Ronny Bräunlich commented on FLINK-2211:
Hey people,
I have a small (big, major (p
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/830#issuecomment-112497483
If there are no objections, I'd like to merge it this evening. Then we can
create the next release candidate.
---
If your project is set up for it, you can reply to
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588366#comment-14588366
]
ASF GitHub Bot commented on FLINK-2225:
---
Github user tillrohrmann commented on the p
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/843#issuecomment-112496491
Will merge it then.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have thi
[
https://issues.apache.org/jira/browse/FLINK-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588364#comment-14588364
]
ASF GitHub Bot commented on FLINK-2214:
---
GitHub user tillrohrmann opened a pull requ
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/844
[FLINK-2214] [ml] Fixes prediction join operation and empirical risk join
operation of ALS by giving join hint
Fixes prediction join operation and empirical risk join operation of ALS by
giving
[
https://issues.apache.org/jira/browse/FLINK-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588360#comment-14588360
]
ASF GitHub Bot commented on FLINK-2229:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/842#issuecomment-112495580
Good fix, +1 to merge
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have th
[
https://issues.apache.org/jira/browse/FLINK-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588351#comment-14588351
]
ASF GitHub Bot commented on FLINK-2214:
---
Github user tillrohrmann closed the pull re
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588350#comment-14588350
]
ASF GitHub Bot commented on FLINK-2225:
---
Github user StephanEwen commented on the pu
Github user tillrohrmann closed the pull request at:
https://github.com/apache/flink/pull/836
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/843#issuecomment-112494219
Great catch!
+1 to merge
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
[
https://issues.apache.org/jira/browse/FLINK-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels resolved FLINK-2226.
---
Resolution: Fixed
> Fail YARN application on failed single-job YARN cluster
>
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/838
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588266#comment-14588266
]
ASF GitHub Bot commented on FLINK-2226:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588259#comment-14588259
]
ASF GitHub Bot commented on FLINK-2161:
---
Github user nikste commented on the pull re
Github user nikste commented on the pull request:
https://github.com/apache/flink/pull/805#issuecomment-112477088
Changed according to comments,
@tillrohrmann I did not check it on a cluster, since I don't have one
available at the moment. I checked with a local jobmanager (using
[
https://issues.apache.org/jira/browse/FLINK-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588198#comment-14588198
]
ASF GitHub Bot commented on FLINK-2120:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels closed FLINK-2120.
-
Resolution: Fixed
> Rename AbstractJobVertex to JobVertex
> --
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/840
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated FLINK-2120:
--
Affects Version/s: (was: master)
0.9
> Rename AbstractJobVert
[
https://issues.apache.org/jira/browse/FLINK-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated FLINK-2120:
--
Fix Version/s: 0.10
> Rename AbstractJobVertex to JobVertex
> --
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587778#comment-14587778
]
Matthias J. Sax edited comment on FLINK-2232 at 6/16/15 3:15 PM:
---
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned FLINK-2232:
--
Assignee: Matthias J. Sax
> StormWordCountLocalITCase fails
> -
Aljoscha Krettek created FLINK-2234:
---
Summary: CoStreamWindow is Dependent on Input Ordering
Key: FLINK-2234
URL: https://issues.apache.org/jira/browse/FLINK-2234
Project: Flink
Issue Type:
Ufuk Celebi created FLINK-2233:
--
Summary: InputFormat nextRecord Javadocs out of sync
Key: FLINK-2233
URL: https://issues.apache.org/jira/browse/FLINK-2233
Project: Flink
Issue Type: Bug
Github user mbalassi commented on the pull request:
https://github.com/apache/flink/pull/837#issuecomment-112432774
Found the bug, was a trivial one on my side. Now the produced NOTICE looks
the following for e.g. flink-shaded-hadoop. [1]
It would be a bit nicer if we could c
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587966#comment-14587966
]
ASF GitHub Bot commented on FLINK-2225:
---
GitHub user tillrohrmann opened a pull requ
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587968#comment-14587968
]
ASF GitHub Bot commented on FLINK-2225:
---
Github user tillrohrmann commented on the p
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/843#issuecomment-112410790
@StephanEwen do I overlook something by excluding static code paths from
the co-location groups?
---
If your project is set up for it, you can reply to this email a
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/843
[FLINK-2225] [scheduler] Excludes static code paths from co-location
constraint to avoid scheduling problems
Including static code paths in the co-location constraints can lead to a
slot assign
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587955#comment-14587955
]
Till Rohrmann commented on FLINK-2225:
--
I think I found the problem. Depending on whe
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587778#comment-14587778
]
Matthias J. Sax edited comment on FLINK-2232 at 6/16/15 12:23 PM:
--
[
https://issues.apache.org/jira/browse/FLINK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587920#comment-14587920
]
Maximilian Michels commented on FLINK-2218:
---
Great! Thank you.
> Web client can
[
https://issues.apache.org/jira/browse/FLINK-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587883#comment-14587883
]
Márton Balassi commented on FLINK-2221:
---
A documentation for 0.9 has been pushed, th
[
https://issues.apache.org/jira/browse/FLINK-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Márton Balassi closed FLINK-2209.
-
Resolution: Implemented
Implemented via be50795.
> Document how to use TableAPI, Gelly and FlinkM
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/839
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/841
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587871#comment-14587871
]
ASF GitHub Bot commented on FLINK-2209:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587872#comment-14587872
]
ASF GitHub Bot commented on FLINK-2221:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/835
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587810#comment-14587810
]
ASF GitHub Bot commented on FLINK-2161:
---
Github user nikste commented on a diff in t
[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587808#comment-14587808
]
ASF GitHub Bot commented on FLINK-2161:
---
Github user nikste commented on a diff in t
[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587809#comment-14587809
]
ASF GitHub Bot commented on FLINK-2161:
---
Github user nikste commented on a diff in t
Github user nikste commented on a diff in the pull request:
https://github.com/apache/flink/pull/805#discussion_r32508286
--- Diff:
flink-staging/flink-scala-shell/src/main/scala/org.apache.flink/api/scala/FlinkShell.scala
---
@@ -44,6 +46,16 @@ object FlinkShell {
Github user nikste commented on a diff in the pull request:
https://github.com/apache/flink/pull/805#discussion_r32508271
--- Diff:
flink-staging/flink-scala-shell/src/main/scala/org.apache.flink/api/scala/FlinkILoop.scala
---
@@ -191,5 +203,14 @@ HINT: You can use print() on a Da
Github user nikste commented on a diff in the pull request:
https://github.com/apache/flink/pull/805#discussion_r32508276
--- Diff:
flink-staging/flink-scala-shell/src/main/scala/org.apache.flink/api/scala/FlinkShell.scala
---
@@ -30,7 +31,8 @@ object FlinkShell {
/
[
https://issues.apache.org/jira/browse/FLINK-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587794#comment-14587794
]
ASF GitHub Bot commented on FLINK-2178:
---
Github user andralungu commented on the pul
Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/799#issuecomment-112373119
PR updated to test the same issue in ApplyCoGroupFunctionOnAllEdges and
ApplyCoGroupFunction.
Also added tests.
---
If your project is set up for it, you can re
[
https://issues.apache.org/jira/browse/FLINK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587783#comment-14587783
]
Matthias J. Sax commented on FLINK-2218:
We are on the same page. One field for us
[
https://issues.apache.org/jira/browse/FLINK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned FLINK-2218:
--
Assignee: Matthias J. Sax
> Web client cannot specify parallelism
> ---
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587778#comment-14587778
]
Matthias J. Sax commented on FLINK-2232:
Hi, I guess, it is a "timing problem". Th
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587736#comment-14587736
]
Till Rohrmann commented on FLINK-2225:
--
It does not seem to be related to FLINK-2183
[
https://issues.apache.org/jira/browse/FLINK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann reassigned FLINK-2225:
Assignee: Till Rohrmann
> Erroneous scheduling of co-located tasks
> --
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587725#comment-14587725
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user mxm commented on the pull reque
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/834#issuecomment-112351299
Looks good. Thanks for addressing my concerns :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
[
https://issues.apache.org/jira/browse/FLINK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587722#comment-14587722
]
Ufuk Celebi commented on FLINK-2218:
I like the idea of separate fields. Makes it clea
[
https://issues.apache.org/jira/browse/FLINK-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587720#comment-14587720
]
ASF GitHub Bot commented on FLINK-2120:
---
Github user mxm commented on the pull reque
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/840#issuecomment-112349746
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wi
[
https://issues.apache.org/jira/browse/FLINK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587714#comment-14587714
]
Maximilian Michels commented on FLINK-2218:
---
My suggestion was to have a user ar
[
https://issues.apache.org/jira/browse/FLINK-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587702#comment-14587702
]
ASF GitHub Bot commented on FLINK-2229:
---
GitHub user sekruse opened a pull request:
GitHub user sekruse opened a pull request:
https://github.com/apache/flink/pull/842
[FLINK-2229] add equals(...) and hashCode() to ObjectArrayTypeInfo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sekruse/flink FLINK-2229
Alte
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/830#discussion_r32501088
--- Diff: flink-dist/src/main/flink-bin/LICENSE ---
@@ -254,20 +285,18 @@ under the Apache License (v 2.0):
The Apache Flink project bundles the
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/830#discussion_r32501126
--- Diff: flink-dist/src/main/flink-bin/NOTICE ---
@@ -407,3 +391,86 @@ LongAdder), which was released with the following
comments:
http://creati
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/830#discussion_r32500834
--- Diff: LICENSE ---
@@ -218,13 +218,9 @@ conditions of their respective licenses.
The Apache Flink project bundles the following files under the MIT
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/841#issuecomment-112338008
Merging
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
[
https://issues.apache.org/jira/browse/FLINK-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ufuk Celebi resolved FLINK-2219.
Resolution: Fixed
Fix Version/s: master
0.9
Fixed via f916819 (master), a3
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/830#discussion_r32500606
--- Diff: LICENSE ---
@@ -218,13 +218,9 @@ conditions of their respective licenses.
The Apache Flink project bundles the following files under the MIT
[
https://issues.apache.org/jira/browse/FLINK-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587677#comment-14587677
]
Márton Balassi commented on FLINK-2232:
---
The root cause seems to be a connection los
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587665#comment-14587665
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/834#issuecomment-112331072
Cool, this looks very nice.
@fhueske @mxm Any objections to me merging this?
---
If your project is set up for it, you can reply to this email and have your
rep
[
https://issues.apache.org/jira/browse/FLINK-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587659#comment-14587659
]
Aljoscha Krettek commented on FLINK-2230:
-
I wrote this on the mailing list, this
GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/841
[hotfix] Some small fixups in README.md
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink readme-fixups
Alternatively you can revi
Ufuk Celebi created FLINK-2232:
--
Summary: StormWordCountLocalITCase fails
Key: FLINK-2232
URL: https://issues.apache.org/jira/browse/FLINK-2232
Project: Flink
Issue Type: Bug
Component
[
https://issues.apache.org/jira/browse/FLINK-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Kruse reassigned FLINK-2229:
--
Assignee: Sebastian Kruse
> Data sets involving non-primitive arrays cannot be unioned
[
https://issues.apache.org/jira/browse/FLINK-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ufuk Celebi reassigned FLINK-2213:
--
Assignee: Ufuk Celebi
> Configure number of vcores
> --
>
>
[
https://issues.apache.org/jira/browse/FLINK-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587619#comment-14587619
]
Ufuk Celebi commented on FLINK-2213:
Yes, I'm looking into it today.
> Configure numb
Github user Shiti commented on the pull request:
https://github.com/apache/flink/pull/834#issuecomment-112319099
@aljoscha I updated the code
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have t
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587587#comment-14587587
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user Shiti commented on the pull req
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587580#comment-14587580
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user aljoscha commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587576#comment-14587576
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user aljoscha commented on a diff in
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/834#issuecomment-112316099
Very good, I would have forgotten about the test case with all-null values.
:smiley:
I only had a minor comment about Boolean.compare()
---
If your project is
[
https://issues.apache.org/jira/browse/FLINK-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587577#comment-14587577
]
ASF GitHub Bot commented on FLINK-2210:
---
Github user aljoscha commented on a diff in
1 - 100 of 103 matches
Mail list logo
