I have a large HBase table (~10 TB) that has an existing key structure.
Based on some recent analysis, the key structure is causing performance
problems for our current query load. I would like to re-write the table
with a new key structure that performs substantially better.
What is the best way
Have you looked at FuzzyRowFilter ?
Cheers
On Mon, Feb 19, 2018 at 8:00 AM, kitex101 wrote:
> I have key design like:byte[] rowKey =
> =Bytes.add(Bytes.toBytes("3"),Bytes.toBytes(customer_id),
> Bytes.toBytes(timestamp));
> customer_id and timestamp are long type. As
I mentioned the method accepting int because of the example in your first
email.
I verified in Eclipse that Bytes.toBytes(98) would end up in that
method.
I understand in your application data is typed as long. However that is not
shown in your previous example.
On Sat, Feb 17, 2018 at 9:00
I have key design like:byte[] rowKey =
=Bytes.add(Bytes.toBytes("3"),Bytes.toBytes(customer_id),Bytes.toBytes(timestamp));
customer_id and timestamp are long type. As opentsdb uses:[…]I would like to
filter my key by customer_id and timestamp. How do I do that?I have tried
using prefixfilter.
So, it would be like manually getting 4 byte. Actually they are long.
--
Sent from: http://apache-hbase.679495.n3.nabble.com/HBase-User-f4020416.html
Thanks, it all makes sense now.
Cheers.
Saad
On Mon, Feb 19, 2018 at 5:40 AM Anoop John wrote:
> Hi
> Seems you have write ops happening as you mentioned abt
> minor compactions. When the compaction happens, the compacted file's
> blocks will get
Hi
Seems you have write ops happening as you mentioned abt
minor compactions. When the compaction happens, the compacted file's
blocks will get evicted. Whatever be the value of
'hbase.rs.evictblocksonclose'. This config comes to play when the
Store is closed. Means the region