[
https://issues.apache.org/jira/browse/HBASE-18906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208518#comment-16208518
]
Josh Elser commented on HBASE-18906:
------------------------------------
bq. You guys all want to insist on having something to point to and otherwise
don't care. So... ok? Whatever.
Wow, well, actually I just wanted to see if there was a use-case that we could
pass to Anoop that, as a not-so-Phoenix-y developer, would server as a good
example of what a "good API" looks like. If it's purely hypothetical, that's
fine. I didn't mean for that to be a touchy question.
I understand and agree about how these would be generally useful APIs to have.
> Investigate Phoenix usages of Region#waitForXXX APIs
> ----------------------------------------------------
>
> Key: HBASE-18906
> URL: https://issues.apache.org/jira/browse/HBASE-18906
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0-alpha-4
>
>
> While reviewing HBASE-18183, Andy pointed out that Phoenix uses
> waitForFlushesAndCompactions and/or waitForFlushes for diff reasons. This
> issue is to see why they need them and whether alternate ways are possible.
> This seems to be too much internal stuff and a normal CP hook calling these
> would be dangerous.
> If there are alternate ways for Phoenix not to use this and not landing in
> issues (As said by Andy) we should suggest/fix for them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
