Is there any recommendation on how many columns one should have per row. My
columns are < 200 bytes. This will help me to decide if I should shard my
rows with id + <some date/time value>.

Hey Mohit,

See http://hbase.apache.org/book.html#schema.smackdown.rowscols

On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia <[EMAIL PROTECTED]> wrote:
> Is there any recommendation on how many columns one should have per row. My
> columns are < 200 bytes. This will help me to decide if I should shard my
> rows with id + <some date/time value>.

--
Harsh J

Option c, depending on the use case, add a structure to you columns to store the data.
You may want to update this section....
Sent from a remote device. Please excuse any typos...

Mike Segel

On Sep 10, 2012, at 12:30 PM, Harsh J <[EMAIL PROTECTED]> wrote:

> Hey Mohit,
>
> See http://hbase.apache.org/book.html#schema.smackdown.rowscols
>
> On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia <[EMAIL PROTECTED]> wrote:
>> Is there any recommendation on how many columns one should have per row. My
>> columns are < 200 bytes. This will help me to decide if I should shard my
>> rows with id + <some date/time value>.
>
>
>
> --
> Harsh J
>

re:  "You may want to update this section"

Good point.  I will add.

On 9/11/12 6:59 AM, "Michel Segel" <[EMAIL PROTECTED]> wrote:

>Option c, depending on the use case, add a structure to you columns to
>store the data.
>You may want to update this section....
>
>
>Sent from a remote device. Please excuse any typos...
>
>Mike Segel
>
>On Sep 10, 2012, at 12:30 PM, Harsh J <[EMAIL PROTECTED]> wrote:
>
>> Hey Mohit,
>>
>> See http://hbase.apache.org/book.html#schema.smackdown.rowscols
>>
>> On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia
>><[EMAIL PROTECTED]> wrote:
>>> Is there any recommendation on how many columns one should have per
>>>row. My
>>> columns are < 200 bytes. This will help me to decide if I should shard
>>>my
>>> rows with id + <some date/time value>.
>>
>>
>>
>> --
>> Harsh J
>>
>

On Mon, Sep 10, 2012 at 10:30 AM, Harsh J <[EMAIL PROTECTED]> wrote:

> Hey Mohit,
>
> See http://hbase.apache.org/book.html#schema.smackdown.rowscols
Thanks! Is there a way in HBase to get the most recent inserted column? Or
a way to sort columns such that I can manage how many columns I want to
read? In timeseries we might be interested in only most recent data point.

>
>
> On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia <[EMAIL PROTECTED]>
> wrote:
> > Is there any recommendation on how many columns one should have per row.
> My
> > columns are < 200 bytes. This will help me to decide if I should shard my
> > rows with id + <some date/time value>.
>
>
>
> --
> Harsh J
>

Versions is what you're talking about, and by default all queries
return the latest version of updated values.

On Mon, Sep 10, 2012 at 11:04 PM, Mohit Anchlia <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2012 at 10:30 AM, Harsh J <[EMAIL PROTECTED]> wrote:
>
>> Hey Mohit,
>>
>> See http://hbase.apache.org/book.html#schema.smackdown.rowscols
>
>
> Thanks! Is there a way in HBase to get the most recent inserted column? Or
> a way to sort columns such that I can manage how many columns I want to
> read? In timeseries we might be interested in only most recent data point.
>
>>
>>
>> On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia <[EMAIL PROTECTED]>
>> wrote:
>> > Is there any recommendation on how many columns one should have per row.
>> My
>> > columns are < 200 bytes. This will help me to decide if I should shard my
>> > rows with id + <some date/time value>.
>>
>>
>>
>> --
>> Harsh J
>>

--
Harsh J

On Mon, Sep 10, 2012 at 10:59 AM, Harsh J <[EMAIL PROTECTED]> wrote:

> Versions is what you're talking about, and by default all queries
> return the latest version of updated values.
>

No actually I was asking if I have columns with qualifier:

d,b,c,e can I store them sorted such that it is e,d,c,b? This ways I can
just get the most recent qualifier or for timeseries most recent qualifier.

>
> On Mon, Sep 10, 2012 at 11:04 PM, Mohit Anchlia <[EMAIL PROTECTED]>
> wrote:
> > On Mon, Sep 10, 2012 at 10:30 AM, Harsh J <[EMAIL PROTECTED]> wrote:
> >
> >> Hey Mohit,
> >>
> >> See http://hbase.apache.org/book.html#schema.smackdown.rowscols
> >
> >
> > Thanks! Is there a way in HBase to get the most recent inserted column?
> Or
> > a way to sort columns such that I can manage how many columns I want to
> > read? In timeseries we might be interested in only most recent data
> point.
> >
> >>
> >>
> >> On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia <[EMAIL PROTECTED]
> >
> >> wrote:
> >> > Is there any recommendation on how many columns one should have per
> row.
> >> My
> >> > columns are < 200 bytes. This will help me to decide if I should
> shard my
> >> > rows with id + <some date/time value>.
> >>
> >>
> >>
> >> --
> >> Harsh J
> >>
>
>
>
> --
> Harsh J
>

Ah, sorry for assuming that then. I don't know of a way to sort
qualifiers. I haven't seen anyone do that or require it for
unstructured data (i.e. a query like "fetch me the latest qualifier
added to this row"). I suppose you can compare the last two versions
to see what was changed, but I still don't see why you need this?

For timeseries, I'd recommend looking at what OpenTSDB already provides though.

On Mon, Sep 10, 2012 at 11:32 PM, Mohit Anchlia <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2012 at 10:59 AM, Harsh J <[EMAIL PROTECTED]> wrote:
>
>> Versions is what you're talking about, and by default all queries
>> return the latest version of updated values.
>>
>
> No actually I was asking if I have columns with qualifier:
>
> d,b,c,e can I store them sorted such that it is e,d,c,b? This ways I can
> just get the most recent qualifier or for timeseries most recent qualifier.
>
>>
>> On Mon, Sep 10, 2012 at 11:04 PM, Mohit Anchlia <[EMAIL PROTECTED]>
>> wrote:
>> > On Mon, Sep 10, 2012 at 10:30 AM, Harsh J <[EMAIL PROTECTED]> wrote:
>> >
>> >> Hey Mohit,
>> >>
>> >> See http://hbase.apache.org/book.html#schema.smackdown.rowscols
>> >
>> >
>> > Thanks! Is there a way in HBase to get the most recent inserted column?
>> Or
>> > a way to sort columns such that I can manage how many columns I want to
>> > read? In timeseries we might be interested in only most recent data
>> point.
>> >
>> >>
>> >>
>> >> On Mon, Sep 10, 2012 at 10:56 PM, Mohit Anchlia <[EMAIL PROTECTED]
>> >
>> >> wrote:
>> >> > Is there any recommendation on how many columns one should have per
>> row.
>> >> My
>> >> > columns are < 200 bytes. This will help me to decide if I should
>> shard my
>> >> > rows with id + <some date/time value>.
>> >>
>> >>
>> >>
>> >> --
>> >> Harsh J
>> >>
>>
>>
>>
>> --
>> Harsh J
>>

--
Harsh J