[
https://issues.apache.org/jira/browse/HBASE-18905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185400#comment-16185400
]
Duo Zhang commented on HBASE-18905:
-----------------------------------
If we have a tracker then return a Future is not necessary I think. Just add a
method to Tracker is enough?
And I'm still not familiar with the usage of Phoenix. The method we care about
is waitForFlushesAndCompactions, the meaning is not the same with waiting for
one specific flush/compaction to finish. We'd better find out the real usage
first before making any decision?
Thanks.
> 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)
