[ https://issues.apache.org/jira/browse/HBASE-15181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127610#comment-15127610 ]
Enis Soztutar commented on HBASE-15181: --------------------------------------- bq. Ok keep the sequenceid around always Enis Soztutar.. .then we could do non-contiguous compactions and respect order in which edits were added. Yes. I think the mvcc unification made this 2 weeks, then Lars made it to be 1 day or so because of extra overhead. Bad thing is that we do not want to keep 2 8-byte objects (ts and seqId) per cell. Time to unify seqId with ts. Is this needed? We already do the CompoundConfig in HStore from {{family.getConfiguration()}}. {code} + this.conf = new CompoundConfiguration().add(conf) + .addBytesMap(storeConfigInfo.getHColumnDescriptor().getValues()); {code} Can you also put up the patch at RB. it would be easier that way. > A simple implementation of date based tiered compaction > ------------------------------------------------------- > > Key: HBASE-15181 > URL: https://issues.apache.org/jira/browse/HBASE-15181 > Project: HBase > Issue Type: New Feature > Components: Compaction > Reporter: Clara Xiong > Assignee: Clara Xiong > Fix For: 2.0.0 > > Attachments: HBASE-15181-v1.patch, HBASE-15181-v2.patch > > > This is a simple implementation of date-based tiered compaction similar to > Cassandra's for the following benefits: > 1. Improve date-range-based scan by structuring store files in date-based > tiered layout. > 2. Reduce compaction overhead. > 3. Improve TTL efficiency. > Perfect fit for the use cases that: > 1. has mostly date-based date write and scan and a focus on the most recent > data. > 2. never or rarely deletes data. > Out-of-order writes are handled gracefully so the data will still get to the > right store file for time-range-scan and re-compacton with existing store > file in the same time window is handled by ExploringCompactionPolicy. > Time range overlapping among store files is tolerated and the performance > impact is minimized. > Configuration can be set at hbase-site or overriden at per-table or > per-column-famly level by hbase shell. > Design spec is at > https://docs.google.com/document/d/1_AmlNb2N8Us1xICsTeGDLKIqL6T-oHoRLZ323MG_uy8/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)