The able will, anyway, be splitted in smaller entities (regions) so I don't
see any reason to split it even more than side on your side. If you goal is
to store timetamps, you might want to take a look at OpenTSDB.
2014-01-31 Jürgen Rose <[EMAIL PROTECTED]>:
> Would there be any reason to split a hbase table into smaller entities,
> or can it grow forever (assuming available disk space)?
> We have realtime data (measurements), up to lets say 500,000/s, which
> consists essentially of timestamp, value, flags. If we distribute the
> values to different tables (for each tag), it would also mean to insert
> each of the entries individually, which is a performance killer. If we
> insert in bulk it is much faster. The question is, are there any
> downsides to having a hbase table with an extreme size?
> best regards