Hi,
This is a good idea, but its other limitations make problem for my design.
Thank you.
On Tue, Sep 24, 2013 at 1:02 AM, Dave Latham wrote:
> What about having all columns in the column family use the same qualifier
> and then setting the max versions for that column family to limit it?
> htt
What about having all columns in the column family use the same qualifier
and then setting the max versions for that column family to limit it?
http://hbase.apache.org/book.html#schema.versions
It would only work if you didn't need to do updates to the cell without
knowing its timestamp or having
Thanks,
I think these limiting does not optimize for my millions of records. And it
is better to change my design.
Don't worry for the language ;)
I don't think there is any mecanism today to limit the number of columns
into a column family.
There might be multiple options but they will all have some drawback.
On option is to have a daily mapreduce job looking at each row and doing
the cleanup. This can work
any cell in the same row.
Sorry because of my poor language!
On Thu, Sep 19, 2013 at 9:28 AM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:
> Hi MBE,
>
> When you are saying "cells with least timestamp being removed" you mean
> versions of the same cell? Or any cell in the same row/cf?
Hi MBE,
When you are saying "cells with least timestamp being removed" you mean
versions of the same cell? Or any cell in the same row/cf?
JM
2013/9/18 M. BagherEsmaeily
> Hi,
> I have a column family that I want the number of columns on it has a
> specific limit, and when this number become
Hi,
I have a column family that I want the number of columns on it has a
specific limit, and when this number becomes greater than the limit, cells
with least timestamp being removed, like TTL on count not time.
Please guide me to find best optimized way.
Thanks.
MBE
