[
https://issues.apache.org/jira/browse/HBASE-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220008#comment-16220008
]
Anoop Sam John commented on HBASE-19033:
----------------------------------------
So for control of TTL/versions etc at time of flush/compaction, we have to add
back these hooks? In mail thread u say so. But in another jira we discussed
that the preFlush/Compaction hook can change the scan info and get things done
right?
On in memory compaction - The flatten and merge op will not remove any versions
based on TTL/version. Only the compact mode will do this. That time we will
open up scanner (with SQM) for reading the cells to be preserved and SQM will
remove some TTL/version expired cells. So u mean this wont call the preFlush
kind of hooks and so we are in trouble? hmm.. may be new one hook at least
would be needed then,
> Allow CP users to change versions and TTL before opening StoreScanner
> ---------------------------------------------------------------------
>
> Key: HBASE-19033
> URL: https://issues.apache.org/jira/browse/HBASE-19033
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 2.0.0-alpha-4
>
>
> See the discussion in HBASE-19001. Changing versions and TTL is safe for
> flush/compaction so we can expose them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
