hi, hbase users.

this question is about a row-key design pattern I believe.
To append data always an end of table, which row-key structures are recommenable?

multiple threads puts many*many data into table.
in this condition, I want to be sure that all of data are going to append the end of table.

if I used timestamp itself, it could be in disorder.
I believe that hbase is quite enough to use as a message queue.

any ideas?

thanks for your concerns.

This would make the last region a hot spot.

Why do you want this design ?

Thanks

On Oct 4, 2012, at 11:50 PM, Henry JunYoung KIM <[EMAIL PROTECTED]> wrote:

> hi, hbase users.
>
> this question is about a row-key design pattern I believe.
> To append data always an end of table, which row-key structures are recommenable?
>
> multiple threads puts many*many data into table.
> in this condition, I want to be sure that all of data are going to append the end of table.
>
> if I used timestamp itself, it could be in disorder.
> I believe that hbase is quite enough to use as a message queue.
>
> any ideas?
>
> thanks for your concerns.

hi, hbase users.

this question is about a row-key design pattern I believe.
To append data always an end of table, which row-key structures are recommenable?

multiple threads puts many*many data into table.
in this condition, I want to be sure that all of data are going to append the end of table.

if I used timestamp itself, it could be in disorder.
I believe that hbase is quite enough to use as a message queue.

any ideas?

thanks for your concerns.

Hi,

HBase tables are sorted alphabetically. So to add to the end, just
take the biggest key and increment the last byte....

But by doing so, your inserts are going to all go to the same region
server until it moves to the next one and you will end with
hotspotting one server, which will result in bad inserts performances.

So I think you're better to think about another key for your needs.

JM

2012/10/5, JUN YOUNG KIM <[EMAIL PROTECTED]>:
> hi, hbase users.
>
> this question is about a row-key design pattern I believe.
> To append data always an end of table, which row-key structures are
> recommenable?
>
> multiple threads puts many*many data into table.
> in this condition, I want to be sure that all of data are going to append
> the end of table.
>
> if I used timestamp itself, it could be in disorder.
> I believe that hbase is quite enough to use as a message queue.
>
> any ideas?
>
> thanks for your concerns.
>
>
>