flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jincheng sun <sunjincheng...@gmail.com>
Subject Re: [VOTE] Release Apache Flink 1.3.0 (RC3)
Date Mon, 29 May 2017 15:16:20 GMT
Hi Robert,

+1 to release:

Check items have been checked, as follows: (flink-table)

1.Check that the JAVA and SCALA logical plans are consistent.
2.Check that the SQL and Table API logical plans are consistent.
3.Check that UDF, UDTF, and UDAF are working properly in group-windows and
over-windows.
4.Check that all built-in Agg on Batch and Stream are working properly.
5.Let types such as Timestamp, BigDecimal or Pojo flow through UDF. UDTF,
UDAF (input and output types).

Cheers,
SunJincheng


2017-05-29 22:57 GMT+08:00 Gyula Fóra <gyula.fora@gmail.com>:

> Hi,
>
> I have found an issue with rescaling incremental checkpoints:
> https://issues.apache.org/jira/browse/FLINK-6762
>
> I am not sure if this is regarded as a blocker, it depends on our
> assumptions about externalized checkpoints.
>
> What do you think?
>
> Cheers,
> Gyula
>
> Robert Metzger <rmetzger@apache.org> ezt írta (időpont: 2017. máj. 29., H,
> 15:59):
>
> > +1 to release:
> >
> > - Tested building job against staging repository
> > - tested YARN session start and container recovery on YARN
> > - Validated HA on YARN (per job and session mode)
> > - Incremental checkpointing with rocksdb works
> > - FsStatebackend with async snapshots works
> >
> > - Flink builds from source on Linux (includes rat license header check)
> > - source doesn't contain binaries
> > - checked md5 / sha512 sum of source archive (assuming the other sums are
> > valid as well)
> >
> >
> > I noticed one minor thing: the copyright in the NOTICE file is 2014-2016.
> > I'll update it on master and the release branch.
> >
> >
> > On Mon, May 29, 2017 at 12:42 PM, Chesnay Schepler <chesnay@apache.org>
> > wrote:
> >
> > > +1
> > >
> > >  * Builds from source
> > >  * start/stop scripts work
> > >  * logs don't show anything suspicious on startup/shutdown
> > >  * ran some example jobs
> > >  * ran jobs on yarn with exactly-once & RocksDB
> > >      o canceling with savepoint/resuming from savepoint
> > >      o without/with rescaling
> > >  * SideOutputs work
> > >  * Metrics are properly transmitted & displayed in the webUI
> > >
> > >
> > > On 28.05.2017 20:33, Robert Metzger wrote:
> > >
> > >> @Shaoxuan, I don't think missing documentation is a release blocker,
> but
> > >> it's something we should fix asap and with high priority :)
> > >> Since the documentation is not bundled with the release, and the docs
> > are
> > >> build off the "release-x.y" branch, we can always update them (even
> > after
> > >> the release).
> > >>
> > >> However, it makes sense to have the docs ready when we announce the
> > >> release
> > >> so that users can understand how to use the newly released features.
> > >>
> > >> On Sat, May 27, 2017 at 6:14 PM, Chesnay Schepler <chesnay@apache.org
> >
> > >> wrote:
> > >>
> > >> I've responded in the JIRA. In my opinion isn't a functional issue,
> but
> > >>> more about improving
> > >>> error messages/documentation.
> > >>>
> > >>>
> > >>> On 27.05.2017 18:07, Gyula Fóra wrote:
> > >>>
> > >>> Hi!
> > >>>> I have found this issue: https://issues.apache.org/jira
> > >>>> /browse/FLINK-6742
> > >>>>
> > >>>> Not sure if it's a blocker or not (not even completely sure what
> > causes
> > >>>> it
> > >>>> at the moment)
> > >>>>
> > >>>> Gyula
> > >>>>
> > >>>> Shaoxuan Wang <wshaoxuan@gmail.com> ezt írta (időpont:
2017. máj.
> > 27.,
> > >>>> Szo,
> > >>>> 6:30):
> > >>>>
> > >>>> Hi Robert.
> > >>>>
> > >>>>> Will doc update be a blocker for release?
> > >>>>> Release 1.3 has many updates on tableAPI and SQL, and the docs
are
> > kind
> > >>>>> of
> > >>>>> lagging. We are trying the efforts to update the doc as much
as
> > >>>>> possible
> > >>>>> before the release is officially published, but I am hoping
this is
> > >>>>> not a
> > >>>>> blocker for the release.
> > >>>>>
> > >>>>> Shaoxuan
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On Sat, May 27, 2017 at 12:58 AM, Robert Metzger <
> > rmetzger@apache.org>
> > >>>>> wrote:
> > >>>>>
> > >>>>> Hi all,
> > >>>>>
> > >>>>>> this is the second VOTEing release candidate for Flink
1.3.0
> > >>>>>>
> > >>>>>> The commit to be voted on:
> > >>>>>> 760eea8a <
> > http://git-wip-us.apache.org/repos/asf/flink/commit/760eea8
> > >>>>>> a>
> > >>>>>> (*http://git-wip-us.apache.org/repos/asf/flink/commit/760eea8a
> > >>>>>> <http://git-wip-us.apache.org/repos/asf/flink/commit/760eea8a>*)
> > >>>>>>
> > >>>>>> Branch:
> > >>>>>> release-1.3.0-rc3
> > >>>>>>
> > >>>>>> The release artifacts to be voted on can be found at:
> > >>>>>> http://people.apache.org/~rmetzger/flink-1.3.0-rc3
> > >>>>>>
> > >>>>>>
> > >>>>>> The release artifacts are signed with the key with fingerprint
> > >>>>>> D9839159:
> > >>>>>> http://www.apache.org/dist/flink/KEYS
> > >>>>>>
> > >>>>>> The staging repository for this release can be found at:
> > >>>>>> *https://repository.apache.org/content/repositories/orgapach
> > >>>>>> eflink-1122
> > >>>>>> <https://repository.apache.org/content/repositories/orgapach
> > >>>>>> eflink-1122
> > >>>>>> *
> > >>>>>>
> > >>>>>> -------------------------------------------------------------
> > >>>>>>
> > >>>>>>
> > >>>>>> The vote ends on Tuesday (May 30th), 7pm CET.
> > >>>>>>
> > >>>>>> [ ] +1 Release this package as Apache Flink 1.3.0
> > >>>>>> [ ] -1 Do not release this package, because ...
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message