I've store a relatively small value on large table size, so it takes
much space. Of course this is a special case but I wonder what is the
problem if it's a optional feature, and is possible.

On Fri, Nov 14, 2008 at 2:14 AM, Jim Kellerman (POWERSET)
<[EMAIL PROTECTED]> wrote:
> Why do you want to avoid read/write of a long?
> It is certainly not even close to being a performance bottleneck.
>
> ---
> Jim Kellerman, Powerset (Live Search, Microsoft Corporation)
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edward J.
>> Yoon
>> Sent: Wednesday, November 12, 2008 10:44 PM
>> To: [email protected]
>> Subject: Re: A time-stamp
>>
>> In short, sometimes I want to avoid read/write timestamp.
>>
>> On Thu, Nov 13, 2008 at 3:34 PM, Billy Pearson
>> <[EMAIL PROTECTED]> wrote:
>> > Not sure if that's possible
>> > but versions is not timestamp version is how many version of the
>> row/column:
>> > you want to keep
>> > they are stored by timestamp but if you just want to keep the last
>> inserted
>> > version the you want version=1
>> >
>> > Billy
>> >
>> > "Edward J. Yoon" <[EMAIL PROTECTED]> wrote in message
>> > news:[EMAIL PROTECTED]
>> >>
>> >> Hbase adds a time-stamp to each cell entry. BTW, I'd like to use only
>> >> row, column w/o time dimension. For example, create 't1', {NAME =>
>> >> 'f1', VERSIONS => 0}. Is it possible?
>> >>
>> >> --
>> >> Best Regards, Edward J. Yoon @ NHN, corp.
>> >> [EMAIL PROTECTED]
>> >> http://blog.udanax.org
>> >>
>> >
>> >
>> >
>>
>>
>>
>> --
>> Best Regards, Edward J. Yoon @ NHN, corp.
>> [EMAIL PROTECTED]
>> http://blog.udanax.org
>
>



-- 
Best Regards, Edward J. Yoon @ NHN, corp.
[EMAIL PROTECTED]
http://blog.udanax.org

Reply via email to