[
https://issues.apache.org/jira/browse/HBASE-18905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185384#comment-16185384
]
Anoop Sam John commented on HBASE-18905:
----------------------------------------
Just initial thought, it may be better to return a Future kind of thing
because that will be the most easy way. We can have the Tracker as param too
as that will be notified at diff steps. May be on failures on Tracker need to
be informed?
> Allow CPs to request flush/compaction on Region
> -----------------------------------------------
>
> Key: HBASE-18905
> URL: https://issues.apache.org/jira/browse/HBASE-18905
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0-alpha-4
>
>
> Follow up for HBASE-18183
> As per that Jira, we keep only requestCompaction API in Region. We did not
> have any such for flush in Region. Only API which was there is a flush which
> will block the callee unless flush is done. This issue has to tacke
> 1. Decide whether we need a requestFlush in Region and if so add
> 2. Whether the requestCompaction (And requestFlush too) should return a
> Future? Right now the former do not return any but allow to pass a
> CompactionLifeCycleTracker which will get notified on start and end of
> compaction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
