Hi,
I was wondering whether we should release Flink 0.10.1 soon, as there are
some issues we've identified:
(pending PRs)
- FLINK-3032: Flink does not start on Hadoop 2.7.1 (HDP), due to class
conflict
- FLINK-3011, 3019, 3028 Cancel jobs in RESTARTING state
- FLINK-3021 Fix class loading issue f
Hey,
I would also add FLINK-3012 and FLINK-3036 (both pending PRs).
Thanks!
-Vasia.
On 18 November 2015 at 12:24, Robert Metzger wrote:
> Hi,
>
> I was wondering whether we should release Flink 0.10.1 soon, as there are
> some issues we've identified:
>
> (pending PRs)
> - FLINK-3032: Flink do
+1 for a timely 0.10.1 release
I would like to add FLINK-2974 - periodic kafka offset committer for case
where checkpointing is deactivated
On Wed, Nov 18, 2015 at 12:34 PM, Vasiliki Kalavri <
vasilikikala...@gmail.com> wrote:
> Hey,
>
> I would also add FLINK-3012 and FLINK-3036 (both pending P
@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:
> +1 for a timely 0.10.1 release
>
> I would like to add FLINK-2974 - periodic kafka offset committer for case
> where checkpointing is
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:
*FLINK-3013 you're right :)
On 18 November 2015 at 13:52, Ufuk Celebi wrote:
> 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 FLIN
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 you mean FLINK-3013 or FLINK-3012?
>
> Will merge PRs for FLINK-3036 and FLINK-3013 this afternoon.
>
> On Wed, Nov 18, 2015 at
@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
@Suneel, I think https://issues.apache.org/jira/browse/FLINK-2949 is a new
feature. The 0.10.1 release is intended as a bugfix release only.
FLINK-3013 and FLINK-3036 have been merged to master only. Are there plans
to merge it to "release-0.10" as well?
The list of issues now looks as follows:
Yes forgot about merging them to release-0.10. Will do it right away.
On Nov 19, 2015 9:40 AM, "Robert Metzger" wrote:
> @Suneel, I think https://issues.apache.org/jira/browse/FLINK-2949 is a new
> feature. The 0.10.1 release is intended as a bugfix release only.
>
> FLINK-3013 and FLINK-3036 hav
@Till Should the recent updates to docs/apis/streaming-guide.md be also
merged to 'release 0.10'? There are other related PRs pending.
On Thu, Nov 19, 2015 at 3:42 AM, Till Rohrmann wrote:
> Yes forgot about merging them to release-0.10. Will do it right away.
> On Nov 19, 2015 9:40 AM, "Robert
If they cover things which are also wrongly documented in 0.10, then they
should be merged to 0.10-release as well.
On Thu, Nov 19, 2015 at 10:01 AM, Suneel Marthi
wrote:
> @Till Should the recent updates to docs/apis/streaming-guide.md be also
> merged to 'release 0.10'? There are other related
+1 for a 0.10.1 release pretty soon.
I merged FLINK-2989 (job cancel button doesn't work on YARN).
On Thu, Nov 19, 2015 at 10:10 AM, Till Rohrmann wrote:
> If they cover things which are also wrongly documented in 0.10, then they
> should be merged to 0.10-release as well.
>
> On Thu, Nov 19, 20
Flink-3017, Flink-3022, and some hotfixes u had put in over the past few
days.
Flink-3041 and Flink-3043 are pending PRs at the moment.
On Thu, Nov 19, 2015 at 4:10 AM, Till Rohrmann
wrote:
> If they cover things which are also wrongly documented in 0.10, then they
> should be merged to 0.10-r
Looks like we didn't manage to merge everything today.
(pending PRs)
- FLINK-3021 Fix class loading issue for streaming sources
- FLINK-2974 Add periodic offset committer for Kafka
(merged)
- FLINK-2977 Using reflection to load HBase Kerberos tokens
- FLINK-3024 Fix TimestampExtractor.getCurrentW
Let me look at FLINK-2974 (open PR) to see if it can be merged...
On Thu, Nov 19, 2015 at 10:09 PM, Robert Metzger
wrote:
> Looks like we didn't manage to merge everything today.
>
> (pending PRs)
> - FLINK-3021 Fix class loading issue for streaming sources
> - FLINK-2974 Add periodic offset com
Great, thank you!
Let me know if there is any issue, I'll address it asap. The PR is not
building anymore because you've pushed an update to the Kafka
documentation. I can rebase and merge the PR once you give me green light ;)
Till has merged FLINK-3021, so we might be able to have a first RC to
Actually, I still have another bug related to the optimizer which I would
like to include if possible. The problem is that the optimizer is not able
to push properties properly out of a bulk iteration which in some cases can
lead to rejected Flink jobs.
On Fri, Nov 20, 2015 at 11:10 AM, Robert Met
Hi all,
Wouldnt you think that it would make sense to wait a week or so to find all
the hot issues with the current release?
To me it feels a little bit like rushing this out and we will have almost
the same situation afterwards.
I might be wrong but I think people should get a chance to try thi
>From my experience, frequent bugfix releases are highly appreciated by
users.
There are some pretty serious fixes people are waiting for, and we can
certainly do a 0.10.2 in a bit, if people find more issues.
On Fri, Nov 20, 2015 at 11:25 AM, Gyula Fóra wrote:
> Hi all,
>
> Wouldnt you think
Hey Gyula,
I understand your point, but we already have some important fixes for
0.10.1. It's fair to assume that we will find more issues in the future,
but the bugfix releases have way less overhead than the major releases. I
would still keep the ASAP schedule and would not wait longer (except f
Thanks guys,
I understand your point and you are probably right, if this is a
lightweight process than the earlier the better :)
Gyula
On Fri, Nov 20, 2015 at 11:34 AM Ufuk Celebi wrote:
> Hey Gyula,
>
> I understand your point, but we already have some important fixes for
> 0.10.1. It's fair t
The optimizer bug (https://issues.apache.org/jira/browse/FLINK-3052) should
be fixed with https://github.com/apache/flink/pull/1388.
On Fri, Nov 20, 2015 at 11:37 AM, Gyula Fóra wrote:
> Thanks guys,
>
> I understand your point and you are probably right, if this is a
> lightweight process than
If we find more bugs later on, we could have a 0.10.2, too.
+1 for quick bug fix release.
Question: should bug fix releases contain fixes for core components
only? I would have a fix for a bug in Storm compatibility -- not sure if
it should be included or not
-Matthias
On 11/20/2015 12:35 PM, T
If it' not API breaking, then it can be included imo.
On Fri, Nov 20, 2015 at 1:44 PM, Matthias J. Sax wrote:
> If we find more bugs later on, we could have a 0.10.2, too.
>
> +1 for quick bug fix release.
>
> Question: should bug fix releases contain fixes for core components
> only? I would ha
Nice.
I just would need to get some feedback about it -- I had to change
something in a "hacky way"... Maybe there is a better solution for it...
https://github.com/apache/flink/pull/1387
I there is no better idea about solving the naming issue, I would merge
it into master (there is no 0.10.1 b
It seems that we have merged all critical fixes into the release-0.10
branch.
Since nobody else stepped up as a release manager, I'll do it again.
It has been a while Lets see how the scripts have evolved ;)
On Fri, Nov 20, 2015 at 2:21 PM, Matthias J. Sax wrote:
> Nice.
>
> I just would nee
Thanks for being the release manager. I promise the release script works
like a charm :)
On Sun, Nov 22, 2015 at 12:30 PM, Robert Metzger
wrote:
> It seems that we have merged all critical fixes into the release-0.10
> branch.
> Since nobody else stepped up as a release manager, I'll do it again
I can confirm that.
Sadly, the repository.apache.org server is not as cooperative as I hoped. I
have everything ready for the release, except the staging repository.
I hope to get it done in the next two hours.
On Mon, Nov 23, 2015 at 10:16 AM, Maximilian Michels wrote:
> Thanks for being the re
29 matches
Mail list logo
