Github user omnisis commented on the pull request:
https://github.com/apache/flink/pull/251#issuecomment-77671415
Whats the current status of this ticket? Starting to checkout Flink and
native Mesos support would be a huge win for my use case.
---
If your project is set up for it, y
Henry Saputra created FLINK-1659:
Summary: Rename classes and packages that contains Pact
Key: FLINK-1659
URL: https://issues.apache.org/jira/browse/FLINK-1659
Project: Flink
Issue Type: Task
GitHub user hsaputra opened a pull request:
https://github.com/apache/flink/pull/461
Fix checking null for ternary operator check on Exception#getMessage calls
Add parentheses on Exception#getMessage calls from pattern of:
"Initializing the input processing failed" + e.getM
[
https://issues.apache.org/jira/browse/FLINK-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Saputra reassigned FLINK-1651:
Assignee: Henry Saputra
> Running mvn test got stuck
> --
>
>
[
https://issues.apache.org/jira/browse/FLINK-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351097#comment-14351097
]
ASF GitHub Bot commented on FLINK-1651:
---
GitHub user hsaputra opened a pull request:
GitHub user hsaputra opened a pull request:
https://github.com/apache/flink/pull/460
[FLINK-1651] Fix test case at JobManagerStartupTest to avoid hang on
certain users
JobManagerStartupTest should not assume user could not create
/does-not-exist-no-sir dir.
Sometimes, user
[
https://issues.apache.org/jira/browse/FLINK-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350926#comment-14350926
]
Robert Metzger commented on FLINK-1629:
---
For everyone who's ever facing issues stopp
[
https://issues.apache.org/jira/browse/FLINK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350558#comment-14350558
]
Vasia Kalavri commented on FLINK-1536:
--
Hi [~ayd]!
As a first step, it would be nice
Github user fpompermaier commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77586066
That would be awesome :)
I think you could talk with Markus about the Dopa scheduler..propably it's
a closed project but it could be a source of inputs to create a
[
https://issues.apache.org/jira/browse/FLINK-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350469#comment-14350469
]
Ufuk Celebi commented on FLINK-1658:
I agree. Please wait with the renaming till after
Gyula Fora created FLINK-1658:
-
Summary: Rename AbstractEvent to AbstractTaskEvent and
AbstractJobEvent
Key: FLINK-1658
URL: https://issues.apache.org/jira/browse/FLINK-1658
Project: Flink
Issue
[
https://issues.apache.org/jira/browse/FLINK-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1648.
-
Resolution: Implemented
Implemented in d8d642fd6d7d9b8526325d4efff1015f636c5ddb
> Add a mode wher
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77569539
I think it would be definitely good to have something like a job submission
queue, that accepts jobs and executes them as soon as enough as enough
resource become av
[
https://issues.apache.org/jira/browse/FLINK-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350263#comment-14350263
]
Fabian Hueske commented on FLINK-1656:
--
Right, that's a good point.
+1 limiting to ke
[
https://issues.apache.org/jira/browse/FLINK-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350262#comment-14350262
]
Fabian Hueske commented on FLINK-1656:
--
Comment by [~StephanEwen] copied from dev mai
Gyula Fora created FLINK-1657:
-
Summary: Make count windows local automatically
Key: FLINK-1657
URL: https://issues.apache.org/jira/browse/FLINK-1657
Project: Flink
Issue Type: Improvement
Github user senorcarbone commented on the pull request:
https://github.com/apache/flink/pull/459#issuecomment-77538649
hold on, will commit an update very soon. :P
---
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 p
GitHub user mbalassi opened a pull request:
https://github.com/apache/flink/pull/459
[streaming] [wip] Fault tolerance prototype (for limited case)
This is the first limited case streaming prototype. The intention is to
provide at least once processing for both states and messages f
Fabian Hueske created FLINK-1656:
Summary: Fix ForwardedField documentation for operators with
iterator input
Key: FLINK-1656
URL: https://issues.apache.org/jira/browse/FLINK-1656
Project: Flink
Github user fpompermaier commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77537609
I know that in stratosphere there was an effort to write a job scheduler,
do you think that such a thing could be valuable for the future or are you
going to rely onl
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77536080
At the moment, this is not supported yet. The easiest way to execute
multiple jobs concurrently is to start each job in a separate Flink cluster
running on YARN
Github user fpompermaier commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77533354
That's true but what if there's not enough resources? Is there any policy
to retry the job submission automatically or give priority to waiting/queued
ones?
---
If
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77530332
Hey,
Flink already supports running multiple jobs in parallel.
If you have 50 slots available, you can run two jobs requiring 25 slots.
The webfrontend is not r
Github user fpompermaier commented on the pull request:
https://github.com/apache/flink/pull/410#issuecomment-77529565
Hi to all,
I was reading this interesting thread..is there any change that
multi-user/multi-job scenarios will come into play sooner or later? Or do you
just rely
24 matches
Mail list logo