[
https://issues.apache.org/jira/browse/HBASE-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221393#comment-16221393
]
stack commented on HBASE-19095:
-------------------------------
[~Apache9] comments from dev list on the 'Moving 2.0 forward' thread:
{code}
As Anoop suggested in HBASE-19001, we still need to give user the ability
to extend the max versions and TTL config, so I plan to add back the hooks
above to let CP users can change the max versions and TTL of a ScanInfo
object. But I'm not sure whether in memory compaction will also discard
expired cells, if so then we are in trouble...
....
OK, skimmed, we are in trouble! The in memory compaction just use the same
constructor with normal compaction to construct a StoreScanner, and use it
to do compaction...
We have to provide several preXXX and postXXX for it, at least we should
allow user reset TTL and max versions, and also do filtering on the scanner.
{code}
So, the in-memory compaction needs to call the hooks and it is not doing this
currenlty. Is that the concern [~Apache9]? Thanks sir.
> Add CP hooks in RegionObserver for in memory compaction
> -------------------------------------------------------
>
> Key: HBASE-19095
> URL: https://issues.apache.org/jira/browse/HBASE-19095
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Duo Zhang
> Fix For: 2.0.0-alpha-4
>
>
> This is a hole in our CP hooks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
