Hey everyone,
We are very excited to share the first stable draft of the Gelly blog post
with you :D
https://docs.google.com/document/d/1FMtpwKSE3kY7RfH082LzQpWrY6o-fdZVxqambIiC_rU/edit?usp=sharing
*Feedback* is welcome, as usual!
Andra
I've filed a JIRA to update the documentation:
https://issues.apache.org/jira/browse/FLINK-2092
On Fri, May 22, 2015 at 11:08 AM, Stephan Ewen se...@apache.org wrote:
Hi all!
Me merged a patch yesterday that changed the API behavior of the
DataSet.print() function.
print() now prints to
Ufuk Celebi created FLINK-2091:
--
Summary: Lock contention during release of network buffer pools
Key: FLINK-2091
URL: https://issues.apache.org/jira/browse/FLINK-2091
Project: Flink
Issue Type:
I second Aljoscha's and Matthias' opinion on the behavior of
`startNewChain()`. In the case of `setParallelism(..)`, we set the
parallelism of the operator but in case of `startNewChain()`, we explicitly
start a new chain; for the user, this is not connected to the previous
operation even though
Robert Metzger created FLINK-2092:
-
Summary: Document (new) behavior of print() and execute()
Key: FLINK-2092
URL: https://issues.apache.org/jira/browse/FLINK-2092
Project: Flink
Issue Type:
Andra Lungu created FLINK-2093:
--
Summary: Add a difference method to Gelly's Graph class
Key: FLINK-2093
URL: https://issues.apache.org/jira/browse/FLINK-2093
Project: Flink
Issue Type: New
Hi Max,
thanks for your feedback. I guess you confuse the interfaces Program
and ProgramDescription. Using Program the use of main method is
replaced by getPlan(...). However, ProgramDescription only adds
method getDescription() which returns a string that explains the usage
of the program (ie,
Wow, this is impressive :-)
Amazing work, Gelly folks!
On Tue, May 26, 2015 at 10:03 AM, Andra Lungu lungu.an...@gmail.com wrote:
Hey everyone,
We are very excited to share the first stable draft of the Gelly blog post
with you :D
Sorry, my bad. Yes, it is helpful to have a separate program and parameter
description in ProgramDescription. I'm not sure if it adds much value to
implement ProgramDescription in the examples. It introduces verbosity and
might give the impression that you have to implement ProgramDescription in
The streaming mode runs batch jobs as well :-)
There should be slightly reduced predictability in the memory management in
the streaming mode, but otherwise there should not be a problem.
So if you want to run mixed workloads, you start the streaming mode.
(Note: Currently, the batch mode runs
Ah yes, technically the streaming mode could run batch jobs as well in Flink.
I am thinking that it could cause confusion with users since most
systems that does batch and stream (well, pretty much Spark ^_^) does
not differentiate the deployment topologies for the cluster to support
different
Hi,
Flink's Table API is pretty close to what SQL provides. IMO, the best
approach would be to leverage that and build a SQL parser (maybe together
with a logical optimizer) on top of the Table API. Parser (and optimizer)
could be built using Apache Calcite which is providing exactly this.
Since
Fabian Hueske created FLINK-2095:
Summary: Screenshots missing in webcient documentation
Key: FLINK-2095
URL: https://issues.apache.org/jira/browse/FLINK-2095
Project: Flink
Issue Type: Bug
I see your point.
However, right now only few people are aware of ProgramDesciption
interface. If we want to advertise for it, it should be used (at
least) in a few examples. Otherwise, people will never use it, and the
changes I plan to apply are kind of useless. I would even claim, that
the
Hi,
currently, the only way to stop a streaming job is to cancel the job,
This has multiple disadvantage:
1) a clean stopping is not possible (see
https://issues.apache.org/jira/browse/FLINK-1929 -- I think a clean stop
is a pre-requirement for FLINK-1929) and
2) as a minor issue, all canceled
15 matches
Mail list logo
