I agree that incrCounter API works as designed. I looked at other ways to
generate auto increment ids and found that ZooKeeper has been used by some
to do this. Unique numbers would not satisfy my requirement as I am moving
an app from traditional data warehouse to Hadoop. The incrCounter API would
have worked for me if it had supported returning the incremented value.
On Sat, Aug 3, 2013 at 4:45 PM, Ashish Umrani <[EMAIL PROTECTED]>wrote:
> While I whole heartedly agree that it could be useful if counter would
> have returned the incremented value, the purpose of coubter is not that.
> Counters are used for counting incidence occurance.
> I have not read through details ofvtge issue, but if you want to generate
> a unique number, then there could be some otger time based mechanism, which
> would make more sense.
> On Aug 3, 2013 4:40 PM, "Rishi Yadav" <[EMAIL PROTECTED]> wrote:
>> Hi Manish,
>> Can you give some more details. You are accessing counter values from
>> On Wed, Jul 31, 2013 at 5:30 PM, Manish Verma <[EMAIL PROTECTED]
>> > wrote:
>>> I wanted to use the incrCounter API to generate auto increment ids but
>>> the problem is that it doesn't return the incremented value. Does anyone
>>> know why this API does not return the incremented value? And whether it
>>> would be possible to change it to return the incremented value?
>>> Manish V