| clear query|facets|time |
Search criteria: .
Results from 131 to 140 from
160 (0.107s).
|
|
|
Loading phrases to help you
refine your search...
|
|
Re: delete using server's timestamp - HBase - [mail # user]
|
|
...Thanks for the replies. My table is set to store only one version, but I'd probably delete all previous versions to be safe. I'd therefore use one of these 2 methods: - Del...
|
|
|
Author: Matt Corgan,
2011-01-22, 01:17
|
|
|
delete using server's timestamp - HBase - [mail # user]
|
|
...Is there a way to issue a delete using the server's current timestamp? I see methods using HConstants.LATEST_TIMESTAMP which is extremely expensive since it triggers a Get call. ...
|
|
|
Author: Matt Corgan,
2011-01-21, 20:30
|
|
|
Re: Enable Compression on a Table - HBase - [mail # user]
|
|
...Another issue is that hbase doesn't currently merge small regions together. After doing something similar, my regions shrank from 125mb to 5mb (large prefixes), and since it's time ser...
|
|
|
Author: Matt Corgan,
2011-01-19, 01:20
|
|
|
Re: Verbose logging with compression - HBase - [mail # user]
|
|
...Sounds like all upside to me... was a little tricky to notice since it still compresses without them Matt On Tue, Jan 11, 2011 at 10:14 PM, Stack wrote: ...
|
|
|
Author: Matt Corgan,
2011-01-12, 03:57
|
|
|
Re: Verbose logging with compression - HBase - [mail # user]
|
|
...Turns out this is what happens if you don't have the native libraries set up correctly. The data still gets compressed using the pure java codec, but it doesn't cache the codec and giv...
|
|
|
Author: Matt Corgan,
2011-01-11, 23:24
|
|
|
Verbose logging with compression - HBase - [mail # user]
|
|
...I'm trying to use GZIP compression but running into a logging problem. It appears that every time a block is compressed it logs the following: 2011-01-10 12:40:48,407 INFO org.ap...
|
|
|
Author: Matt Corgan,
2011-01-10, 17:46
|
|
|
Re: how to randomize the primary key which is a timestamp - HBase - [mail # user]
|
|
...You could have prefix = timestamp % 64. Then for a single key lookup, you could calculate the prefix and query just one shard. For a scan, you have to query all shards and merge ...
|
|
|
Author: Matt Corgan,
2011-01-10, 17:04
|
|
|
Re: how to randomize the primary key which is a timestamp - HBase - [mail # user]
|
|
...You can put them all in the same table. If you prefix the keys when written, use a prefix filter when querying. I would choose a prefix window that's about 4 times the number of ...
|
|
|
Author: Matt Corgan,
2011-01-10, 16:41
|
|
|
Re: how to randomize the primary key which is a timestamp - HBase - [mail # user]
|
|
...You can also add a random (or hashed) prefix to the beginning of the key. If your prefix were one byte with values 0-63, you've divided the hot spot into 64 smaller ones, which is bett...
|
|
|
Author: Matt Corgan,
2011-01-10, 16:08
|
|
|
Re: HBase / HDFS on EBS? - HBase - [mail # user]
|
|
...Yeah, EC2 tends to have both low network and disk throughput. We use it because of the flexibility and because throughput isn't a big concern for us. Also, fyi, I'm pretty sure f...
|
|
|
Author: Matt Corgan,
2011-01-05, 16:32
|
|
|
|
