[
https://issues.apache.org/jira/browse/HBASE-18906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208529#comment-16208529
]
Andrew Purtell edited comment on HBASE-18906 at 10/17/17 10:45 PM:
-------------------------------------------------------------------
Maybe the misunderstanding we keep having is everyone is assuming I am a
Phoenix developer coming here to provide Phoenix feedback. No. I am an HBase
developer. I rarely touch Phoenix. I was involved with the first generation
coprocessor APIs. That's it. If I've made a suggestion where Phoenix is doing
something to my knowledge I've said it, otherwise I am not looking to defend
against an adversarial questioning of what Phoenix might or might not be doing.
was (Author: apurtell):
Maybe the misunderstanding we keep having is everyone is assuming I am a
Phoenix developer coming here to provide Phoenix feedback. No. I am an HBase
developer. I rarely touch Phoenix. I was involved with the first generation
coprocessor APIs. That's it.
> 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)
