Thanks for the notice. I’ve added a warning to the snapshot docs and created a
Wiki page with the changes:
https://cwiki.apache.org/confluence/display/FLINK/Maven+artifact+names+suffixed+with+Scala+version
– Ufuk
> On 27 Jan 2016, at 12:20, Maximilian Michels wrote:
>
> Dear users and develop
> On 01 Feb 2016, at 16:45, Hilmi Yildirim wrote:
>
> It seems that the exception is caused by a OutOfMemoryError. But this is only
> visible in the logs
Could you share the relevant parts?
– Ufuk
Hey all,
Our release-0.10 branch contains some important fixes (for example a
critical fix in the network stack). I would like to hear your opinions
about doing a 0.10.2 bug fix release.
I think it's a good idea to go for it now. Even though we have the 1.0.0
release coming up, it's not clear whe
> On 02 Feb 2016, at 11:43, Stephan Ewen wrote:
>
> +1
>
> @Ufuk: Would you be the release manager for that one?
Yes.
Thanks for the responses so far. I will go ahead and prepare a release
candidate soon.
If you have any minor fixes, which you would like to have in the release,
please repo
> On 02 Feb 2016, at 17:30, Robert Metzger wrote:
>
> Thank you for taking care of this. +1
>
> I'd like to include this in to the 0.10.2 release:
> https://github.com/apache/flink/pull/1576
OK (merged to master and release-10)
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version
0.10.2.
Shared document to coordinate testing:
https://docs.google.com/document/d/1oCOHwHwZNjHb7MX-qLvA61akEBOAxSIYo53MoygUqxQ/
The commit to be voted on:
3fcb91641118ba362b29a55e9102539e96852172
Bran
I've created the release candidate and started the vote thread.
This is the document to coordinate testing:
https://docs.google.com/document/d/1oCOHwHwZNjHb7MX-qLvA61akEBOAxSIYo53MoygUqxQ/
On Wed, Feb 3, 2016 at 7:31 PM, Ufuk Celebi wrote:
>
> > On 02 Feb 2016, at 17:30, Robert
> On 05 Feb 2016, at 12:17, Fabian Hueske wrote:
>
> I compared the RC1 branch to the release-0.10.2 tag and went over the diff
> (less than 2k changed lines, mostly added tests).
>
> Issues:
> - the docs/_config.yml needs to be updated to version 0.10.2
>
> Added / changed dependencies in pom
s for the RC. The documentation version is a really minor issue
>>>> which most people won't even notice because they use the online
>>>> documentation. I wouldn't create a new RC just for fixing that.
>>>>
>>>> On Fri, Feb 5, 2016 at 12:
> On 08 Feb 2016, at 13:57, Chesnay Schepler wrote:
>
> Hello all,
>
> The final flag on the
> org.apache.flink.runtime.io.network.api.writer.ResultPartitionWriter class is
> causing issues for me.
>
> The flag requires me to run a test I'm working on with a
> @RunWith(PowerMockRunner.class
> On 08 Feb 2016, at 15:13, Robert Metzger wrote:
>
> -1 (binding)
>
> the quickstart for 0.10.2 has the Flink version set to 0.10-SNAPSHOT, not
> to 0.10.2.
> https://repository.apache.org/content/repositories/orgapacheflink-1060/org/apache/flink/flink-quickstart-java/0.10.2/flink-quickstart-j
This vote is cancelled in favor of RC2.
On Mon, Feb 8, 2016 at 3:18 PM, Ufuk Celebi wrote:
>
>> On 08 Feb 2016, at 15:13, Robert Metzger wrote:
>>
>> -1 (binding)
>>
>> the quickstart for 0.10.2 has the Flink version set to 0.10-SNAPSHOT, not
>> to 0
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version
0.10.2.
Please note that this vote has a slightly shorter voting period of 48
hours. Only a single change has been made since the last release
candidate. Since the community has already done extensive t
On Mon, Feb 8, 2016 at 8:05 PM, Nick Dimiduk wrote:
> Perhaps too late for the RC, but I've backported FLINK-3293 to this branch
> via FLINK-3372. Would be nice for those wanting to monitory yarn
> application submissions.
>
> On Mon, Feb 8, 2016 at 9:37 AM, Ufuk Celeb
anyways pretty soon.
>>
>> I personally also invested again quite a bit of time into testing this
>> release candidate already.
>>
>>
>>
>> On Tue, Feb 9, 2016 at 1:51 PM, Fabian Hueske wrote:
>>
>>> Thanks Ufuk,
>>> +1 for a new
This vote has passed with 3 binding +1 votes. Thanks to everyone who
contributed and tested the release candidate.
+1s:
Ufuk Celebi (binding)
Stephan Ewen (binding)
Henry Saputra (binding)
There are no 0s or -1s.
I'll finalize and package this release in the next 48 hours.
– Ufuk
The Flink PMC is pleased to announce the availability of Flink 0.10.2.
On behalf of the Flink PMC, I would like to thank everybody who contributed
to the release.
The official release announcement:
http://flink.apache.org/news/2016/02/11/release-0.10.2.html
Release binaries:
http://apache.openmi
No, the "slaves" file is still used to ssh into the machines and start
the task manager processes in the start-cluster.sh script. So you
still need password-less ssh into the machines if you want to use
that. The task managers discover the job manager via ZooKeeper though
(therefore you don't need
Yes, you can cancel it via the web frontend or the CLI interface [1].
If you can send messages to the JobManager, you can also send a
CancelJob message yourself.
[1] https://ci.apache.org/projects/flink/flink-docs-master/apis/cli.html
On Fri, Feb 19, 2016 at 12:08 PM, Nikolaas s
wrote:
> Hi guy
update in rest of the machines in the cluster. I'm
> going to use Docker & Amazon ECS. So, if there is a change in my artifact,
> I will build a new cluster but as such each node of the cluster will be
> immutable.
>
>
>
> On Wed, Feb 17, 2016 at 11:54 PM, Ufuk Celebi
Maybe you can check whether this is a problem, too:
https://issues.apache.org/jira/browse/FLINK-3501
Under the assumption that no major functionality changes, I will
continue with the functional checks.
On Thu, Feb 25, 2016 at 2:32 PM, Robert Metzger wrote:
> Damn. I agree that this is a blocker
On Thu, Feb 25, 2016 at 5:23 PM, Vasiliki Kalavri
wrote:
> - HA: tested on a 6-node cluster with 2 masters.
> Issues:
> 1. After new leader election, the job history is cleaned up (at least in
> the WebUI). Is this on purpose?
Yes, the job history is part of the job manager.
> 2. After cluster r
I think that forking off is the regular way we do the releases and I
don't see any reasons to not do it this time.
– Ufuk
On Thu, Feb 25, 2016 at 7:41 PM, Robert Metzger wrote:
> Hi,
> I'd like to fork off a branch for the 1.0 release so that we can merge big
> changes into master. Any objectio
-1
Unfortunately, I've found a blocker
(https://issues.apache.org/jira/browse/FLINK-3556) while using RocksDB
and HA. Aljoscha ran into this as well.
– Ufuk
On Tue, Mar 1, 2016 at 11:28 AM, Stephan Ewen wrote:
> Thanks Robert for the RC.
>
> FYI: I checked and updated License file a few days ba
I get a 404 for the binaries. It's a INFRA thing I guess, because my
personal apache user page is also down/gone. :-(
On Tue, Mar 1, 2016 at 10:42 PM, Robert Metzger wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version 1.0
> .0.
>
> This is t
Hey all,
let's make sure that we have a good migration guide for the 1.0
release with the announcement.
Can you please add relevant changes that you are aware of to this document:
https://docs.google.com/document/d/13RqZ-_7_w1pYCi4cm_94XfaxwyTS1R_9KYUmD7jmGV8
I've created two sections, one for
+1
- Checked checksums and signatures
- Verified no binaries in source release
- Checked that source release is building properly
- Build for custom Hadoop version
- Ran start scripts
- Checked log and out files
- Tested in local mode
- Tested in cluster mode
- Tested on cluster with HDFS
- Tested
@Stefano: Yes, would be great to have a fix in the docs and pointers
on how to improve the docs for this.
On Fri, Mar 4, 2016 at 11:41 AM, Stefano Baghino
wrote:
> Build successful, thank you.
>
> On Fri, Mar 4, 2016 at 11:24 AM, Stefano Baghino <
> stefano.bagh...@radicalbit.io> wrote:
>
>> I'll
t; In the docs, it says to run the "tools/change-scala-version.sh 2.11" script
> first (which implicitly adds the "-Dscala-2.11" flag.
>
> I thought this problem arose because neither the flag was specified, nor
> the script run.
>
> On Fri, Mar 4, 2016 at 1
the
>> list. But definitely good to mention it there.
>>
>> On Thu, Mar 3, 2016 at 10:48 AM, Ufuk Celebi wrote:
>>
>> > Hey all,
>> >
>> > let's make sure that we have a good migration guide for the 1.0
>> > release with the a
Very nice proposal!
On Wed, Mar 9, 2016 at 6:35 PM, Stephan Ewen wrote:
> Thanks for posting this.
>
> I think it is not super urgent (in the sense of weeks or few months), so
> results around mid summer is probably good.
> The background in LLVM is a very good base for this!
>
> On Wed, Mar 9, 2
Hey Deepak!
Your description of Flink's behaviour is correct. To summarize:
# Host Address
If you specify a host address as an argument to the JVM (via
jobmanager.sh or the start-cluster.sh scripts) then that one is used.
If you don't, it falls back to the value configured in flink-conf.yaml
(wh
On Mon, Mar 14, 2016 at 11:20 AM, Gyula Fóra wrote:
> We developed (and contributed) the DB state backend to be able to handle
> large state sizes, but have moved to RocksDB for much better read/write
> performance. I have a pending PR with some improvements to the MySQL
> adapter but the question
I'm not too familiar with this part of Flink, but your arguments
certainly make sense.
Are there any performance differences to be expected?
– Ufuk
On Tue, Mar 15, 2016 at 11:02 AM, Aljoscha Krettek wrote:
> Hi folks,
> I opened a Jira Issue: https://issues.apache.org/jira/browse/FLINK-3614
>
>
On Tue, Mar 15, 2016 at 11:06 AM, Ufuk Celebi wrote:
> Are there any performance differences to be expected?
To clarify: I don't think that it would be a blocker expect for if it
had a yuge impact.
– Ufuk
On Tue, Mar 22, 2016 at 8:42 PM, Stefano Baghino
wrote:
> My feeling is that running a job on YARN should
> end up in having more or less the same effect, regardless of the way the
> job is run.
+1
I think that the current behaviour is buggy. The resource management
is currently undergoing a mas
Big +1, let's get this rolling... ;)
On Wed, Mar 23, 2016 at 11:14 AM, Aljoscha Krettek wrote:
> Hi,
> I’m aware of one critical fix and one somewhat critical fix since 1.0.0. One
> concerns data loss in the RollingSink, the other is a bug in a window
> trigger. I would like to release a bugfix
ls wrote:
>>
>>> +1
>>>
>>> On Wed, Mar 23, 2016 at 12:19 PM, Till Rohrmann
>>> wrote:
>>>> +1
>>>>
>>>> On Wed, Mar 23, 2016 at 11:24 AM, Stephan Ewen wrote:
>>>>
>>>>> Yes, there is also
ote:
> what about PR# 1829? We need it real bad for an upcoming release.
>
> On Tue, Mar 29, 2016 at 1:17 PM, Ufuk Celebi wrote:
>
>> I just merged #1830 and will create a RC after cherry picking
>> '[FLINK-3636] Add ThrottledIterator to WindowJoin jar' to the
&g
@Till: Isn't this an instance of the bug fixed in
https://github.com/apache/flink/pull/1818?
On Thu, Mar 31, 2016 at 5:05 PM, Stephan Ewen wrote:
> Hmm, it is wrong that the JobManager tries to load that class directly from
> the actor message.
> All user code should be deserialized lazily.
>
> H
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version
1.0.1.
The commit to be voted on:
4afa401ab3c2b53de115d17a3157e8b80431dd10
Branch:
release-1.0.1-rc1 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
Hey Matthias,
the test has been only recently added with the resource management
refactoring. It's probably just a too aggressive timeout for Travis.
@Max: Did you ever see this fail?
– Ufuk
On Fri, Apr 1, 2016 at 9:24 AM, Matthias J. Sax wrote:
> Anyone seen this before? One-time thing or tes
t; this bug which seems to be a blocker:
> https://issues.apache.org/jira/browse/FLINK-3688?jql=project%20%3D%20FLINK
>
> Should we maybe wait for the fix and then to another RC?
>
> On Thu, 31 Mar 2016 at 18:10 Ufuk Celebi wrote:
>
>> Dear Flink community,
>>
Same here.
+1 to publish
On Mon, Apr 4, 2016 at 10:04 AM, Aljoscha Krettek wrote:
> Hi,
> I like it. Very dense and very focused on the example but I think it should
> be good for the Flink Blog.
>
> --
> aljoscha
>
> On Fri, 1 Apr 2016 at 15:56 Till Rohrmann wrote:
>
>> Hi Flink community,
>>
Dear Flink community,
I have updated the Material section on the Flink project page and
moved the slides section to a separate page.
You can find links to slides and talks here now:
http://flink.apache.org/slides.html
I've added slides for talks from this year by Till Rohrmann, Vasia
Kalavri, Ro
Dear Flink community,
I'm happy to announce that we have added a long overdue section on
general Flink concepts to the documentation.
You can find it here:
https://ci.apache.org/projects/flink/flink-docs-release-1.0/concepts/concepts.html
Thanks to Stephan Ewen who wrote this great overview. I h
@Paris: Just added it. Thanks for the pointer. Great slides!
ing anymore and always depend on force-shading:1.0.0.
>
>
> On Sat, Apr 2, 2016 at 9:25 PM, Aljoscha Krettek
> wrote:
>
>> Yes, that seems reasonable.
>>
>> On Sat, 2 Apr 2016 at 13:14 Ufuk Celebi wrote:
>>
>> > Thanks for the initial tests.
>> &g
Hey Matthias,
could you update the links in the posts or share a list of the posts
with broken links so I can update them?
We can also provide redirects for the broken links. With 1.0, we now
should be more careful to not break/redirect links...
On Mon, Apr 4, 2016 at 2:53 PM, Matthias J. Sax
luded in
> the concepts.html for some reason. Chrome throws me this error:
>
> Uncaught ReferenceError: $ is not defined(anonymous function) @
> concepts.html:221
>
> Thanks
> Tianji
>
>
> On Mon, Apr 4, 2016 at 5:39 AM, Ufuk Celebi wrote:
>
>> Dear Flink commun
;> >> > One quick question regarding the release:
>> >> > Are you intentionally releasing a 1.0.1 version of the force-shading
>> >> module?
>> >> >
>> >> > Since it is really a work around, I wounder if we should not release
>&
This vote has passed with 3 binding +1 votes. Thanks to everyone who
contributed and tested the release candidate.
+1s:
Robert Metzger (binding)
Aljoscha Krettek (binding)
Ufuk Celebi (binding)
There are no 0s or -1s.
I'll finalize and package this release asap.
– Ufuk
On Mon, Apr 4, 20
The Flink PMC is pleased to announce the availability of Flink 1.0.1.
The official release announcement:
http://flink.apache.org/news/2016/04/06/release-1.0.1.html
Release binaries:
http://apache.openmirror.de/flink/flink-1.0.1/
Please update your Maven dependencies to the new 1.0.1 version and
The website has been updated for 1.0.1. :-)
@Till: If you don't mention it in the post, it makes sense to have a
note at the end of the post saying that the code examples only work
with 1.0.1.
On Mon, Apr 4, 2016 at 3:35 PM, Till Rohrmann wrote:
> Thanks a lot to all for the valuable feedback. I
>> -> https://github.com/apache/flink/tree/master/flink-staging/flink-table
>>>> ->
>>> https://github.com/apache/flink/tree/master/flink-staging/flink-hcatalog
>>>>
>>>> I would just removed those.
>>>>
>>>>
>>>>
&g
Hey all,
we recently released Flink 1.0.1, but some fixes did not make it into
the release:
Major issues reported by users:
- YARN dynamic properties (to be merged to release-1.0),
- POJO key selection,
- WindowOperator.trigger() and watermarks
Performance improvement:
- Disable WAL in RocksDB
t's not that critical, however.
>
> On Mon, 11 Apr 2016 at 18:40 Till Rohrmann wrote:
>
>> Given that it's low overhead, then +1 for new bug fix release. If we find
>> more stuff later on, then we can release another bug fix version.
>>
>> Cheers,
>> T
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.0.2.
The commit to be voted on:
80211d64e5d9f0e4f7f5e41085fc6a0e61bcdc02
Branch:
release-1.0.2-rc1 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
It's an easy fix and I will open a PR momentarily.
>
> On Thu, 14 Apr 2016 at 13:17 Ufuk Celebi >
> wrote:
>
> > Thanks for your feedback Till and Aljoscha. I will trigger the first RC
> > today.
> >
> > – Ufuk
> >
> > On Mon, Apr 11, 2016 a
s no workaround.
>
> On Thu, 14 Apr 2016 at 16:05 Ufuk Celebi wrote:
>
>> Dear Flink community,
>>
>> Please vote on releasing the following candidate as Apache Flink version
>> 1.0.2.
>>
>> The commit to be voted on:
>> 80211d64e5d9f0e4f7f5e41085
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.0.2.
The commit to be voted on:
058cc5de789331983830ce4720cd98c3af786109
Branch:
release-1.0.2-rc2 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
On Sat, Apr 16, 2016 at 1:05 PM, Matthias J. Sax wrote:
> (with the need to sort the data, because both
> datasets will be sorted on A already). Thus, the overhead of sorting in
> the group might pay of in the join.
I think you meant to write withOUT the need to the sort the data, right?
.
>
> I'm running tests right now and will merge the fix they provided later
> today.
>
> Cheers, Fabian
>
> [1]
> https://mail-archives.apache.org/mod_mbox/flink-dev/201604.mbox/%3CCANC1h_v2TwooQnXsfgYhpPCremT37%2BOwGjz_d5qsLdE0D%2BfmDA%40mail.gmail.com%3E
>
&
others think?
>
> Cheers, Fabian
>
> 2016-04-18 11:52 GMT+02:00 Ufuk Celebi :
>
>> This vote is cancelled in favour of RC3, because of the problem raised
>> by Fabian.
>>
>> On Fri, Apr 15, 2016 at 1:02 PM, Fabian Hueske wrote:
>> > There is a request
OK, thanks for the responses. I'll go ahead and include it for RC3.
On Mon, Apr 18, 2016 at 12:20 PM, Aljoscha Krettek wrote:
> +1, since others are blocked on this
>
> On Mon, 18 Apr 2016 at 12:10 Ufuk Celebi wrote:
>
>> I am fine with it since it only touches a
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.0.2.
The commit to be voted on:
d39af152a166ddafaa2466cdae82695880893f3e
Branch:
release-1.0.2-rc3 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
Can you please share the program before and after the savepoint?
– Ufuk
On Mon, Apr 18, 2016 at 3:11 PM, Ozan DENİZ wrote:
> Hi everyone,
>
> I am trying to implement savepoint mechanism for my Flink project.
>
> Here is the scenario:
>
> I got the snapshot of Flink application by using "flink s
s and hashes of all release artifacts.
>> > >>>
>> > >>> +1 to release this RC.
>> > >>>
>> > >>> Thanks, Fabian
>> > >>>
>> > >>> 2016-04-19 21:34 G
Ufuk,
>> > >
>> > > for our production use-case FLINK-3688 is very important, so we would
>> > > appreciate a quick 1.0.2 release. If you guys can take this into
>> > > consideration, this would be great.
>> > >
>> > > Cheers,
>
gt; I can only test this tomorrow though in the production
>> >> > environment.
>> >> > > > > >>
>> >> > > > > >> I can work around this issue for our use-case by copying the
>> >> fixed
>> >> > > > sink
The Flink PMC is pleased to announce the availability of Flink 1.0.2.
The official release announcement:
http://flink.apache.org/news/2016/04/22/release-1.0.2.html
Release binaries:
http://apache.openmirror.de/flink/flink-1.0.2/
Please update your Maven dependencies to the new 1.0.2 version and
Hey all,
thanks to Robert for starting the discussion.
- FLINK-3790 is merged
- FLINK-3800 looks good to merge after a test issue is resolved
- FLINK-3701 needs some feedback on the latest changes
After we have resolved these, I can kick off the first RC for 1.0.3.
Are there any other fixes we
On Mon, Apr 25, 2016 at 12:14 AM, Matthias J. Sax wrote:
> What do you think about this?
Hey Matthias!
Thanks for bringing this up.
I think it is very desirable to keep support for Eclipse. It's quite a
high barrier for new contributors to enforce a specific IDE (although
IntelliJ is gaining qu
quite annoying: https://issues.apache.org/jira/browse/FLINK-3678
>
> In my opinion its a bugfix we can include into the release.
> Any objections?
>
> On Mon, Apr 25, 2016 at 10:48 AM, Ufuk Celebi wrote:
>
>> Hey all,
>>
>> thanks to Robert for starting the discu
27;m currently working on the Flink+Bigtop integration and I found this
>> > issue quite annoying: https://issues.apache.org/jira/browse/FLINK-3678
>> >
>> > In my opinion its a bugfix we can include into the release.
>> > Any objections?
>> >
>>
Hi Till,
thank you for bringing this up. We really need to fix this.
Filing JIRAs with critical priority was how we tried to solve it in
the past, but obviously it did not work. There seems to be a mismatch
between assigned and actual priorities.
As a first step, I would volunteer to gather a li
ering some hard-to-catch race conditions.
– Ufuk
On Wed, Apr 27, 2016 at 2:01 PM, Greg Hogan wrote:
> We have also started running over Travis' 2 hour limit for the longest build.
>
> Greg
>
>
>> On Apr 27, 2016, at 7:53 AM, Ufuk Celebi wrote:
>>
>> Hi Till,
sure if the issues is as big as it seems on a first sight.
>> The reason why all the builds of master are red on travis is that the cache
>> of the 5th build is invalid. We have to ask infra to delete the caches and
>> then they'll be green again.
>>
>> On Wed, Ap
The issues mentioned in this thread have been resolved now. Are there
any other fixes you want in for 1.0.3?
– Ufuk
On Mon, Apr 25, 2016 at 3:34 PM, Ufuk Celebi wrote:
> I think FLINK-3803 can be included as well for 1.0.3 (checkpoint stats
> tracker configuration was not picked up).
>
5:16 GMT+02:00 Fabian Hueske :
>
>> I have an easy fix for FLINK-3835 coming up.
>> It's not an urgent fix but if you wait for 1h it is in.
>>
>> 2016-04-27 14:57 GMT+02:00 Ufuk Celebi :
>>
>>> The issues mentioned in this thread have been reso
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.0.3.
The commit to be voted on:
06c5d7651dd2ef670d94ba0d6f0bb922a0aafd1b
Branch:
release-1.0.3-rc1 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
AM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version
> 1.0.3.
>
> The commit to be voted on:
> 06c5d7651dd2ef670d94ba0d6f0bb922a0aafd1b
>
> Branch:
> release-1.0.3-rc1 (see
> https://git1-us-w
This vote is cancelled in favour of RC2.
On Fri, Apr 29, 2016 at 10:10 AM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version
> 1.0.3.
>
> The commit to be voted on:
> 06c5d7651dd2ef670d94ba0d6f0bb9
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.0.3.
The commit to be voted on:
51daef0063169ee276cc4877d52ea42731d884c1
Branch:
release-1.0.3-rc2 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
ls due to the
> WikipediaEditsSourceTest (FLINK-3860).
>
> In addition I checked:
>
> - checked the diffs compared to Flink 1.0.2. No dependencies were added or
> modified. OK
> - MD5 and SHA hashes are OK
> - Signatures are OK
>
> Cheers, Fabian
>
> 2016-04-29
60).
>> > >
>> > > In addition I checked:
>> > >
>> > > - checked the diffs compared to Flink 1.0.2. No dependencies were added
>> > or
>> > > modified. OK
>> > > - MD5 and SHA hashes are OK
>> > > - Sign
diffs compared to Flink 1.0.2. No dependencies were added or
> modified. OK
> - MD5 and SHA hashes are OK
> - Signatures are OK
>
> Cheers, Fabian
>
> 2016-04-29 15:12 GMT+02:00 Ufuk Celebi :
>
>> Dear Flink community,
>>
>> Please vote on releasing the foll
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.0.3.
The commit to be voted on:
f3a6b5f1e8d85d10e1449e2f96291408b781
Branch:
release-1.0.3-rc3 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.
RC2.
> +1 to release.
>
> I checked:
> - building from source (mvn clean install) OK
> - no dependencies added or modified OK
> - hashes OK
> - signatures OK
>
> Cheers, Fabian
>
>
> 2016-05-10 12:06 GMT+02:00 Gyula Fóra :
>
>> + 1 from me
>>
>
This vote has passed with 3 binding +1 votes. Thanks to everyone who
contributed and tested the release candidate.
+1s:
Gyula Fora (binding)
Fabian Hueske (binding)
Ufuk Celebi (binding)
There are no 0s or -1s.
I'll go ahead finalize and package this release.
On Mon, May 9, 2016 at 10:
The Flink PMC is pleased to announce the availability of Flink 1.0.3.
The official release announcement:
http://flink.apache.org/news/2016/05/11/release-1.0.3.html
Release binaries:
http://apache.openmirror.de/flink/flink-1.0.3/
Please update your Maven dependencies to the new 1.0.3 version and
Hey Stephan!
Thanks to you and the others who started this. I really like the
proposal and I'm happy to see my name on some components.
So, +1.
I'd say let's wait until the end of the week/beginning of next week to
see if there is any disagreement with the propsal in the community
(doesn't look
On Fri, May 20, 2016 at 3:32 PM, Timo Walther wrote:
> What are the plans for 1.1.0 release so far?
Hey Timo,
following the 3 months release schedule, a release would be due soon
(June 8th). My personal opinion is that exact date is probably a
little optimistic, but June sounds about right.
We
Hey Fabian,
thank you for this blog post. I added some minor comments in the
document. Great read and great work by you and the others who have
contributed to SQL! :-)
In general, I think that the post is very much an "Internals" post
like the "bits and bytes" one. This is definitely nice, but I
o tackle test stability problems and
> potential involved bugs.
>
> On Wed, Apr 27, 2016 at 2:13 PM, Ufuk Celebi wrote:
>> @Max: I think you wanted to look into whether we can use Apache's
>> Jenkins server for our builds instead of Travis. Did you ever get
>> around
Hey Gyula!
You are right that in this case the memory snapshots go to the job
manager and are part of the save point. The docs seem to be off there.
The whole save point backend and pointer business should be removed
though in favour of making save points self contained and always go to
files. I
Thanks for the effort, Max and Stephan! Happy to see the green light again.
On Mon, May 30, 2016 at 11:03 PM, Stephan Ewen wrote:
> Hi all!
>
> After a few weeks of terrible build issues, I am happy to announce that the
> build works again properly, and we actually get meaningful CI results.
>
>
r maven projects!
>>
>> Best,
>> Flavio
>> On 30 May 2016 23:47, "Ufuk Celebi" wrote:
>>
>>> Thanks for the effort, Max and Stephan! Happy to see the green light again.
>>>
>>> On Mon, May 30, 2016 at 11:03 PM, Stephan Ewe
On Tue, May 31, 2016 at 11:53 AM, Alexander Alexandrov
wrote:
> Can somebody shed a light on the execution semantics of the scheduler which
> will explain this behavior?
The execution IDs are unique per execution attempt. Having two tasks
with the same subtask index running at the same time is un
Hey Tzu-Li! Which commit are you referring to exactly? We just changed
something yesterday and the build docs command now makes sure to use a
specific Jekyll version via Rubygems. The Jekyll version we use is
2.5.3. And with this it works as expected for me.
Previously, we had issues with differen
101 - 200 of 991 matches
Mail list logo
