One potentially blocking issue that I can see is
https://issues.apache.org/jira/browse/HBASE-20723 which causes potential
dataloss when recovering from a RS crash when a custom WAL directory is set
(hbase.wal.dir).

Josh and I had some discussion on the issue and since this is not a default
config, I believe it is okay to let this slip to a 1.4.6 as long as we
release 1.4.6 as quickly as we have been releasing the other 1.4.x line :)

Just wanted to call this out to get greater awareness.

Thanks,
Zach

On Wed, Jun 13, 2018 at 10:18 PM, Chia-Ping Tsai <chia7...@apache.org>
wrote:

> +1 (binding)
>
> jdk_1.8.0_171
>
> unit tests - all pass
> web UI - LGTM
> CRUD by shell - LGTM
>
> On 2018/06/13 19:53:33, Josh Elser <els...@apache.org> wrote:
> > Hi,
> >
> > Please vote to approve the following as Apache HBase 1.4.5. The only
> > change in RC1 over RC0 is the updated CHANGES.txt.
> >
> > https://dist.apache.org/repos/dist/dev/hbase/1.4.5RC1/
> >
> > Per usual, there is a source release as well as a convenience binary
> >
> > This is built with JDK7 from the commit:
> > https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=commit;h=
> ca99a9466415dc4cfc095df33efb45cb82fe5480
> > (there is a corresponding tag "1.4.5RC1" for convenience). Please ignore
> > the incorrect commit message (forgot to update that text after rc0).
> >
> > hbase-1.4.5-bin.tar.gz: 1C34A448 DF4E102E 7964C6D8 84C2B1E5 35DD0CAA
> > E67E6B15
> >                          92DB2B10 8A6D3A0F B2D841F7 677EB5C3 8EB6D78F
> > 342CB42F
> >                          8CE90AA6 D62A5362 3C727023 4E8C95EE
> > hbase-1.4.5-src.tar.gz: 61B83966 952D334A FDAE7E3A 11FD8529 90583302
> > 4AC186C4
> >                          2B7BDA11 5CB472A4 34C71466 4DCF90BB 8735F658
> > 20975292
> >                          35319D5C 2287B0DE 64F484C7 42F635D6
> >
> > There is also a Maven staging repository for this release:
> > https://repository.apache.org/content/repositories/orgapachehbase-1221
> >
> > This vote will be open for at least 72 hours (2018/06/16 2000 UTC).
> >
> > - Josh (on behalf of the HBase PMC)
> >
> >
>

Reply via email to