We are currently running with 0.92.0 (cdh4b1) and have configured HA
so that the master will fail over automatically (we will be upgrading
to 0.92.1 cdh4u0 soon). In testing failover we've noticed that in our
long running processes which hold onto an instance of HTable or
HTablePool when the mast
limit to HColumnDescriptor.setMaxVersion(..)?
>
>
> The default for versioning is 3, unfortunately the sub-section also cites
> (incorrectly) that the min is 0. That sub-section is trying to indicate
> the minimum legal value. I am working on clearing that entry up with
> another de
Are you surmising that from the description of setting a minimum version?
On Tue, Oct 4, 2011 at 2:31 PM, Doug Meil wrote:
>
> http://hbase.apache.org/book.html#schema.versions
>
>
> I believe if you set that to 0 it should disable the versioning.
>
>
>
> On 10/4/
might be decided by other consumers of
the service. So having room to grow is ideal.
On Tue, Oct 4, 2011 at 11:36 AM, Doug Meil
wrote:
>
> Hi there-
>
> re: "i don't care store them all"
>
>
> What do you mean?
>
>
>
> On 10/4/11 12:20 PM, &qu
In reading the documentation all I've seen suggestions on how to set
the value and the default value. However I haven't seen any
indication how to set the value to "i don't care store them all" or if
there is a maximum bounds aside from Integer.MAX_VALUE. Does anyone
know?
Thanks,
Micah
[1] -
