> On 08 Sep 2015, at 12:01, Stephan Ewen wrote:
>
> Hi all!
>
> Some day back we talked about releasing an 0.10.0-milestone1 release. The
> master has advanced quite a bit (especially due to high-availability code).
>
> I cherry picked the important additions to the release-0.10.0-milestone1
>
I saw that the tool is missing Javadocs. I think that this is a prerequisite
before moving it into all the examples (or at least both should happen hand in
hand). I would like an example-centric style there.
– Ufuk
> On 04 Sep 2015, at 14:46, Behrouz Derakhshan
> wrote:
>
> Yes, I was referr
Hey Niklas,
this is very much hidden unfortunately. You can find it in
Execution#markFinished.
The last partition to be finished triggers the scheduling of the receivers.
From your comments I see that you have dug through the network stack code quite
a bit. If you are interested, we can have a
> On 09 Sep 2015, at 19:31, Niklas Semmler wrote:
>
> Hello Ufuk,
>
> thanks for you amazingly quick reply.
>
> I have seen the markFinished in Execution.java, but if I get it right, this
> is simply used to stop a task. The ScheduleOrUpdateConsumers message in the
> pipeline case on the oth
Thanks Stephan for pointing this out. I agree with you. +1
@Chiwan: Good idea with the Wiki. Actually maybe even better to add it to the
contribution guide? Do you have time to open a PR with Stephan’s suggestions?
@Martin: I agree that it does not suffice to just point this out as a new
guidel
Same here.
> On 23 Sep 2015, at 13:50, Vasiliki Kalavri wrote:
>
> Hi,
>
> It's the latest master I'm trying to build, but it still hangs.
> Here's the trace:
>
> -
> 2015-09-23 13:48:41
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode):
>
I’ve pushed a fix.
> On 23 Sep 2015, at 16:28, Paris Carbone wrote:
>
> It hangs for me too at the same test when doing "clean verify"
>
>> On 23 Sep 2015, at 16:09, Stephan Ewen wrote:
>>
>> Okay, will look into this is a bit today...
>>
&
Hey Fabian,
nice to see you taking care of this.
I was wondering whether it makes sense to let the milestone branch catch up
with the current master as it contains many small fixes by now.
You will have a better understanding of this. But as far as I can tell the only
big recent change we want
> On 25 Sep 2015, at 11:15, Fabian Hueske wrote:
>
> RC1 has a few issues that need to be resolved before we can continue with
> the release.
>
> - .git folder contained in source release
> - start/stop script fail in paths with spaces (FLINK-2756)
I’ll take care of these two.
> On 25 Sep 2015, at 11:22, Fabian Hueske wrote:
>
> Thanks Ufuk! I have a patch for the start/stop scripts coming up. Sorry for
> not assigning the issue to myself. Will do that now.
No biggie. I just got around to looking into the other issue. I’ve pushed the
fix to master (one line).
– Ufu
> On 30 Sep 2015, at 10:06, Kostas Tzoumas wrote:
>
> Does the workaround work, or can FLINK-2443 still appear?
>
> If we have a workaround, we can schedule a fix to FLINK-2443 for 0.10.1
+1 Sounds like a good plan to me.
– Ufuk
> On 01 Oct 2015, at 16:48, Robert Metzger wrote:
>
> @Chesnay: Nothing prevents projects from getting stuck there. But at least
> we don't have two staging repositories (dist, staging). Also I would not
> say that there has been no graduation out of staging. Yarn was also there
> once, streamin
I would like to remove it as well. I doubt that a lot of people will really
switch back to the old one. So we won't gain a lot by keeping it around imo.
On Sunday, October 4, 2015, Robert Metzger wrote:
> Its not very hard to move the features to the new interface. I think the
> main issue is ti
Hey Niklas,
I’ve missed your answer. Sorry for the delay!
> On 20 Jul 2015, at 19:00, Niklas Semmler wrote:
>
> Hello Ufuk,
>
> thank you very much for the answer. You helped me to bring a great deal of
> context into the problem :).
>
> I have one final question: What is a good indicator th
I know that Till observed issues with the ScalaShell tests as well. If I
remember correctly, the issues were caused by checking the log file for
specific order of events, which is not necessarily the case.
– Ufuk
> On 13 Oct 2015, at 16:14, Sachin Goel wrote:
>
> Hi all
> Over the past few da
> On 11 Oct 2015, at 23:54, Stephan Ewen wrote:
>
> Can you see is there is anything unusual in the JobManager logs?
Ping. :)
DISCLAIMER: This is not my personal idea, but a community discussion from
some time ago. Don't kill the messenger.
In March we were discussing issues with heterogeneity of the code [1]. The
summary is that we had a consensus to enforce a stricter code style on our
Java code base in order to make i
; > 1) yes. Been dancing this issue for a while. Let's pull the trigger.
> Did
> > > the exercise with Tachyon while back and did help readability and
> > > homogeneity of code.
> > >
> > > 2) +1 for Google Java style with documented except
@testers: I think it's OK to forward test results not touching these parts
to the next RC.
On Wed, Oct 21, 2015 at 11:33 PM, Gyula Fóra wrote:
>
> FLINK-2888 and FLINK-2824 are blockers from my point of view.
>
Regarding FLINK-2824: from the discussion on the ML [1] I understood that
the plan wa
This vote has passed with 4 binding +1 votes. Thanks to everyone who
contributed and tested the release candidate.
+1s:
Stephan Ewen (binding)
Till Rohrmann (binding)
Aljoscha Krettek (binding)
Ufuk Celebi (binding)
There are no 0s or -1s.
On Thu, Aug 4, 2016 at 9:14 AM, Ufuk Celebi wrote
The Flink PMC is pleased to announce the availability of Flink 1.1.0.
On behalf of the PMC, I would like to thank everybody who contributed
to the release.
The release announcement:
http://flink.apache.org/news/2016/08/08/release-1.1.0.html
Release binaries:
http://apache.openmirror.de/flink/fli
As noted in the other thread, this is a problem with the Maven
artifacts of 1.1.0 :-( I've added a warning to the release note and
will start a emergency vote for 1.1.1 which only updates the Maven
artifacts.
On Tue, Aug 9, 2016 at 9:45 AM, LINZ, Arnaud wrote:
> Hello,
>
>
>
> I’ve switched to 1.
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.1.
*Important*: I would like to reduce the voting time to 24 hours (with
a majority of at least three +1 PMC votes as usual). We discovered
that the Maven artifacts published with version 1.1.0 have
t
and update the Flink version to 1.1.1:
flink-rc
flink-rc
https://repository.apache.org/content/repositories/orgapacheflink-1101
true
false
Would really appreciate it!
On Tue, Aug 9, 2016 at 2:11 PM, Ufuk Celebi wrote:
> As noted in the other thread, this is a problem with the Maven
>
PS: Let me add that no changes other than the release 1.1.1 commit
have been added on top of what we had in 1.1.0.
On Tue, Aug 9, 2016 at 6:27 PM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version
> 1.1.1.
>
&
;> >
>> > With the 1.1.1 RC1, the exception disappeared.
>> >
>> >
>> >
>> > On Wed, Aug 10, 2016 at 9:24 AM, Till Rohrmann
>> wrote:
>> >
>> >> +1 from my side as well.
>> >>
>> >> On Tue,
This vote has passed with 10 binding +1 votes. I'll go ahead finalize
and package this release.
+1s (all binding):
Marton Balassi
Vasia Kalavri
Gyula Fora
Henry Saputra
Stephan Ewen
Till Rohrmann
Robert Metzger
Maximilian Michels
Aljoscha Krettek
Ufuk Celebi
There are no 0s or -1s.
On Wed
This vote has passed with 10 binding +1 votes. I'll go ahead finalize
and package this release.
+1s (all binding):
Marton Balassi
Vasia Kalavri
Gyula Fora
Henry Saputra
Stephan Ewen
Till Rohrmann
Robert Metzger
Maximilian Michels
Aljoscha Krettek
Ufuk Celebi
There are no 0s or -1s.
On Wed
The Flink PMC is pleased to announce the availability of Flink 1.1.1.
The Maven artifacts published on Maven central for the previous 1.1.0
version had a Hadoop dependency issue. No Hadoop 1 specific version
(with version 1.1.0-hadoop1) was deployed and the 1.1.0 artifacts have
a dependency on Had
Hey all!
I've created a short FLIP for rescalable non-partitioned state:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-8%3A+Rescalable+Non-Partitioned+State
This is related to an effort led by Till, Aljoscha, Stephan, and
Stefan to allow rescaling of Flink jobs (see FLINK-3755, FLINK-43
Comments inline.
On Thu, Aug 11, 2016 at 8:06 PM, Gyula Fóra wrote:
> Option 1:
> I think the main problem here is sending all the state everywhere will not
> scale at all. I think this will even fail for some internal Flink operators
> (window timers I think are kept like this, maybe Im wrong he
>> can
>> > of course use connected operators or wrapper types and broadcast one of
>> the
>> > input but there are several limitations. We cant use keyed states for
>> > instance becase that requires both inputs to be keyed (so we cant
>> > broadcast).
I agree that it is acceptable to break it (again). At the moment, we
already prohibit users from resuming 1.0 savepoints with 1.1 and so
far (~1 week since release) no one complained. I think that at this
point most users use it only with the same major version as they used
when triggering the save
Hey David! Yes, sure.
- The NettyServer handles these requests in the server pipeline (see
PartitionRequestProtocol#getServerChannelHandlers())
- The main handler for these requests is
PartitionRequestServerHandler: it gets the requests, forwards it to
the ResultPartitionProvider and queues it for
If I'm understanding correctly, you want something liked
"tumbling-session" windows. Session windows [1] do exactly what you
describe but are only evaluated after a certain period of inactivity,
but you want to evaluate the window every X minutes after the first
element for a key arrived, right? I
Hey Kostas! Thanks for sharing the documents. I think it makes sense
to merge the two documents by moving the Google doc contents to the
Wiki. I think they form one unit.
On Tue, Aug 16, 2016 at 12:34 PM, Kostas Kloudas
wrote:
> Hi all!
>
> I've created a FLIP for the trigger DSL. This is the tri
I've seen this in BEAM as well and I really like it.
- I'm finishing up the initial work for FLIP-3 (Docs restructuring)
and hope to post something to the mailing list later today about it.
- I will start working on top of Aljoscha's and Stefan's pull request
#2376 with an initial version for non
+1
On Wed, Aug 17, 2016 at 5:24 PM, Robert Metzger wrote:
> Hi,
>
> following the discussions in [1], the community decided to offer
> contributors to submit streaming connectors the Flink community can not
> maintain to Apache Bahir (there is still the option that we are moving
> popular connec
>> > +1, thanks :-)
>> >
>> > On Tue, Aug 2, 2016 at 11:39 AM, Ufuk Celebi wrote:
>> >
>> > > If there are no objections, I would like to work on this in the next
>> > > days. I would like to only do the restructuring and don't add any
Hey devs! I've created a FLIP to unify savepoints and checkpoints:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-10%3A+Unify+Checkpoints+and+Savepoints#
Looking forward to your feedback.
– Ufuk
On Tue, Aug 23, 2016 at 9:47 AM, Fabian Hueske wrote:
> I drafted an API proposal a few months ago [2] and could convert this into
> a FLIP to discuss the API and break it down into subtasks.
>
> What do you think?
Sounds very reasonable :) +1
t;> I second Aljoscha :-)
>>
>> On Fri, Aug 19, 2016 at 11:53 AM, Aljoscha Krettek
>> wrote:
>>
>>> I checked it out and I liked it. :-)
>>>
>>> On Thu, 18 Aug 2016 at 19:40 Ufuk Celebi wrote:
>>>
>>> > Initial PR for the layou
It's been ~2 weeks since we released Flink 1.1.1 and I wanted to start
discussing releasing Flink 1.1.2.
There have been 27 commits in the release-1.1 branch since the
release, including at least one critical issue:
[FLINK-4332] [checkpoints] Fix SavepointV1Serializer read() /
readFully() (2 week
On Fri, Aug 26, 2016 at 2:40 AM, Greg Hogan wrote:
>
> This sounds like a nice compromise, to include the extra jars in the
> download but off the default classpath. The distinction between lib and
> libraries may be subtle and not as applicable to the other jars. Would
> something like "opt" be t
Hey devs,
had a quick discussion with Stephan about usage of DataInputStream
read and readFully. In most cases we want to use readFully, but it's
easy to accidentally use read instead (happened to me here for
example: https://issues.apache.org/jira/browse/FLINK-4332), which only
reads as many byte
+1... Personally, I'm a big fan of frequent bugfix releases :-)
A user already reported running into the file source problem and
having a very hard time debugging it. This would be good to fix asap.
– Ufuk
On Thu, Sep 29, 2016 at 3:20 PM, Fabian Hueske wrote:
> Sounds good to me.
>
> Can we inc
Hey Dan!
On Thu, Sep 29, 2016 at 10:58 PM, dan bress wrote:
> If I deploy a job to Flink called "A"(set my
> streamExecutionEnvironment.execute("A"), that checkpoints state. Then I
> cancel "A" and deploy the same job but call it "B", will it pick up A's
> state? Or is checkpointing key'd by th
On Fri, Sep 30, 2016 at 7:02 PM, dan bress wrote:
> Thanks for the answer. In 1.1.X, If I deploy job "Job-V1", run for a
> while, trigger a save point, cancel the job, submit job "Job-V2" and resume
> save point. Will Job-V2 understand the savepoint from Job-V1?
Currently it depends on the type
If there are no objections I would like to be the release manager for
this release.
Futhermore, I would like to add FLINK-4732 (Maven junction plugin
security issue) to the list of fixes for this release. Other than
that, I think the list in this thread is good and we should now focus
on getting a
Hey Eron! What will this mean for users running older Mesos versions?
It might help to post this question to the user mailing list as well.
On Tue, Oct 4, 2016 at 4:06 AM, Eron Wright wrote:
> Hello,
> For Flink's initial support for Mesos, coming in Flink 1.2, does anyone have
> an objection to
October 4, 2016 at 6:12:06 PM, Fabian Hueske (fhue...@gmail.com) wrote:
>>
>> Thanks Ufuk for stepping up as release manager!
>>
>> Yes, I will backport the fix for FLINK-4311 to Flink 1.1.3 and merge it
>> today.
>>
>> 2016-10-04 12:07 GMT+02:00 Ufuk Celebi :
&
Hi Ufuk,
>>>
>>> Thanks for being the release manager.
>>>
>>> There is already an open PR under review for the Continuous File Sources.
>>>
>>> Kostas
>>>
>>>> On Oct 4, 2016, at 11:25 PM, Ufuk Celebi wrote:
>>>>
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.3.
The commit to be voted on:
3264a16 (http://git-wip-us.apache.org/repos/asf/flink/commit/3264a16)
Branch:
release-1.1.3-rc1
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
t;
>>> I would still give a +1 if we have merged the pull request.
>>>
>>> -Max
>>>
>>>
>>> On Fri, Oct 7, 2016 at 4:49 PM, Kostas Kloudas
>>> wrote:
>>> > Hi all,
>>> >
>>> > I tested the Kafka
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.3.
The commit to be voted on:
8e8d454 (http://git-wip-us.apache.org/repos/asf/flink/commit/8e8d454)
Branch:
release-1.1.3-rc2
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
tory
>> > > > (cleaned .m2 cache for 1.1.3 before doing that)
>> > > > - various tests with ContinuousFileMonitoringFunction and verified
>> the
>> > > > fix from the previous RC1
>> > > >
>> > > >
>> > > > -Max
The Flink PMC is pleased to announce the availability of Flink 1.1.3.
The official release announcement:
https://flink.apache.org/news/2016/10/12/release-1.1.3.html
Release binaries:
http://apache.lauf-forum.at/flink/flink-1.1.3/
Please update your Maven dependencies to the new 1.1.3 version and
Hey devs,
I would like to propose the removal of the
flink-contrib/flink-operator-stats module.
It is currently causing some build stability issues
(https://issues.apache.org/jira/browse/FLINK-4833) and there is no
active maintainer for it as far as I can tell.
Are there any objections to this?
> > If there are no users and no contributors of the module, I'm +1 to
>> remove
>> > > it.
>> > >
>> > > If we decide to remove it from flink-contrib, but there are some
>> > > contributors interested in it, I can offer to assist the cont
Hey all,
I would like to start the discussion for kicking off the next bug fix
release, Flink 1.1.4. What do you think about aiming for a RC by end
of this week?
Users reported some instabilities/inconveniences that would be good to fix.
Personally, I would like to backport the following fixes:
t; >>> dependencies.
>> > > >>>
>> > > >>> Stability on S3 considering eventual consistency *(fix pending)*
>> > > >>> - [FLINK-4218] [checkpoints] Do not fail checkpoints when state
>> > > >>size
>> >
Hey devs,
can we disable Jenkins for our pull requests? They are failing, but
Travis runs (mostly) succeed. I'm asking because because of the failed
Jenkins builds, the main PR listing shows all PRs as failing builds.
Furthermore, contributors might be confused by this.
If we want to keep both, c
in user code.
>
>> Am 28.10.2016 um 14:27 schrieb Ufuk Celebi :
>>
>> Thanks for all your feedback.
>>
>> If there are no objections, I would like to stick to the mentioned
>> issues in this thread and create RC1 as soon as they are all
>> addressed. This will p
Thanks!
On Thu, Nov 3, 2016 at 6:47 PM, Maximilian Michels wrote:
> +1 I've put the Jenkins PR testing on hold until we investigate.
>
> -Max
>
>
> On Tue, Nov 1, 2016 at 7:15 PM, wrote:
>> +1
>>
>> Thanks and Regards,
>> Vishnu Viswanath
>
I really like your proposal. +1.
I did some of the previous site updates, but never actually had the time to
really think it through like you did.
All main changes (start page, intro to Flink, and moving the quick starts) look
very cool and well thought out. Looking forward to the initial PR. :
On 10 November 2016 at 14:46:57, Mike Winters (mwi...@gmail.com) wrote:
> > @Max, I was also unsure about the left-hand nav as it's a substantial
> change from the status quo, however, I believe it provides more
> guidance on
> a 'logical' order for a new user to move through the site. Definitely
I also just noticed it today. We used to work with the 120 minutes limit and
the builds took way longer as you said. I don't know what's going on here...
It might be related to some issues they reported a few hours ago
(https://twitter.com/traviscistatus), but I can't tell.
I really hope that t
eath watch with own heartbeat on the TM
> >> side: https://github.com/apache/flink/pull/2742
> >>
> >> as well. This will allow us to activate the quarantine monitoring per
> >> default in 1.1.4 without risking to kill all TMs in case of a JM failure.
> >&
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.4.
The commit to be voted on:
3c1024a (http://git-wip-us.apache.org/repos/asf/flink/commit/3c1024a)
Branch:
release-1.1.4-rc1
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
> Tested:
> >
> > - Built from source for Hadoop 2.7.3
> > - Tested running on YARN (with some fairly complex topologies)
> > - Savepoint app running on 1.1.3 -> restored successfully on 1.1.4
> >
> > Cheers,
> > Gyula
> >
> > Ufuk Celebi ezt
Furthermore, I think this issue is a blocker:
https://issues.apache.org/jira/browse/FLINK-5065: Resource leaks in case of
lost checkpoint messages
– Ufuk
On 14 November 2016 at 19:15:49, Ufuk Celebi (u...@apache.org) wrote:
> -1
>
> (1) We found an issue with the task cancellation s
> Am 15.11.2016 um 10:49 schrieb Till Rohrmann :
> > >
> > > +1 for Ufuk's proposal to cancel the vote in favour of a new RC. +1 for
> > > including FLINK-5065. I'm currently backporting the fix.
> > >
> > > On Tue, Nov 15, 2016 at 9:
include this fix for 1.1.4.
> Several users reported this issue.
>
> Cheers, Fabian
>
> [1] https://github.com/apache/flink/pull/2848
>
> 2016-11-16 9:42 GMT+01:00 Ufuk Celebi :
>
> > This RC has been cancelled in favour of RC2.
> >
> > I will wai
Thanks for reporting this Gyula. A fix is available in #2930. We are going to
merge that today.
– Ufuk
On 3 December 2016 at 09:56:21, Gyula Fóra (gyula.f...@gmail.com) wrote:
> Hi,
>
> I think something is not behaving correctly with savepoint/checkpoint
> discard on the release-1.1 branch. I
Thanks. It has been merged now. :-)
On 4 December 2016 at 17:24:30, Gyula Fóra (gyula.f...@gmail.com) wrote:
> Hi,
> Thanks for being so quick, I will try the fix as soon as it is merged. :)
> Gyula
>
> Ufuk Celebi ezt írta (időpont: 2016. dec. 4., V, 12:02):
>
> > T
Hey Robert,
thanks for bringing the discussion up again.
On Mon, Dec 5, 2016 at 6:28 PM, Robert Metzger wrote:
> - UNRESOLVED Unify Savepoints and Checkpoints (FLINK-4484)
This issue/FLIP contained two parts:
1. Write periodic checkpoints out to external storage
2. Allow periodic scheduling
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.4.
The commit to be voted on:
a587fe9 (http://git-wip-us.apache.org/repos/asf/flink/commit/a587fe9)
Branch:
release-1.1.4-rc2
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
On 12 December 2016 at 12:30:31, Maximilian Michels (m...@apache.org) wrote:
> > It seems like we lack the resources for now to properly to take
> care
> of your pull request before the release. Unless someone from
> the
> community is really eager to help out here, I would be in favor
> of
>
me, except the YARN vcore problem.
>
> Cheers,
> Gyula
>
>
> Ufuk Celebi ezt írta (időpont: 2016. dec. 12., H, 9:28):
>
> > Dear Flink community,
> >
> > Please vote on releasing the following candidate as Apache Flink version
> > 1.1.4.
> &
t; backported. (I opened a PR: https://github.com/apache/flink/pull/2990)
> This can be quite annoying for YARN deployments. I am not sure if this is a
> blocker though.
>
> So +1 from me, except the YARN vcore problem.
>
> Cheers,
> Gyula
>
>
> Ufuk Celebi ezt írt
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.4.
The commit to be voted on:
2cd6579 (http://git-wip-us.apache.org/repos/asf/flink/commit/2cd6579)
Branch:
release-1.1.4-rc3
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
//issues.apache.org/jira/browse/FLINK-5345
> - This is also a non blocking issue for 1.1.4 (fixed for 1.2)
> https://issues.apache.org/jira/browse/FLINK-4631
>
>
> Let me know if we should release anyways or fix these issues first.
>
>
> On Tue, Dec 13, 2016 at 11:04 PM, Uf
not a blocking issue I found during the testing:
>> > https://issues.apache.org/jira/browse/FLINK-5345
>> > - This is also a non blocking issue for 1.1.4 (fixed for 1.2)
>> > https://issues.apache.org/jira/browse/FLINK-4631
>> >
>> &g
This vote has been cancelled in favour of RC4.
I will kick of RC4 immediately since all fixes are already in the
release-1.1 branch.
On Tue, Dec 13, 2016 at 11:04 PM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.4.
The commit to be voted on:
8fb0fc8 (http://git-wip-us.apache.org/repos/asf/flink/commit/8fb0fc8)
Branch:
release-1.1.4-rc4
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
The delta iterations are a batch-only feature.
Did you try the DataStream#iterate?
https://ci.apache.org/projects/flink/flink-docs-release-1.1/apis/streaming/index.html#iterations
On Mon, Dec 19, 2016 at 5:35 AM, Govindarajan Srinivasaraghavan
wrote:
> Hi All,
>
> I have a use case for which I
Tue, Dec 20, 2016 at 10:44 AM, Gyula Fóra wrote:
>>
>> > I have built and ran the tests for the latest RC, so I carry my +1 vote
>> > from the previous thread
>> >
>> > Gyula
>> >
>> > Ufuk Celebi ezt írta (időpont: 2016. dec. 19., H,
The Flink PMC is pleased to announce the availability of Flink 1.1.4.
The official release announcement:
https://flink.apache.org/news/2016/12/21/release-1.1.4.html
Release binaries:
http://apache.lauf-forum.at/flink/flink-1.1.4
Please update your Maven dependencies to the new 1.1.4 version and
eryone,
>>> >
>>> > We've made progress on the new site, and here's a version you can run
>>> > locally if you'd like to take a look:
>>> > https://github.com/wints/flink-web-updates
>>> >
>>> > Should ta
me before 'Powered
> By' logos--I think this makes sense.
> -Nav bar highlights issue is fixed
>
> Just pushed these changes, and the preview site (
> https://wints.github.io/flink-web/) has been updated as well.
>
> Best,
> Mike
>
> On Mon, Jan 9, 2017 at 6:12 PM,
Hey all,
I've just created a Wiki page with a loose collection of some coding
"best practices" for the Flink project. The list was the result of a
discussion with other PMCs, committers, and contributors. It is not a
set of enforced rules, but a general list of tips, links to Flink
utilities, comm
On 16 January 2017 at 12:59:04, Paris Carbone (par...@kth.se) wrote:
> > Though, when someone has started reviewing a PR and shows interest
> it probably makes sense to finish doing so. Wouldn’t tagging
> be acceptable there?
> In those case tagging triggers direct notifications, so that
> pe
@Robert: I really like this. +1 to implement this after 1.2.0 is released.
Small note about your release dates: you started with 1.3.0 but probably meant
1.2.0 right?
On 18 January 2017 at 09:57:31, Tzu-Li (Gordon) Tai (tzuli...@apache.org) wrote:
> Hi Robert,
>
> Thanks for bringing up the di
anyone have the same problem?
>> - Do we still link to the wiki?
>> - Maybe too much info is buried under the Community & Project Info
>> category?
>>
>> On Tue, Jan 10, 2017 at 1:27 PM, Ufuk Celebi wrote:
>>
>>> Thanks for addressing my comments. I re
PS: Make sure to clear your caches. Otherwise there can be some weirdness. :D
On Wed, Jan 18, 2017 at 3:17 PM, Ufuk Celebi wrote:
> The updated page has been merged: http://flink.apache.org/
>
> Would appreciate it if you took a minute to just browse the web page
> and look out for a
If you like you could also open JIRA issues for these points with a note about
the discussion here. That way we make sure that we don't forget about our
feedback.
– Ufuk
On 20 January 2017 at 12:02:14, Mike Winters (mwi...@gmail.com) wrote:
> > Yes, thanks to all for helping! There are still so
Hey Paris!
As far as I know it's not possible at the moment and not planned. Does
not sound to hard to add though. @Stefan: correct?
You can currently only clear the state via #clear in the scope of the
key for keyed state or the whole operator when used with operator
state. In case of keyed stat
I totally did not see this email. Sorry! Thanks for all your hard work
and the great discussions on and offline. I learned a lot from you in
the past two years! Looking forward to seeing you again on the mailing
lists in the future.
– Ufuk
On Sat, Jan 21, 2017 at 4:49 PM, Paris Carbone wrote:
>
Hey Scott, thanks for reporting these.
Regarding the 2nd point: RC0 had an issue with the KryoSerializer
preventing users to resume from 1.1 savepoints. That was fixed at the
cost of breaking savepoint compatability between the RCs, but there is
no way around it. Flink guarantees compatability bet
I ran some tests and found the following issues:
https://issues.apache.org/jira/browse/FLINK-5663: Checkpoint fails
because of closed registry
=> This happened a couple of times for the first checkpoints after
submitting a job. If it happened on every submission I would
definitely make this a bloc
401 - 500 of 991 matches
Mail list logo
