Stephan Ewen created FLINK-1418:
---
Summary: Make 'print()' output on the client command line, rather
than on the task manager sysout
Key: FLINK-1418
URL: https://issues.apache.org/jira/browse/FLINK-1418
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/297#issuecomment-70413324
Thanks for taking a go at this. It is going into a good direction.
What needs to be adjusted is the way that the job manager gets accessed.
The current
[
https://issues.apache.org/jira/browse/FLINK-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281843#comment-14281843
]
Stephan Ewen commented on FLINK-1372:
-
This should be fixed with some priority,
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/308#issuecomment-70413423
@StephanEwen would that look like this?
```java
reverse(dataset.map(...)).filter(...)
```
Ive been thinking about the API overload issue a bit: could a
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/236#issuecomment-70413969
Two questions relevant to the interplay with other code:
- How does the `registerType()` interact with the registration of custom
kryo serializers?
- Why
[
https://issues.apache.org/jira/browse/FLINK-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1384.
-
Resolution: Fixed
Removed in 0.9 in f38e2039969f613c18edda2528e4e7b5018d46ad
Web Infoserver has
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/298#issuecomment-70421138
I addressed the comments and committed the changes to the 0.9 master. I
forgot to add the This closes #298 message, thought. Marton, can you close
this Pull Request
[
https://issues.apache.org/jira/browse/FLINK-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1400.
-
Resolution: Won't Fix
This is expected behavior:
- A single task manager in local mode does not
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/291
---
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 asfgit closed the pull request at:
https://github.com/apache/flink/pull/299
---
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 a diff in the pull request:
https://github.com/apache/flink/pull/311#discussion_r23135998
--- Diff:
flink-core/src/main/java/org/apache/flink/api/common/operators/DualInputSemanticProperties.java
---
@@ -56,218 +56,135 @@
[
https://issues.apache.org/jira/browse/FLINK-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281927#comment-14281927
]
Stephan Ewen commented on FLINK-655:
I think it is fine to add functions for scalar
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/291#issuecomment-70415920
Looks good to be merged, in my opinion!
---
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 tillrohrmann closed the pull request at:
https://github.com/apache/flink/pull/310
---
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 tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/309#issuecomment-70417368
Found an issue with the releasing of colocated task slots and the disposal
of shared slots for colocation groups. Will open a new PR with fix and rebased
code.
---
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/294#issuecomment-70418596
The changes have been merged to 0.8 and master (except for FLINK-1385, but
this fix needs to be implemented differently for master. I'll do that as part
of my yarn pull
Github user rmetzger closed the pull request at:
https://github.com/apache/flink/pull/294
---
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 tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/317
[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
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/318
[FLINK-1376] [runtime] Add proper shared slot release in case of a fatal
TaskManager failure for 0.8 branch
This PR introduces SharedSlots as being a special Slot type and as such
being
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/292#issuecomment-70415876
A good piece of work!. I like that there is a much better test coverage for
the Yarn cluster now.
@rmetzger Can you comment on a few open questions?
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/305#issuecomment-70416371
This would do it for now. However, the use of static variables to
communicate between components is an antipattern and one that has caused
problems before. I would
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/292#issuecomment-70416726
Thank you for the feedback. I'll address the inline comments.
Regarding the questions:
1. The separation between `flink-yarn` and `flink-yarn-tests` exists
Github user physikerwelt closed the pull request at:
https://github.com/apache/flink/pull/161
---
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
[
https://issues.apache.org/jira/browse/FLINK-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281857#comment-14281857
]
Robert Metzger commented on FLINK-1411:
---
+1 for hosting the tool on the website
Robert Metzger created FLINK-1413:
-
Summary: Add option to YARN client to use already deployed
uberjar/flink files instead of redeploying on each YARN session
Key: FLINK-1413
URL:
Stephan Ewen created FLINK-1417:
---
Summary: Automatically register nested types at Kryo
Key: FLINK-1417
URL: https://issues.apache.org/jira/browse/FLINK-1417
Project: Flink
Issue Type:
Github user mbalassi closed the pull request at:
https://github.com/apache/flink/pull/298
---
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 mbalassi commented on the pull request:
https://github.com/apache/flink/pull/298#issuecomment-70429116
Thanks, done.
---
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
Robert Metzger created FLINK-1414:
-
Summary: Remove quickstart-*.sh from git source and put them to
the website's svn
Key: FLINK-1414
URL: https://issues.apache.org/jira/browse/FLINK-1414
Project:
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/305#issuecomment-70424146
The registration at Kryo seems to be a bit incomplete. Adding a default
serializer does not to type/tag registration, which is very much desirable.
Also, it registers
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/305#issuecomment-70424921
Maybe we should offer users both options: register and default serializer.
In some cases, you don't know the exact types and you want to go for a
default serializer.
31 matches
Mail list logo