[
https://issues.apache.org/jira/browse/HBASE-18906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208595#comment-16208595
]
Josh Elser commented on HBASE-18906:
------------------------------------
bq. Maybe a shruggie would have been better. No desire to comment further.
Understood, Andrew. Sorry for bringing you back in again.
bq. I am not looking to defend against an adversarial questioning of what
Phoenix might or might not be doing. I admit it's a bit unfair for me to bring
this frustration to this issue where there is missing context, so I apologize
for that.
I was definitely not trying to be argumentative here (sorry if I came across
that way), just come up with a minimum set of things that would make sense to
get into alpha-4 and not let scope creep more. Your consideration on good API
design from the HBase POV (and the consideration for those downstream) is
greatly appreciated by me.
> 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)
