[
https://issues.apache.org/jira/browse/HBASE-7267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Tang updated HBASE-7267:
------------------------------
Description:
In HBASE-6059, it introduced a new behavior that the compaction would create
the HFileWriter no mater whether there is any key/value as the output or not.
This new behavior actually is conflicts with HBASE-5199 (Delete out of TTL
store files before compaction selection) so that compacting the expired hfiles
would generate one more expired hfiles.
Actually we only needs to create the dummy hfile IFF the maxSequenceID among
the compaction candidates is equal to the the maxSequenceID among all the
on-disk hfiles.
was:
In HBASE-6059, it introduced a new behavior that the compaction would create
the HFileWriter no mater whether there is any key/value as the output or not.
This new behavior actually is conflicts with HBASE-5199 (Delete out of TTL
store files before compaction selection) so that compacting the expired hfiles
would generate one more expired hfiles.
Actually we only needs to create the dummy hfile iff the maxSequenceID among
the compaction candidates is equal the the maxSequenceID among all the on-disk
hfiles.
> [89-fb] Only create the dummy hfile for the compaction if necessary.
> --------------------------------------------------------------------
>
> Key: HBASE-7267
> URL: https://issues.apache.org/jira/browse/HBASE-7267
> Project: HBase
> Issue Type: Bug
> Reporter: Liyin Tang
>
> In HBASE-6059, it introduced a new behavior that the compaction would create
> the HFileWriter no mater whether there is any key/value as the output or not.
> This new behavior actually is conflicts with HBASE-5199 (Delete out of TTL
> store files before compaction selection) so that compacting the expired
> hfiles would generate one more expired hfiles.
> Actually we only needs to create the dummy hfile IFF the maxSequenceID among
> the compaction candidates is equal to the the maxSequenceID among all the
> on-disk hfiles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
