Ok. I will make sure a release announcement mentions this issue and that the fix will be in 1.4.3.
On Feb 18, 2018, at 3:41 PM, Chia-Ping Tsai <[email protected]> wrote: >> It will be a month until 1.4.3. Can this wait? Sounds bad but we already >> have two releases out there where this didn't come up? Maybe nobody is >> making use of BufferedMutator and 1.4 yet? > Got it. Let us concentrate on 1.4.2 rc. > >> On 2018/02/18 19:10:16, Andrew Purtell <[email protected]> wrote: >> It will be a month until 1.4.3. Can this wait? Sounds bad but we already >> have two releases out there where this didn't come up? Maybe nobody is >> making use of BufferedMutator and 1.4 yet? >> >> If you would like to veto this RC for this reason that's no problem, in >> which case I will pick up the latest changes to branch-1.4 and try again >> with RC1 later this week. >> >> >>> On Feb 18, 2018, at 1:54 AM, Chia-Ping Tsai <[email protected]> wrote: >>> >>> hi Andrew, >>> >>> Could we add HBASE-20017 to 1.4.2? The issue is related to data lose. >>> >>>> On 2018/02/16 21:46:17, Andrew Purtell <[email protected]> wrote: >>>> The first HBase 1.4.2 release candidate (RC0) is available for download at >>>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC0/ and Maven >>>> artifacts are available in the temporary repository >>>> https://repository.apache.org/content/repositories/orgapachehbase-1195/ . >>>> >>>> The git tag corresponding to the candidate is '1.4.2RC0' (9519ec2ead). >>>> >>>> A detailed source and binary compatibility report for this release is >>>> available for your review at https://dist.apache.org/repos/ >>>> dist/dev/hbase/hbase-1.4.2RC0/compat-check-report.html . >>>> >>>> A list of the 19 issues resolved in this release can be found at >>>> https://s.apache.org/aGcb . >>>> >>>> Please try out the candidate and vote +1/0/-1. >>>> >>>> This vote will be open for at least 72 hours. Unless objection I will try >>>> to close it Friday February 23, 2018 if we have sufficient votes. >>>> >>>> Prior to making this announcement I made the following preflight checks: >>>> >>>> - RAT check passes (7u80) >>>> - Unit test suite passes (8u131) >>>> - LTT load 1M rows with 100% verification and 20% updates (8u131) >>>> - PE sequentialWrite, sequentialRead, randomWrite, randomRead, >>>> scanRange100 (8u131) >>>> - ITBLL Loop 1 100M rows (8u131) >>>> >>>> >>>> -- >>>> Best regards, >>>> Andrew >>>> >>
