You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Alex Vollmer <al...@evri.com> on 2008/08/19 02:22:08 UTC
Practical limits of timestamp versions
We are looking at storing aggregated web-server log data in HBase and
are curious about the practical limits of the timestamp dimension of
cells. Can we use the timestamp/version dimension to store the event
timestamp? We expect to have thousands of time-related entries per
row. It's not clear if we would be better off using the timestamp in
the column qualifier instead. Any recommendations would be appreciated.
--
Alex Vollmer
Evri -- Helping users make sense of the world's information
Senior Software Engineer
alex@evri.com
RE: Practical limits of timestamp versions
Posted by Jim Kellerman <ji...@powerset.com>.
The range for timestamps is 0 to Long.MAX_VALUE
---
Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)
> -----Original Message-----
> From: Alex Vollmer [mailto:alex@evri.com]
> Sent: Monday, August 18, 2008 5:22 PM
> To: HBase User List
> Subject: Practical limits of timestamp versions
>
> We are looking at storing aggregated web-server log data in HBase and
> are curious about the practical limits of the timestamp dimension of
> cells. Can we use the timestamp/version dimension to store the event
> timestamp? We expect to have thousands of time-related entries per
> row. It's not clear if we would be better off using the timestamp in
> the column qualifier instead. Any recommendations would be appreciated.
>
> --
> Alex Vollmer
> Evri -- Helping users make sense of the world's information
> Senior Software Engineer
> alex@evri.com