Thanks guys for the replies, I missed the cell level TTL feature!
Josh
On Fri, Jun 23, 2017 at 1:01 PM, Anoop John wrote:
> Yes we have per cell level TTL setting from 0.98.9 release onwards.
> That should be the best way for ur usecase.
> See Mutation#setTTL(long)
>
>
Yes we have per cell level TTL setting from 0.98.9 release onwards.
That should be the best way for ur usecase.
See Mutation#setTTL(long)
-Anoop-
On Fri, Jun 23, 2017 at 2:17 PM, yonghu wrote:
> I did not quite understand what you mean by "row timestamp"? As far as I
>
I did not quite understand what you mean by "row timestamp"? As far as I
know, timestamp is associated to each data version (cell). Will you store
multiple data versions in a single column?
On Thu, Jun 22, 2017 at 4:35 AM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:
> Why not using
Why not using the cell level ttl?
Le 2017-06-21 2:35 PM, "Vladimir Rodionov" a
écrit :
> Should work
>
> On Wed, Jun 21, 2017 at 11:31 AM, wrote:
>
> > Hi all,
> >
> > I know it is possible to set TTL in HBase at the column family level -
> > which
Should work
On Wed, Jun 21, 2017 at 11:31 AM, wrote:
> Hi all,
>
> I know it is possible to set TTL in HBase at the column family level -
> which makes HBase delete rows in the column family when they reach a
> certain age.
>
> Rather than expire a row after it's reached a
Hi all,
I know it is possible to set TTL in HBase at the column family level - which
makes HBase delete rows in the column family when they reach a certain age.
Rather than expire a row after it's reached a certain age, I would like to
expire each specific row at a specific time in the future