I recommend multiple Jobs. You can still share most of the code by creating
Java / Scala packages. THis makes it easier to update Jobs.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Many-streaming-jobs-vs-one-tp11449p11450.html
Sent from th
Hi,
I am running a flink cluster to process clickstream data (generate user
level, page level, site level statistics)
I want to understand the cons and pros of submitting multiple jobs (each
job handles one simple processing/computation) vs one/few complex jobs. At
present, the events are read
https://www.discourse.org/about/ for the features
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/How-about-Discourse-https-www-discourse-org-for-this-mailing-list-tp11448.html
Sent from the Apache Flink User Mailing List archive. mailing lis
Using a profiler I found out that the main performance problem (80%) was
spent in a domain specific data structure. After implementing it with a more
efficient one, the performance problems are gone.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabbl
Hi,
Looking forward to 1.2 version of Flink (lots of exciting features have
been added).
Has the date finalized yet?
Thanks,
Tarandeep
Hi,
On quickstart page of Flink docs, it suggests starting a Flink app with
"bin/flink" command on command line. Is there any other way of submitting
to a cluster of flink, that is, through API call within a program, or
through server request?
Thanks,
Luqman
I really don't know what you mean, I've been reading the documentation and
examples showing iterations. but it just won't work for me I believe. Maybe
you can write a quick example? It doesn't matter the details, only the
topology.
If anyone else has an idea it's very welcome!
Matt
On Tue, Jan 3
