Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/296#issuecomment-69970228
How about setting the message to something like
Warning: You are running Flink with Java 6, which is not maintained any
more by Oracle or the OpenJDK
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277647#comment-14277647
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user aljoscha commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277522#comment-14277522
]
Stephan Ewen commented on FLINK-1400:
-
I think you can also locally start a job
Github user hsaputra commented on the pull request:
https://github.com/apache/flink/pull/306#issuecomment-69967270
Ah ok, thanks for the info Stephen, good to know it was intentional.
Do you want to keep this pattern?
---
If your project is set up for it, you can reply to this
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277644#comment-14277644
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user rmetzger commented on a diff in
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/304#discussion_r22968592
--- Diff: flink-java/pom.xml ---
@@ -64,6 +64,18 @@ under the License.
version0.5.1/version
/dependency
+
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277526#comment-14277526
]
ASF GitHub Bot commented on FLINK-1398:
---
Github user rmetzger commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277635#comment-14277635
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user aljoscha commented on a diff in
[
https://issues.apache.org/jira/browse/FLINK-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277455#comment-14277455
]
ASF GitHub Bot commented on FLINK-1183:
---
Github user hsaputra commented on the pull
Github user hsaputra commented on the pull request:
https://github.com/apache/flink/pull/296#issuecomment-69971212
+1 gentler and informative =)
---
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 rmetzger commented on the pull request:
https://github.com/apache/flink/pull/308#issuecomment-69976328
+1 for some utilities.
I'm not sure however where to put it.
Should we add another maven module? Make it part of the current
flink-java ? Or start it as a github
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277634#comment-14277634
]
ASF GitHub Bot commented on FLINK-1395:
---
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/304#discussion_r22968293
--- Diff:
flink-core/src/test/java/org/apache/flink/api/common/typeutils/SerializerTestBase.java
---
@@ -99,6 +104,7 @@ public void testCopy() {
Github user hsaputra commented on the pull request:
https://github.com/apache/flink/pull/306#issuecomment-69992202
I don't remember if there any best practice about this, so If we think it
is useful we could keep this style and maybe document it?
But I don't think it is good
[
https://issues.apache.org/jira/browse/FLINK-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277061#comment-14277061
]
Gyula Fora commented on FLINK-1381:
---
Hey,
So the problem is that the splitting is tied
Ufuk Celebi created FLINK-1404:
--
Summary: Trigger recycling of buffers held by historic
intermediate result partitions
Key: FLINK-1404
URL: https://issues.apache.org/jira/browse/FLINK-1404
Project:
[
https://issues.apache.org/jira/browse/FLINK-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277073#comment-14277073
]
Márton Balassi commented on FLINK-1403:
---
Hey,
Thanks for posting the issue. We have
[
https://issues.apache.org/jira/browse/FLINK-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276984#comment-14276984
]
Mingliang Qi commented on FLINK-1381:
-
Is there any problem of moving the split
[
https://issues.apache.org/jira/browse/FLINK-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278333#comment-14278333
]
ASF GitHub Bot commented on FLINK-1388:
---
GitHub user msdevanms opened a pull
[
https://issues.apache.org/jira/browse/FLINK-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278338#comment-14278338
]
ASF GitHub Bot commented on FLINK-1183:
---
Github user ajaybhat commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277105#comment-14277105
]
ASF GitHub Bot commented on FLINK-1398:
---
GitHub user FelixNeutatz opened a pull
GitHub user FelixNeutatz opened a pull request:
https://github.com/apache/flink/pull/308
[FLINK-1398] Introduce extractSingleField() in DataSet
This is a prototype how we could implement extractSingleField() for
DataSet. Let's discuss :)
You can merge this pull request into a Git
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277141#comment-14277141
]
ASF GitHub Bot commented on FLINK-1398:
---
Github user zentol commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277304#comment-14277304
]
ASF GitHub Bot commented on FLINK-1376:
---
Github user tillrohrmann commented on the
Github user tillrohrmann closed the pull request at:
https://github.com/apache/flink/pull/300
---
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
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/304#discussion_r22955775
--- Diff:
flink-core/src/test/java/org/apache/flink/api/common/typeutils/SerializerTestBase.java
---
@@ -99,6 +104,7 @@ public void testCopy() {
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277226#comment-14277226
]
Fabian Hueske commented on FLINK-1398:
--
I am not sure how useful / how much needed
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/304#discussion_r22956572
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/KryoGenericTypeSerializerTest.scala
---
@@ -125,6 +133,7 @@ class
[
https://issues.apache.org/jira/browse/FLINK-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Neutatz reassigned FLINK-1398:
Assignee: Felix Neutatz
A new DataSet function: extractElementFromTuple
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277379#comment-14277379
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user StephanEwen commented on the
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/309
[FLINK-1376] [runtime] Add proper shared slot release in case of a fatal
TaskManager failure
This PR introduces SharedSlots as being a special Slot type and as such
being released properly in
[
https://issues.apache.org/jira/browse/FLINK-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277385#comment-14277385
]
ASF GitHub Bot commented on FLINK-1376:
---
GitHub user tillrohrmann opened a pull
[
https://issues.apache.org/jira/browse/FLINK-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277415#comment-14277415
]
ASF GitHub Bot commented on FLINK-1402:
---
Github user hsaputra commented on the pull
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/307#issuecomment-69967981
This change looks good 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
[
https://issues.apache.org/jira/browse/FLINK-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276888#comment-14276888
]
ASF GitHub Bot commented on FLINK-1389:
---
Github user rmetzger commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276744#comment-14276744
]
ASF GitHub Bot commented on FLINK-1399:
---
Github user uce commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276731#comment-14276731
]
Aljoscha Krettek commented on FLINK-1400:
-
You can, with a hack. You start a
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/305#issuecomment-69896090
The second option (env) is probably better because people will see the
method when their IDE suggests method names.
---
If your project is set up for it, you can reply
[
https://issues.apache.org/jira/browse/FLINK-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276911#comment-14276911
]
ASF GitHub Bot commented on FLINK-1320:
---
Github user mxm commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276923#comment-14276923
]
ASF GitHub Bot commented on FLINK-1320:
---
Github user mxm commented on the pull
40 matches
Mail list logo
