hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Rodionov <vladrodio...@gmail.com>
Subject Re: Need guidance on Custom Compaction Policy
Date Wed, 22 Mar 2017 19:36:05 GMT
Older files will be purged by default HBase compactor if all data inside
expired (you have TTL for data?)

As for custom compaction policy you can refer to FIFOCompactionPolicy class
to get the idea how custom compaction works.


On Wed, Mar 22, 2017 at 12:29 PM, jeff saremi <jeffsaremi@hotmail.com>

> I mentioned some of this in another thread. We have a readonly database
> which get bulk loaded using HFiles.
> We want to keep only two versions/generations of data. Since the size of
> data is massive we need to delete the older generation.
> Since we write one single HBase for each region for each CF for each
> generation, could we just yank the older files using a separate standalone
> process? (sounds a little scary)
> If not, could we write a custom compactor? what's involved (some pointers
> please)? thanks
> Jeff

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message