+1
Ran hbase torture test, checked out documentation, and ran unit tests.
St.Ack
stack wrote:
> Release candidate 4 was voted down because HBASE-613 needed more
> attention and because we weren't splitting under loads if a schema
> with many families: HBASE-707. We also found a deadlock, HBASE-709
> and another area in which we were susceptible to (very) bad clock
> skew: HBASE-710. All these issues have been fixed in the new candidate.
>
> Release candidate 5 is available for download here:
>
> http://people.apache.org/~stack/hbase-0.1.3-candidate-5/
>
> Please try it out and let us know if any issues.
>
> Known issues: HBASE-713 Onlining/Offlining of tables is not reliable
> on biggish tables (hundreds of regions).
>
> Lets make the voting period short, tomorrow, Friday, June 26th.
>
> The HBase Team
>
>
>
> stack wrote:
>> Release candidate 4 adds a fix for HBASE-613:
>>
>> http://people.apache.org/~stack/hbase-0.1.3-candidate-4/
>>
>> Please try it and let us know if issues. Voting closes on Tuesday,
>> June 24th.
>>
>> Thanks,
>> Your HBase Team
>>
>>
>> stack wrote:
>>> Michael Bieniosek reports I'd mangled release candidate 2.
>>>
>>> Here is release candidate 3:
>>>
>>> http://people.apache.org/~stack/hbase-0.1.3-candidate-3/
>>>
>>> Please take it for a spin. Voting (again) closes Friday, June 20th.
>>>
>>> This release only runs on hadoop 0.16.x.
>>>
>>> Yours,
>>> HBase Team
>>>
>>>
>>> stack wrote:
>>>> Here's a new 0.1.3 release candidate:
>>>>
>>>> http://people.apache.org/~stack/hbase-0.1.3-candidate-2/
>>>>
>>>> Please try it out. Voting closes Friday, June 20th.
>>>>
>>>> (Candidate 1 was squashed because a couple of more fixes came in:
>>>> HBASE-680, HBASE-684, and HBASE-686)
>>>>
>>>> Thanks,
>>>>
>>>> The HBase Team
>>>
>>
>
|