+1
On Mon, Jul 29, 2019 at 11:06 AM Jeff Zhang wrote:
> +1 to remove it.
>
> Aljoscha Krettek 于2019年7月29日周一 下午5:01写道：
>
> > Hi,
> >
> > Because of recent problems in the dependencies of that module [1] I would
> > suggest that we remove it. If people are using it, they can use the one
> > from
Thanks for checking. No concerns on my side. +1 to back port. Fixing fault
tolerance of streaming iterations sounds like a very valuable thing to
unblock with this release.
– Ufuk
On Thu, Aug 1, 2019 at 11:02 AM Stephan Ewen wrote:
> Hi all!
>
> I would like to backport a minor chance from 'ma
+1 (binding)
– Ufuk
On Wed, Aug 14, 2019 at 4:50 AM Biao Liu wrote:
> +1 (non-binding)
>
> Thanks for pushing this!
>
> Thanks,
> Biao /'bɪ.aʊ/
>
>
>
> On Wed, 14 Aug 2019 at 09:37, Jark Wu wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Jark
> >
> > On Wed, 14 Aug 2019 at 09:22, Kurt Young
I'm late to the party... Welcome and congrats! :-)
– Ufuk
On Mon, Aug 19, 2019 at 9:26 AM Andrey Zagrebin
wrote:
> Hi Everybody!
>
> Thanks a lot for the warn welcome!
> I am really happy about joining Flink committer team and hope to help the
> project to grow more.
>
> Cheers,
> Andrey
>
> O
+1 to have the README as source of truth and link to the repository from
the Wiki page.
– Ufuk
On Mon, Feb 10, 2020 at 3:48 AM Yang Wang wrote:
> +1 to make flink-docker repository self-contained, including the document.
> And others refer
> to it.
>
>
> Best,
> Yang
>
> Till Rohrmann 于2020年2
Hey Chensay,
+1 (binding).
- Verified checksum ✅
- Verified signature ✅
- Jira changelog looks good to me ✅
- Website PR looks good to me ✅
- Verified no unshaded dependencies (except the Hadoop modules which I
think is expected) ✅
- Verified dependency management fix FLINK-15540 (commons-collect
PS: Also verified the NOTICE changes since the last RC.
On Thu, Feb 13, 2020 at 5:25 PM Ufuk Celebi wrote:
> Hey Chensay,
>
> +1 (binding).
>
> - Verified checksum ✅
> - Verified signature ✅
> - Jira changelog looks good to me ✅
> - Website PR looks good to me ✅
I'd be happy to read such a blog. Big +1 as a potential reader. ;-)
– Ufuk
On Mon, Mar 2, 2020 at 11:53 AM Arvid Heise wrote:
> Dear devs,
>
> development speed of Flink has steadily increased. Lots of new concepts are
> introduced and technical debt removed. However, it's hard to keep track o
t;> - Scheduling
> > >>>>>>>> - Cluster partitions
> > >>>>>>>> - Memory configuration
> > >>>>>>>> - Recovery
> > >>>>>>>>
> > >>>>>>>> Cheers,
> > >&
+1.
The repo creation process is a light-weight, automated process on the ASF
side. When Patrick Lucas contributed docker-flink back to the Flink
community (as flink-docker), there was virtually no overhead in creating
the repository. Reusing build scripts should still be possible at the cost
of s
Hey all,
thanks for the proposal and the detailed discussion. In particular, thanks
to Andrey for starting this thread and to Patrick for the additional ideas
in the linked Google doc.
I find many of the improvements proposed during the discussion (such as the
unified entrypoint in Flink, proper
Hey Yang,
thanks! See inline answers.
On Fri, Apr 3, 2020 at 5:11 AM Yang Wang wrote:
> Hi Ufuk,
>
> Thanks for make the conclusion and directly point out what need to be done
> in
> FLIP-111. I agree with you that we should narrow down the scope and focus
> the
> most important and basic part
ions of docker image.
>
> # Dockerfile / image for developers
> We keep it on our future roadmap. This effort should help to understand
> what we can reuse there.
>
> Best,
> Andrey
>
>
> On Fri, Apr 3, 2020 at 12:57 PM Till Rohrmann
> wrote:
>
>> Hi
Thanks for starting this FLIP.
+1
On Tue, Apr 7, 2020 at 11:29 AM Andrey Zagrebin
wrote:
> Hi All,
>
> As discussed in these threads [1] and [2],
> we suggest to unify the docker topic in Flink for users [3].
>
> This mainly means refactoring of the existing code and introducing more
> docs as
+1 (binding)
- checked release notes ✅
- verified sums and hashes ✅
- verified no binary artifacts in source release ✅
- reviewed website PR ✅
- built from source ✅
- built an internal Flink distribution based on the 1.9.3-rc1 commit ✅
- built internal jobs against the staging repo ✅
- deployed th
+1 (binding)
On Fri, Oct 25, 2019 at 6:39 PM Maximilian Michels wrote:
> +1 (binding)
>
> On 25.10.19 14:31, Congxian Qiu wrote:
> > +1 (non-biding)
> > Best,
> > Congxian
> >
> >
> > Terry Wang 于2019年10月24日周四 上午11:15写道：
> >
> >> +1 (non-biding)
> >>
> >> Best,
> >> Terry Wang
> >>
> >>
> >>
>
The opt-in approach seems reasonable to me. +1 to include the profiles in
1.8 and 1.9 without changing the default versions (including the default
version of flink-shaded).
As far as I can tell, the next steps would be:
1) Release flink-shaded with upgraded Jackson
2a) Bump the flink-shaded versi
>From what I can see, the Jackson version bump fixes quite a few
vulnerabilities. Therefore, I'd be +1 to release flink-shaded 9.0.
Thanks for all the work to verify this on master already.
– Ufuk
On Fri, Nov 15, 2019 at 2:26 PM Chesnay Schepler wrote:
> Hello,
>
> I'd like to kick off the ne
ion: the flink-shaded upgrade does not have to be
> >>>> part of the profile; since it is only intended for internal use anyway
> >>>> (and thus has limited exposure) we can be pretty sure this doesn't
> break
> >>>> anything.
> >>>>
ve these security vulnerabilities.
>
> Thanks a lot for your nice work and kick off the release so quickly.
>
>
> On Fri, Nov 15, 2019 at 11:50 PM Ufuk Celebi wrote:
>
> > From what I can see, the Jackson version bump fixes quite a few
> > vulnerabilities. T
+1 (binding)
* built master against flink-shaded 9.0 and jackson 2.10.1 (via
https://repository.apache.org/content/repositories/orgapacheflink-1275)
- code: https://github.com/uce/flink/tree/flink-shaded-9.0
- travis: https://travis-ci.org/uce/flink/builds/615013399
* ran examples against web
; checking can cause severe
> >> performance issues for large scale jobs. So I hope the fix could be
> >> released with 1.8.3.
> >>
> >> The fix is already merged into master, and is now in the process of
> >> backporting to 1.8.
> >>
> >&g
+1 to drop the MapR page.
For the other two I'm +0. I fully agree that the linked AWS and GCE pages
are in bad shape and don't relate to a component developed by the
community. Do we have any numbers from Google Analytics on how popular
those pages are? If they are somewhat popular, I would prefer
+1 (binding)
* verified checksums and hashes
* ran stateful example job in Kubernetes environment
* build (custom) Docker image from sources for Scala 2.11, 2.12
* used jackson new 2.10.1 profile and verified that the jackson databind
version is updated
* verified versions match 1.8.3 in pom.xml f
Answers inline...
On Thu, Dec 5, 2019 at 6:28 PM Seth Wiesman wrote:
> One option would be to do exactly that, but then I feel like we are
> committing to tracking changes on those systems and I just don't know how
> feasible that is.
>
I don't think that's feasible. It's bound to get out of sy
I can confirm that the Docker images are available [1]. Thanks, Patrick!
Looking forward to your ideas to integrate the Docker builds into the
release process. I'm happy to support you on this effort.
– Ufuk
[1] $ docker pull flink:1.8.3
1.8.3: Pulling from library/flink
844c33c7e6ea: Pull comp
Hey all,
first of all a big thank you for driving many of the Docker image releases
in the last two years.
*(1) Moving docker-flink/docker-flink to apache/docker-flink*
+1 to do this as you outlined. I would propose to aim for a first
integration with the 1.10 release without major changes to th
etup for
> the
> > main Flink images (those that depend on Flink releases) for better
> > visibility and to not confuse our users.
> > We might want to publish less critical images (playground images, dev
> > images, nightly builds, etc) via Infra under the Apache Docker
Hey all,
there is a proposal to contribute the Dockerfiles and scripts of
https://github.com/docker-flink/docker-flink to the Flink project. The
discussion corresponding to this vote outlines the reasoning for the
proposal and can be found here: [1].
The proposal is as follows:
* Request a new re
; > >>>> for every Flink release.
> > > >>>> Since we're mainly migrating the docker-flink/docker-flink repo to
> > > >>>> apache/flink-docker, this should just work as before.
> > > >>>>
> > > >>>> Less important imag
Hi everyone,
I'm happy to announce that we have unanimously approved the integration of
the Docker image publication into the Flink release process.
+1s (17 votes in total, 6 binding, 11 non-binding):
- Till Rohrmann (binding)
- Stephan Ewen (binding)
- Fabian Hüske (binding)
- Konstantin Knauf
Hey Piotr,
thanks for bringing this up. I really like this proposal and also saw
it work successfully at other projects. So +1 from my side.
- I like the approach with a notification one week before
automatically closing the PR
- I think a bot will the best option as these kinds of things are
usu
Congrats and welcome Sihua :-)
– Ufuk
On Fri, Jun 22, 2018 at 10:34 PM, Dawid Wysakowicz
wrote:
> Congratulations Sihua!
>
>
> On 22.06.2018 15:17, Till Rohrmann wrote:
>> Hi everybody,
>>
>> On behalf of the PMC I am delighted to announce Sihua Zhou as a new Flink
>> committer!
>>
>> Sihua has
Congrats and welcome Piotr! :-)
– Ufuk
On Sat, Jun 23, 2018 at 3:54 AM, zhangminglei <18717838...@163.com> wrote:
> Congrats Piotr!
>
> Cheers
> Minglei
>> 在 2018年6月23日，上午3:26，Till Rohrmann 写道：
>>
>> Hi everybody,
>>
>> On behalf of the PMC I am delighted to announce Piotr Nowojski as a new
>>
We fixed this for the Flink docs a while back in
https://github.com/apache/flink/pull/5395, but didn't think of the
flink-web repo which uses a similar setup to our docs.
If somebody has time to look into this, we can follow the above PR to
apply the same changes.
– Ufuk
On Fri, Jul 27, 2018 at
Great addition to the committers. Congrats, Gary!
– Ufuk
On Fri, Sep 7, 2018 at 4:45 PM, Kostas Kloudas
wrote:
> Congratulations Gary! Well deserved!
>
> Cheers,
> Kostas
>
>> On Sep 7, 2018, at 4:43 PM, Fabian Hueske wrote:
>>
>> Congratulations Gary!
>>
>> 2018-09-07 16:29 GMT+02:00 Thomas W
Hey Thomas,
On Fri, Nov 9, 2018 at 6:07 PM Thomas Weise wrote:
> Is there a way to activate the predefined options via configuration / flink-
> conf.yaml? Or only programmatically, like in [4]? The difficulty with the
> programmatic route (assuming this works now), is that in my case the client
>
+1. This seems reasonable to me. Since the fixes are already in and
also part of other releases, the release overhead should be
manageable.
@Vino: I agree with your assessment.
@Qi: As Till mentioned, the official project guideline is to support
the last two minor releases, e.g. currently 1.7 and
+1 to drop.
I totally agree with your reasoning. I like that we tried to keep it,
but I don't think the maintenance overhead would be justified.
– Ufuk
On Wed, Jan 9, 2019 at 4:09 PM Till Rohrmann wrote:
>
> With https://issues.apache.org/jira/browse/FLINK-10571, we will remove the
> Storm topo
Thanks Chesnay.
+1 to drop since we are not using them (flink-libraries is empty and
incubator-flink redirects to flink in GitHub).
– Ufuk
On Wed, Jan 16, 2019 at 10:38 AM Chesnay Schepler wrote:
>
> I've filed https://issues.apache.org/jira/browse/INFRA-17666.
>
> On 16.01.2019 10:32, Tzu-Li (
Hey Stephan and others,
thanks for the summary. I'm very excited about the outlined improvements. :-)
Separate branch vs. fork: I'm fine with either of the suggestions.
Depending on the expected strategy for merging the changes, expected
number of additional changes, etc., either one or the other
I like the idea of a leaner binary distribution. At the same time I
agree with Jamie that the current binary is quite convenient and
connection speeds should not be that big of a deal. Since the binary
distribution is one of the first entry points for users, I'd like to
keep it as user-friendly as
On Wed, Jan 23, 2019 at 11:01 AM Timo Walther wrote:
> I think what is more important than a big dist bundle is a helpful
> "Downloads" page where users can easily find available filesystems,
> connectors, metric repoters. Not everyone checks Maven central for
> available JAR files. I just saw tha
I played around with the bot and it works pretty well. :-) @Robert:
Are there any plans to contribute the code for the bot to Apache
(potentially in another repository)?
I like Fabians suggestions. Regarding the questions:
1) I would make that dependent on whether you expected the review
guideline
(1) I agree with Aljoscha's line of arguing here. A staleness bot is
quite the opposite of “sweeping things under the rug". A clear and
automated message about the state of a PR provides good value to
contributors, reviewers, and other people monitoring PRs. Asking
committers to proactively close P
de reviews before there was
> consensus whether the contribution was welcome or not.
>
> Am Mo., 28. Jan. 2019 um 16:54 Uhr schrieb Ufuk Celebi :
>
> > I played around with the bot and it works pretty well. :-) @Robert:
> > Are there any plans to contribute the code for the bot to
I'm late to this party but big +1. Great idea! I think this will help
to better represent the actual Flink community size and increase
interaction between the English and non-English speaking community.
:-)
On Mon, Jan 28, 2019 at 6:02 PM jincheng sun wrote:
>
> +1，I like the idea very much！
>
>
Hey devs,
I've been only following Flink dev loosely in the last couple of
months and could not find the following information:
What's the schedule for the next release? In particular, when is the
planned feature freeze and when is the planned release date?
I think this can be valuable informati
don't really know if there's an agreed upon release schedule in
>> the Flink community (I've not been following the dev@ list closely
>> recently).
>> I'll try to find somebody who knows a bit more about the recent Flink
>> community developmen
+1
@Gordon: There has been no further review of the PR that Shuyi linked
(https://github.com/apache/flink/pull/7356). Do you plan to block
1.7.2 on this or rather not?
– Ufuk
On Fri, Feb 8, 2019 at 10:35 PM Thomas Weise wrote:
>
> +1
>
>
> On Fri, Feb 8, 2019 at 6:14 AM jincheng sun
> wrote:
+1 to release 1.6.4
On Tue, Feb 12, 2019 at 10:01 AM jincheng sun wrote:
>
> Hi Flink devs,
>
> It has been a long time since the release of 1.6.3 (December 23, 2018).
> There have been a lot of valuable bug fixes during this period.
> What do you think about releasing Flink 1.6.4 soon?
>
> We al
+1 for Feb 22. Thanks for being the release manager.
– Ufuk
On Tue, Feb 12, 2019 at 7:00 PM Stephan Ewen wrote:
>
> +1 for doing a 1.8 release soon.
>
> Some of the Table API refactoring work is blocked on a release (assuming we
> want one release to deprecate some functions before dropping them
Dear devs,
what are your thoughts about moving flink-python (batch API) to opt
instead of having it in lib? The streaming counter part
(flink-streaming-python) is only as part of opt.
I think we don't have many users of the Python batch API. I think this
will make the streaming/batch experience m
;
> On Tue, Feb 26, 2019 at 7:37 AM jincheng sun
> wrote:
>
> > Thanks for bringing up this DISCUSS Ufuk!
> >
> > Makes sense. +1 for doing this.
> >
> > Best,
> > Jincheng
> >
> > Ufuk Celebi 于2019年2月25日周一 下午10:33写道：
> >
> > &
I fully agree with Aljoscha and Chesnay (although my recent PR
experience was still close to what Stanislav describes).
@Robert: Do we have standard labels that we apply to tickets that
report a flaky test? I think this would be helpful to make sure that
we have a good overview of the state of fla
e explicitly.
>
> On Thu, Feb 28, 2019 at 1:59 PM Ufuk Celebi wrote:
>
> > I fully agree with Aljoscha and Chesnay (although my recent PR
> > experience was still close to what Stanislav describes).
> >
> > @Robert: Do we have standard labels that we apply to tickets tha
I really like this effort. I think the original plan for
"cancel-with-savepoint" was always to just be a workaround until we
arrived at a better solution as proposed here.
Regarding the FLIP, I agree with Elias comments. I think the number of
termination modes the FLIP introduces can be overwhelmi
I like Shaoxuan's idea to keep this a static site first. We could then
iterate on this and make it a dynamic thing. Of course, if we have the
resources in the community to quickly start with a dynamic site, I'm
not apposed.
– Ufuk
On Wed, Mar 6, 2019 at 2:31 PM Robert Metzger wrote:
>
> Awesome!
Hey Aljoscha,
thanks for bringing this up. I think that we should either integrate
checks for this into our CI/CD environment (using existing tools) or
add a conditional check for this into flink-bot in case a pom.xml was
modified. Otherwise it will be easy to forget in the future.
– Ufuk
On Mon
happened)).
> Theoretically it is even possible to generate the licensing files from said
> output, but haven't had time yet to look into whether this is truly possible.
>
> On 19.03.2019 07:15, Ufuk Celebi wrote:
>
> Hey Aljoscha,
>
> thanks for bringing this
Wow! Very nice. Thanks for sharing. I will try it out :-)
On Thursday, October 22, 2015, Kunft, Andreas
wrote:
> FYI:
>
>
> FastR on Flink, a project to combine the R programming language with
> Flink, just went open source:
>
>
> http://mail.openjdk.java.net/pipermail/graal-dev/2015-October/003
>> >>>
> > > > >> >>> myVar.callMethod(param1, // many more
> > > > >> >>> .paramX); // the dots mark space
> > indention
> > > > >> >>>
> > > >
ed
>>>>>>>>>> tabs/spaces from my side.
>>>>>>>>>>
>>>>>>>>>> Matthias J. Sax ezt írta (időpont: 2015. okt.
>>>>>> 21.,
>>>>>>>> Sze,
>>>>>>>>>> 11:46):
&g
> On 26 Oct 2015, at 10:27, Fabian Hueske wrote:
>
> The website consists of two parts which are maintained in two separate
> respositories:
>
> 1) The project website about features, community, etc.
> 2) The documentation of the project
>
> We have the separation because we want to be able to
I agree with Till, but is this something you want to address in this release
already?
I would postpone it to 1.0.0.
– Ufuk
> On 26 Oct 2015, at 16:17, Till Rohrmann wrote:
>
> I would be in favor of deploying also Scala 2.11 artifacts to Maven since
> more and more people will try out Flink w
> On 27 Oct 2015, at 12:12, Aljoscha Krettek wrote:
>
> There are still references to 0.10-SNAPSHOT in the release. Especially for
> the quickstarts this is problematic:
>
> ~/D/flink (release-0.10.0-rc1|✔) $ ag "0.10-SNAPSHOT"
> docs/_config.yml
> 30:version: "0.10-SNAPSHOT"
>
> docs/apis/be
I think your comment was misleading. It sounded like you added the actual
dependency to the POM and not just to the LICENSE file.
> On 02 Nov 2015, at 16:26, Aljoscha Krettek wrote:
>
> This is the PR: https://github.com/apache/flink/pull/1316 if anyone is
> interested or knows something about
+1
I
- ran fault-tolerant job with Kafka and randomly killed workers and masters
(for Hadoop 2.4, 2.6, 2.7 and standalone)
- verified the local split assignment
- read the README file
- verify that the log is free of errors/exceptions
- checked the quickstarts
– Ufuk
> On 09 Nov 2015, at 10:34,
Thu, Oct 22, 2015 at 3:13 PM, Maximilian Michels <
>>>>>>> m...@apache.org
>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>&
Thanks for reporting this. Are you using any custom data types?
If you can share your code, it would be very helpful in order to debug this.
– Ufuk
On Tuesday, 10 November 2015, Fabian Hueske wrote:
> I agree with Robert. Looks like a bug in Flink.
> Maybe an off-by-one issue (violating index
s question: I¹m using the 0.9.1 release right off the
> website (flink-0.9.1-bin-hadoop1.tgz).
>
> In answer to Ufuk¹s question: Yes I¹m using custom data types.
>
> Thanks,
> Ali
>
>
>
> On 2015-11-10, 3:01 PM, "Ufuk Celebi" wrote:
>
> >Thanks for re
> On 12 Nov 2015, at 15:38, Gyula Fóra wrote:
>
> I am not sure if this issue affects the release or maybe I am just doing
> something wrong: https://issues.apache.org/jira/browse/FLINK-3006
I would address it in a bug fix release.
– Ufuk
> On 12 Nov 2015, at 21:25, Fabian Hueske wrote:
>
> Hi everybody,
>
> with 0.10.0 almost being released I started writing release nodes for the
> Flink blog.
>
> Please find the current draft here:
> https://docs.google.com/document/d/1ULZAdxwneZAldhJ69tB3UEvjJQhS-ZASN5mdtumtJ48/edit?usp=shar
hould to go directly into the release
> announcement.
>
> It would be great if you could draft a migration guide.
>
> 2015-11-13 10:27 GMT+01:00 Ufuk Celebi :
>
>>
>>> On 12 Nov 2015, at 21:25, Fabian Hueske wrote:
>>>
>>> Hi everybody,
>&g
Not that I am aware of. This is most probably a bug.
Looking at the code of the ExecutionGraph:
A job can only be cancelled when the job status is CREATED or RUNNING. If the
job failed during execution it is in state FAILED until it is RESTARTING. After
resetting the ExecutionGraph state, the s
Can you please share the complete logs with me? Uce at apache org ;)
On Saturday, 14 November 2015, Gyula Fóra wrote:
> Hi guys,
>
> I have a Flink Streaming job running for about a day now without any errors
> and then I got this in the job manager log:
>
> 15:37:49,905 WARN io.netty.channel.D
This Exception was not thrown by the data exchange component. This is confirmed
by the stack trace you have shared. It shows the DefaultThreadFactory, which we
don’t use for the data exchange. Any Exception thrown there will actually fail
the program.
My best guess is that this was thrown by t
https://issues.apache.org/jira/browse/KAFKA-824
This has been fixed for Kafka’s 0.9.0 version.
We should investigate why the job gets stuck though. Do you have a stack trace
or any logs available?
– Ufuk
> On 17 Nov 2015, at 09:24, Gyula Fóra wrote:
>
> Hey guys,
>
> I ran into some issue w
at 10:43, Ufuk Celebi wrote:
>
> https://issues.apache.org/jira/browse/KAFKA-824
>
> This has been fixed for Kafka’s 0.9.0 version.
>
> We should investigate why the job gets stuck though. Do you have a stack
> trace or any logs available?
>
> – Ufuk
>
>&g
Big +1
I think the mentioned issues cover all important fixes.
– Ufuk
> On 18 Nov 2015, at 13:49, Till Rohrmann wrote:
>
> @Vasia, do you mean FLINK-3013 or FLINK-3012?
>
> Will merge PRs for FLINK-3036 and FLINK-3013 this afternoon.
>
> On Wed, Nov 18, 2015 at 1:47 PM, Stephan Ewen wrote:
@Suneel: I think that's OK for the next major release :)
On Wed, Nov 18, 2015 at 2:17 PM, Suneel Marthi
wrote:
> Would be nice to have Flink-2949 in the mix, but I won't be able to get to
> it until early next week.
>
> On Wed, Nov 18, 2015 at 7:49 AM, Till Rohrmann
> wrote:
>
> > @Vasia, do yo
I like this idea. +1
> On 18 Nov 2015, at 15:25, Stephan Ewen wrote:
>
> I had pretty much in mind what Aljoscha suggested.
>
> On Thu, Nov 12, 2015 at 11:37 AM, Aljoscha Krettek
> wrote:
>
>> IMHO it’s not possible to have streaming/batch specific ExecutionConfig
>> since the user functions
I think it's confusing to only have a subset of import statements provided.
But then again, the missing ones will be resolved without confusion
(hopefully) ;) We can go with this and see what feedback we get.
(Just doing it for some examples sounds reasonable.)
– Ufuk
On Thu, Nov 19, 2015 at 5:2
gt; > >
> > > > > > > > > > @Suneel, I think
> > > > > https://issues.apache.org/jira/browse/FLINK-2949
> > > > > > > is a
> > > > > > > > > new
> > > &g
+1
- Verified hashes and signatures
- Ran example jobs on YARN with vanilla Hadoop vesions (on 4 GCE nodes):
* 2.7.1 with Flink Hadoop 2.7 binary, Scala 2.10 and 11
* 2.6.2 with Flink Hadoop 2.6 binary, Scala 2.10
* 2.4.1 with Flink Hadoop 2.4 binary, Scala 2.10
* 2.3.0 with Flink Hadoop 2
> On 30 Nov 2015, at 17:47, Kashmar, Ali wrote:
> Do the parallel instances of each task get distributed across the cluster or
> is it possible that they all run on the same node?
Yes, slots are requested from all nodes of the cluster. But keep in mind that
multiple tasks (forming a local pipe
> On 01 Dec 2015, at 15:26, Kashmar, Ali wrote:
>
> Is there a way to make a task cluster-parallelizable? I.e. Make sure the
> parallel instances of the task are distributed across the cluster. When I
> run my flink job with a parallelism of 16, all the parallel tasks are
> assigned to the first
Great post! Thanks!
I have also made some comments in the commit.
– Ufuk
> On 09 Dec 2015, at 14:19, Maximilian Michels wrote:
>
> Hi Matthias,
>
> Thank you for the blog post. You had already shared a first draft with
> me. This one looks even better!
>
> I've made some minor comments. +1 t
Hey Ali,
can you send me the complete logs?
I don’t think it’s possible via the mailing list. Just send it to my private
email u...@apache.org.
– Ufuk
> On 16 Dec 2015, at 17:26, Kashmar, Ali wrote:
>
> Hi,
>
> I’m trying to test HA on a 3-node Flink cluster (task slots = 48). So I
> start
Hey Ali,
can you send me the complete logs?
I don’t think it’s possible via the mailing list. Just send it to my private
email u...@apache.org.
– Ufuk
> On 16 Dec 2015, at 17:26, Kashmar, Ali wrote:
>
> Hi,
>
> I’m trying to test HA on a 3-node Flink cluster (task slots = 48). So I
> start
As an update: I’m investigating this. Ali sent me the log files.
> On 16 Dec 2015, at 18:15, Ufuk Celebi wrote:
>
> Hey Ali,
>
> can you send me the complete logs?
>
> I don’t think it’s possible via the mailing list. Just send it to my private
> email u...@apache.o
> On 18 Dec 2015, at 03:07, Xinhui Tian wrote:
>
> Hello everyone!
>
> Earlier we have posted a topic about the plan of including Flink support in
> our big data benchmark, which is called BigDataBench. The benchmarks can be
> found on http://prof.ict.ac.cn/BigDataBench/. Now we have released
The issue was that 1) local state backend but loss of VM and 2) recovery did
not log any Exception.
2) has been addressed in this PR: https://github.com/apache/flink/pull/1472
– Ufuk
> On 17 Dec 2015, at 15:26, Ufuk Celebi wrote:
>
> As an update: I’m investigating this. Ali sent m
+1
I wanted to make a similar proposal.
– Ufuk
> On 08 Jan 2016, at 17:03, Kostas Tzoumas wrote:
>
> for clarification, I was talking about dropping the code, I am unsure about
> the consequences of dripping code :-)
>
> On Fri, Jan 8, 2016 at 4:57 PM, Kostas Tzoumas wrote:
>
>> +1 from my
> On 08 Jan 2016, at 15:54, Till Rohrmann wrote:
>
> Hi everybody,
>
> recently we've seen an increased interest in complex event processing (CEP)
> by Flink users. Even though most functionality is already there to solve
> many use cases it would still be helpful for most users to have an easy
01-08 17:35 GMT+01:00 Till Rohrmann > >:
>>>
>>>> +1 since it increase maintainability of the code base if it is not
>> really
>>>> used and thus removed.
>>>>
>>>> On Fri, Jan 8, 2016 at 5:33 PM, Ufuk Celebi > > wrote:
&g
Thank you :D
On Tue, Jan 19, 2016 at 6:41 PM, Till Rohrmann wrote:
> Thanks Max :-)
>
> On Tue, Jan 19, 2016 at 6:05 PM, Fabian Hueske wrote:
>
> > Thanks Max!
> >
> > 2016-01-19 18:04 GMT+01:00 Maximilian Michels :
> >
> > > I've filed an issue at infra to protect the master:
> > > https://iss
On Tue, Jan 19, 2016 at 11:37 AM, Camelia Elena Ciolac
wrote:
> Hello,
>
> I list some questions gathered while reading documentation on Flink's
> internals and I am grateful to receive your answers.
>
> 1) How is the JobManager involved in the communication between tasks
> running in task slots
> On 21 Jan 2016, at 17:51, Maximilian Michels wrote:
>
> https://issues.apache.org/jira/browse/FLINK-2940
>
> There is now a pending pull request: https://github.com/apache/flink/pull/1529
>
> As I was working on the changes, I discovered we have some more
> modules which have a Scala depende
> On 25 Jan 2016, at 11:39, Maximilian Michels wrote:
>
> I won't have the time to finish the refactoring. Also, it will be
> pretty painful with all the large streaming pull requests being merged
> at the moment. If there are no objections, I would like to merge the
> Scala suffix changes with
1 - 100 of 990 matches
Mail list logo
