Please see HBASE-19099
for the final round of compatibility discussion. Sean and I already had
an exchange with a compatibility fixup resulting.
HBASE-18993 needs someone else to step forward and agree to it. Otherwise
I'd like the change held for further discussion, or at least excluded from
1
See my comment on HBASE-18993.
On Thu, Oct 26, 2017 at 7:24 AM, OpenInx wrote:
> Hi Andrew, I think we can resolve HBASE-18993 in branch-1.x first before
> we roll 1.4.0 RC0 ? The patches are ready, and we are waiting for the
> Hadoop QA & Review .
>
> On Thu, Oct 26, 2017 at 1:50 AM, Andrew P
Hi Andrew, I think we can resolve HBASE-18993 in branch-1.x first before
we roll 1.4.0 RC0 ? The patches are ready, and we are waiting for the
Hadoop QA & Review .
On Thu, Oct 26, 2017 at 1:50 AM, Andrew Purtell wrote:
> Now that HBASE-15631 has been committed I plan to roll 1.4.0 RC0 this wee
Now that HBASE-15631 has been committed I plan to roll 1.4.0 RC0 this week.
Right now I am looking at a few unit tests that are infrequent flakes and
have been on branch-1 and branch-1.4 for a while.
On Wed, Oct 4, 2017 at 2:23 PM, Andrew Purtell wrote:
> I had hoped to make a release candidat
I apologize for being late to this discussion, but will add a few points
here.
Speaking of moving stable pointer to 1.3.2 release, as you say:
>>>"According to our testing at Salesforce, yes, so far. We have yet to run
in
full production. Give us a few months of that and my answer will be
uncondi
As far as I know, Facebook's one use case is the only remaining known place
we are experience FNFE related issues in long scanning / compaction, and
since the time we last talked about it some more fixes have gone in. Our
testing looks good. If they also see good results with latest branch-1.3 I
wo
As said in HBASE-18786 some exception handling for FileNot Found
Exception was the reason for the issues posted by FB. All were actually
related one way or the other. HBASE-18771 has fixed the issue when that
FileNotFound happens.
If facebook can provide feedback post HBASE-18771 I think that ca
Just to be clear my statement was meant to be "I'm looking forward to
seeing rsgroups in a 1.4 release so we can get more feedback on how useful
it is." Realized it could have been read as wanting more feedback prior to
1.4 inclusion.
Cloudera has been shipping the rsgroups feature backported onto
Francis Liu has talked before about how useful this feature has been for
them.
Unfortunately I won't be able to give you personal feedback until some time
after it is out in the 1.4 code line. The way the schedule looks a 1.4.0
release will precede (and be a prerequisite for) enabling rsgroups in
> What ever happened to the issue that was keeping 1.3 from becoming the
stable release line? That still outstanding for 1.4 too?
Yes.
Let me provide some context.
The root issue was fallout from a locking change introduced just prior to
release of 1.3. That change was HBASE-13082. Lars H propos
Sounds great to me. Would love to see more feedback on the utility of the
rsgroups feature.
What ever happened to the issue that was keeping 1.3 from becoming the
stable release line? That still outstanding for 1.4 too?
On Oct 4, 2017 16:24, "Andrew Purtell" wrote:
> I had hoped to make a relea
I had hoped to make a release candidate of 1.4.0 a long time ago when I
first made the branch, but work/life intervened. Sorry it has been slow
going.
I've been making some test fixes to shore up unit test suite results.
As far as big items, at this point a candidate 1.4.0 is only waiting on
HBAS
12 matches
Mail list logo
