Hi all,
I have a question about an issue regarding counters increment versions in
HBase:

I see this issue (HBase-3398) was resolved as "Not A Problem" with a
release note of: "maxversion is set to 1".

Does that mean that Column Families containing counters should be limited
to 1 version ? What were the implications of that issue that noted it in
the first place ?

Thanks!

That JIRA was submitted based on 0.90

What version are you using ?

You can take a look at TestFromClientSide#testIncrement where various
scenarios are tested.

Cheers

On Wed, Mar 13, 2013 at 2:21 PM, Amit Sela <[EMAIL PROTECTED]> wrote:

> Hi all,
> I have a question about an issue regarding counters increment versions in
> HBase:
>
> I see this issue (HBase-3398) was resolved as "Not A Problem" with a
> release note of: "maxversion is set to 1".
>
> Does that mean that Column Families containing counters should be limited
> to 1 version ? What were the implications of that issue that noted it in
> the first place ?
>
> Thanks!
>

I'm using 0.94.2 - but I came across this issue while googling and the
resolve note of 1 max versions looked a bit odd to me since I recall that
counters use versions for example when a time range is expired and the
counter is reset.
Thanks.
On Mar 14, 2013 12:43 AM, "Ted Yu" <[EMAIL PROTECTED]> wrote:

> That JIRA was submitted based on 0.90
>
> What version are you using ?
>
> You can take a look at TestFromClientSide#testIncrement where various
> scenarios are tested.
>
> Cheers
>
> On Wed, Mar 13, 2013 at 2:21 PM, Amit Sela <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> > I have a question about an issue regarding counters increment versions in
> > HBase:
> >
> > I see this issue (HBase-3398) was resolved as "Not A Problem" with a
> > release note of: "maxversion is set to 1".
> >
> > Does that mean that Column Families containing counters should be limited
> > to 1 version ? What were the implications of that issue that noted it in
> > the first place ?
> >
> > Thanks!
> >
>