[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509139#comment-14509139
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user Elbehery commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509282#comment-14509282
]
Alexander Alexandrov commented on FLINK-1848:
-
I think this should be fixed
Github user Elbehery commented on the pull request:
https://github.com/apache/flink/pull/442#issuecomment-95603365
@aljoscha you should be able to see it from the PR .. anyway this is mine
https://github.com/Elbehery/flink
---
If your project is set up for it, you can reply to this
[
https://issues.apache.org/jira/browse/FLINK-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509134#comment-14509134
]
ASF GitHub Bot commented on FLINK-1828:
---
Github user fpompermaier commented on a
[
https://issues.apache.org/jira/browse/FLINK-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509442#comment-14509442
]
ASF GitHub Bot commented on FLINK-1693:
---
Github user vasia commented on the pull
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/618#issuecomment-95668944
Thank you @hsaputra! Looks good :-)
---
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
Github user fpompermaier commented on a diff in the pull request:
https://github.com/apache/flink/pull/571#discussion_r28966088
--- Diff: flink-staging/flink-hbase/pom.xml ---
@@ -112,6 +112,12 @@ under the License.
/exclusion
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509090#comment-14509090
]
ASF GitHub Bot commented on FLINK-1930:
---
Github user StephanEwen commented on the
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509091#comment-14509091
]
ASF GitHub Bot commented on FLINK-1930:
---
Github user StephanEwen closed the pull
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509097#comment-14509097
]
Stephan Ewen commented on FLINK-1930:
-
Should give better error messages now.
Please
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/619#issuecomment-95593489
Manually merged in 4dbf030a6b0415832862c3fd0c3fe7403878a998
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509124#comment-14509124
]
Vasia Kalavri commented on FLINK-1930:
--
Ok, so now the program fails with this:
[
https://issues.apache.org/jira/browse/FLINK-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger reassigned FLINK-1865:
-
Assignee: Robert Metzger (was: Márton Balassi)
Unstable test KafkaITCase
[
https://issues.apache.org/jira/browse/FLINK-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger reassigned FLINK-1921:
-
Assignee: Robert Metzger
Rework parallelism/slots handling for per-job YARN sessions
[
https://issues.apache.org/jira/browse/FLINK-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger reassigned FLINK-1920:
-
Assignee: Robert Metzger
Passing -D akka.ask.timeout=5 min to yarn client does not work
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508978#comment-14508978
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/442#issuecomment-95570894
Where is your git repository? So that I can checkout your commit and merge
it?
---
If your project is set up for it, you can reply to this email and have your
reply
Robert Metzger created FLINK-1935:
-
Summary: Reimplement PersistentKafkaSource using high level Kafka
API
Key: FLINK-1935
URL: https://issues.apache.org/jira/browse/FLINK-1935
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509002#comment-14509002
]
ASF GitHub Bot commented on FLINK-1398:
---
Github user StephanEwen commented on the
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/308#issuecomment-95577570
+1 for not specializing code in the `DataSet`
A `TupleUtil` would be fine, in my opinion
---
If your project is set up for it, you can reply to this email
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/439#issuecomment-95579057
I agree to enforce normalization in the `ConfigConstants`, by adding a test
case that reflectively gets all fields and checks whether they start with
DEFAULT_ or end
[
https://issues.apache.org/jira/browse/FLINK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509006#comment-14509006
]
ASF GitHub Bot commented on FLINK-1472:
---
Github user StephanEwen commented on the
[
https://issues.apache.org/jira/browse/FLINK-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508609#comment-14508609
]
Till Rohrmann commented on FLINK-1745:
--
That sounds really good [~chiwanpark] and
[
https://issues.apache.org/jira/browse/FLINK-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508612#comment-14508612
]
Till Rohrmann commented on FLINK-1933:
--
Good selection of distance measures. Should
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508635#comment-14508635
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on a diff in
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28943704
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/jobmanager/JobManagerFailsITCase.scala
---
@@ -18,24 +18,23 @@
package
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels resolved FLINK-1486.
---
Resolution: Implemented
Add a string to the print method to identify output
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508743#comment-14508743
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user Elbehery commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508643#comment-14508643
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on a diff in
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28943849
--- Diff:
flink-tests/src/test/java/org/apache/flink/test/recovery/AbstractProcessFailureRecoveryTest.java
---
@@ -112,9 +112,9 @@ public void
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28943875
--- Diff:
flink-tests/src/test/java/org/apache/flink/test/recovery/AbstractProcessFailureRecoveryTest.java
---
@@ -112,9 +112,9 @@ public void
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28943824
--- Diff:
flink-tests/src/test/java/org/apache/flink/test/recovery/AbstractProcessFailureRecoveryTest.java
---
@@ -112,9 +112,9 @@ public void
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508645#comment-14508645
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on a diff in
[
https://issues.apache.org/jira/browse/FLINK-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508652#comment-14508652
]
Gianmarco De Francisci Morales commented on FLINK-1725:
---
Hi,
The
Github user Elbehery commented on the pull request:
https://github.com/apache/flink/pull/442#issuecomment-95512206
I did rebase against the master before creating the PR .. but this was long
time ago, could this be the problems for the conflicts ?!!
---
If your project is set up for
[
https://issues.apache.org/jira/browse/FLINK-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508619#comment-14508619
]
ASF GitHub Bot commented on FLINK-1792:
---
Github user bhatsachin commented on the
Github user bhatsachin commented on the pull request:
https://github.com/apache/flink/pull/553#issuecomment-95480100
The suggested changes have been made
---
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
[
https://issues.apache.org/jira/browse/FLINK-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-1745:
-
Summary: Add exact k-nearest-neighbours algorithm to machine learning
library (was: Add
[
https://issues.apache.org/jira/browse/FLINK-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-1745:
-
Description:
Even though the k-nearest-neighbours (kNN) [1,2] algorithm is quite trivial it
is
[
https://issues.apache.org/jira/browse/FLINK-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-1745:
-
Description:
Even though the k-nearest-neighbours (kNN) [1,2] algorithm is quite trivial it
is
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508637#comment-14508637
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on a diff in
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28943731
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/jobmanager/JobManagerFailsITCase.scala
---
@@ -136,9 +135,9 @@ with WordSpecLike
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508638#comment-14508638
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on a diff in
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/593#issuecomment-95500680
This does not work if the user uses classes that are not available on the
local machine since you don't add the additional class path entries in
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/582
---
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 aljoscha commented on the pull request:
https://github.com/apache/flink/pull/442#issuecomment-95511047
This looks good to merge. Any objections?
---
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
[
https://issues.apache.org/jira/browse/FLINK-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508606#comment-14508606
]
Till Rohrmann commented on FLINK-1745:
--
I agree with grouping the nearest neighbours
Till Rohrmann created FLINK-1934:
Summary: Add approximative k-nearest-neighbours (kNN) algorithm to
machine learning library
Key: FLINK-1934
URL: https://issues.apache.org/jira/browse/FLINK-1934
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28943598
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/taskmanager/TaskManagerFailsITCase.scala
---
@@ -231,9 +231,9 @@ with WordSpecLike
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508648#comment-14508648
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on a diff in
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/372#issuecomment-95488183
Do we want to break backwards compatibility or include a new method for
printing on the client? After all, printing on the workers is a useful tool to
debug the dataflow of a
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508656#comment-14508656
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user mxm commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508704#comment-14508704
]
ASF GitHub Bot commented on FLINK-1789:
---
Github user aljoscha commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek resolved FLINK-1799.
-
Resolution: Fixed
Fixed in
[
https://issues.apache.org/jira/browse/FLINK-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508721#comment-14508721
]
ASF GitHub Bot commented on FLINK-1799:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508741#comment-14508741
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user aljoscha commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508774#comment-14508774
]
ASF GitHub Bot commented on FLINK-1398:
---
Github user rmetzger commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508778#comment-14508778
]
ASF GitHub Bot commented on FLINK-1472:
---
Github user qmlmoon commented on the pull
Github user ggevay commented on the pull request:
https://github.com/apache/flink/pull/581#issuecomment-95523580
OK, I see your point. I am thinking about using
NetUtils.findConnectingAddress to determine which interface is used for the
communication with the cluster. For this, I
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508751#comment-14508751
]
ASF GitHub Bot commented on FLINK-1930:
---
GitHub user StephanEwen opened a pull
[
https://issues.apache.org/jira/browse/FLINK-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghav Chalapathy reassigned FLINK-1934:
Assignee: Raghav Chalapathy
Add approximative k-nearest-neighbours (kNN)
Github user uce closed the pull request at:
https://github.com/apache/flink/pull/617
---
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 enabled
GitHub user uce reopened a pull request:
https://github.com/apache/flink/pull/617
[runtime] Bump Netty version to 4.27.Final and add javassist
@rmetzger, javassist is set in the root POM. Is it OK to leave it in
flink-runtime as I have it now w/o version?
You can merge this pull
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/619#issuecomment-95517313
@uce Do you see any further implications to the network stack via this
change (exception instead of null)
---
If your project is set up for it, you can reply to this
GitHub user StephanEwen opened a pull request:
https://github.com/apache/flink/pull/619
[FLINK-1930] [runtime] Improve exception when bufferpools have been shutdown
You can merge this pull request into a Git repository by running:
$ git pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/439#issuecomment-95517673
Hi,
sorry for the long wait on this. I really like the feature but the
implementation is not scalable: If new config values are added this needs to be
updated in
[
https://issues.apache.org/jira/browse/FLINK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508756#comment-14508756
]
ASF GitHub Bot commented on FLINK-1472:
---
Github user aljoscha commented on the pull
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/308#issuecomment-95522921
I would put this into the `flink-contrib` module.
---
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
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/308#issuecomment-95523597
@aljoscha Those are good points. I like the idea of cleaning the Java and
Scala APIs from operations that work on structured data such as projection,
aggregation, etc.
[
https://issues.apache.org/jira/browse/FLINK-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508781#comment-14508781
]
ASF GitHub Bot commented on FLINK-1670:
---
Github user ggevay commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508782#comment-14508782
]
ASF GitHub Bot commented on FLINK-1398:
---
Github user fhueske commented on the pull
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/581#issuecomment-95528015
`NetUtils.findConnectingAddress` is a useful util, when you know that the
endpoint is up already. If you can make the assumption that the master is
running already
[
https://issues.apache.org/jira/browse/FLINK-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508803#comment-14508803
]
ASF GitHub Bot commented on FLINK-1670:
---
Github user StephanEwen commented on the
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/593#issuecomment-95564844
Yes, this is true, but the way it is implemented, the folders are not
always added to the class loader. Maybe I'm wrong here, but
JobWithJars.getUserCodeClassLoader and
[
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508954#comment-14508954
]
ASF GitHub Bot commented on FLINK-1789:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/308#issuecomment-95566780
Yes, I think we should start a discussion there. I just wanted to give the
reasons for my opinion here.
---
If your project is set up for it, you can reply to this
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508957#comment-14508957
]
ASF GitHub Bot commented on FLINK-1398:
---
Github user aljoscha commented on the pull
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/48#issuecomment-95579798
Thanks for the PR. I've looked into the other approach (#248) and I think
you can safely close this on now.
---
If your project is set up for it, you can reply to this email
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509016#comment-14509016
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user StephanEwen commented on the
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/372#issuecomment-95580456
From what I have seen, most people expect print() to actually go to the
client.
It would be a break of backwards compatibility, agreed. Maybe one of the
few that
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509029#comment-14509029
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user StephanEwen commented on a diff
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/439#issuecomment-95580562
Yes, but then we should change this now and not build more code on top of
this that can fail in the future if someone forgets to add the names to the
correct hash set in
[
https://issues.apache.org/jira/browse/FLINK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509032#comment-14509032
]
ASF GitHub Bot commented on FLINK-1472:
---
Github user aljoscha commented on the pull
Aljoscha Krettek created FLINK-1936:
---
Summary: Normalize keys and default values in ConfigConstants.java
Key: FLINK-1936
URL: https://issues.apache.org/jira/browse/FLINK-1936
Project: Flink
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/439#issuecomment-95581307
I added a Jira for this: https://issues.apache.org/jira/browse/FLINK-1936
---
If your project is set up for it, you can reply to this email and have your
reply appear on
[
https://issues.apache.org/jira/browse/FLINK-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509034#comment-14509034
]
ASF GitHub Bot commented on FLINK-1828:
---
Github user StephanEwen commented on a diff
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509039#comment-14509039
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user mxm commented on the pull
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-95586174
I've rebased this on the current master, added log messages when falling
back to the default address (which I've renamed as Till suggested), and tested
it.
There is
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509051#comment-14509051
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user StephanEwen commented on the
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/35#issuecomment-95590430
Hi @qmlmoon,
sorry for the long wait on this PR. Could you please rebase on top of the
current master and also get rid of the merge commits in the process?
---
If
[
https://issues.apache.org/jira/browse/FLINK-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509075#comment-14509075
]
ASF GitHub Bot commented on FLINK-924:
--
Github user aljoscha commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509010#comment-14509010
]
ASF GitHub Bot commented on FLINK-938:
--
Github user uce commented on the pull request:
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/372#issuecomment-95580149
Can you think of a case where printing on the client is worse than printing
on worker?
---
If your project is set up for it, you can reply to this email and have
Github user qmlmoon closed the pull request at:
https://github.com/apache/flink/pull/48
---
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
[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509013#comment-14509013
]
ASF GitHub Bot commented on FLINK-938:
--
Github user qmlmoon closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509012#comment-14509012
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user StephanEwen commented on the
[
https://issues.apache.org/jira/browse/FLINK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509017#comment-14509017
]
ASF GitHub Bot commented on FLINK-1472:
---
Github user aljoscha commented on the pull
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28961064
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/taskmanager/TaskManagerFailsITCase.scala
---
@@ -231,9 +231,9 @@ with
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/571#discussion_r28961417
--- Diff: flink-staging/flink-hbase/pom.xml ---
@@ -112,6 +112,12 @@ under the License.
/exclusion
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28961799
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/taskmanager/TaskManagerFailsITCase.scala
---
@@ -231,9 +231,9 @@ with WordSpecLike
1 - 100 of 110 matches
Mail list logo
