Re: [VOTE] Release Apache Flink 1.2.1 (RC1)

2017-04-08 Thread Gyula Fóra
Hi All,

Any updates on this?

It would be nice to get this out soon, the Kafka bug is hurting our prod
jobs big time.

Thanks,
Gyula

On Wed, Apr 5, 2017, 15:27 Ufuk Celebi  wrote:

> @Stefan: What's the state with the RocksDB fixes? I would be +1 to do this.
>
> On Tue, Apr 4, 2017 at 6:05 PM, Chesnay Schepler 
> wrote:
> > Yes, aljoscha already opened one against master:
> > https://github.com/apache/flink/pull/3670
> >
> > On 04.04.2017 17:57, Ted Yu wrote:
> >>
> >> Should the commits be reverted from master branch as well ?
> >>
> >> On Tue, Apr 4, 2017 at 4:59 AM, Aljoscha Krettek 
> >> wrote:
> >>
> >>> The commits around FLINK-5808 have been reverted on release-1.2.
> >>>
>  On 4. Apr 2017, at 12:16, Stefan Richter  >
> >>>
> >>> wrote:
> 
>  I have created a custom build of RocksDB 4.11.2 that fixes a
> significant
> >>>
> >>> performance problem with append operations. I think this should
> >>> definitely
> >>> be part of the 1.2.1 release because this is already blocking some
> users.
> >>> What is missing is uploading the jar to maven central and a testing
> run,
> >>> e.g. with some misbehaved job that has large state.
> 
> 
> > Am 04.04.2017 um 11:57 schrieb Robert Metzger :
> >
> > Thank you for opening a PR for this.
> >
> > Chesnay, do you need more reviews for the metrics changes /
> backports?
> >
> > Are there any other release blockers for 1.2.1, or are we good to go?
> >
> > On Mon, Apr 3, 2017 at 6:48 PM, Aljoscha Krettek <
> aljos...@apache.org>
> > wrote:
> >
> >> I created a PR for the revert: https://github.com/apache/
> >>>
> >>> flink/pull/3664
> >>>
> >>> On 3. Apr 2017, at 18:32, Stephan Ewen  wrote:
> >>>
> >>> +1 for options (1), but also invest the time to fix it properly for
> >>>
> >>> 1.2.2
> >>>
> >>>
> >>> On Mon, Apr 3, 2017 at 9:10 AM, Kostas Kloudas <
> >>
> >> k.klou...@data-artisans.com>
> >>>
> >>> wrote:
> >>>
>  +1 for 1
> 
> > On Apr 3, 2017, at 5:52 PM, Till Rohrmann 
> >>
> >> wrote:
> >
> > +1 for option 1)
> >
> > On Mon, Apr 3, 2017 at 5:48 PM, Fabian Hueske  >
> >>
> >> wrote:
> >>
> >> +1 to option 1)
> >>
> >> 2017-04-03 16:57 GMT+02:00 Ted Yu :
> >>
> >>> Looks like #1 is better - 1.2.1 would be at least as stable as
> >>>
> >>> 1.2.0
> >>>
> >>> Cheers
> >>>
> >>> On Mon, Apr 3, 2017 at 7:39 AM, Aljoscha Krettek <
> >>
> >> aljos...@apache.org>
> >>>
> >>> wrote:
> >>>
>  Just so we’re all on the same page. ;-)
> 
>  There was https://issues.apache.org/jira/browse/FLINK-5808
> which
> >>
> >> was
> 
>  a
> 
>  bug that we initially discovered in Flink 1.2 which was/is
> about
> >>
> >> missing
> 
>  verification for the correctness of the combination of
> >>>
> >>> parallelism
> >>
> >> and
> 
>  max-parallelism. Due to lacking test coverage this introduced
>  two
> >>
> >> more
> >>>
> >>> bugs:
> 
>  - https://issues.apache.org/jira/browse/FLINK-6188: Some
>  setParallelism() methods can't cope with default parallelism
>  - https://issues.apache.org/jira/browse/FLINK-6209:
>  StreamPlanEnvironment always has a parallelism of 1
> 
>  IMHO, the options are:
>  1) revert the changes made for FLINK-5808 on the release-1.2
> >>>
> >>> branch
> >>
> >> and
> 
>  live with the bug still being present
>  2) put in more work to fix FLINK-5808 which requires fixing
> some
> >>>
> >>> problems
> 
>  that have existed for a long time with how the parallelism is
> >>>
> >>> set in
> 
>  streaming programs
> 
>  Best,
>  Aljoscha
> 
> > On 31. Mar 2017, at 21:34, Robert Metzger <
> rmetz...@apache.org>
> >>
> >> wrote:
> >
> > I don't know what is best to do, but I think releasing 1.2.1
> >>>
> >>> with
> >
> > potentially more bugs than 1.2.0 is not a good option.
> > I suspect a good workaround for FLINK-6188
> >  is
> setting
> >>>
> >>> the
> >
> > parallelism manually for operators that can't cope with the
> >>>
> >>> default
> >>
> >> -1
> 

[jira] [Created] (FLINK-6282) Some words was spelled wrong

2017-04-08 Thread Jinjiang Ling (JIRA)
Jinjiang Ling created FLINK-6282:


 Summary: Some words was spelled wrong
 Key: FLINK-6282
 URL: https://issues.apache.org/jira/browse/FLINK-6282
 Project: Flink
  Issue Type: Bug
Reporter: Jinjiang Ling
Priority: Trivial


I find some words was spelled wrong.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)