hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-18906) Investigate Phoenix usages of Region#waitForXXX APIs
Date Tue, 17 Oct 2017 16:25:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207873#comment-16207873
] 

Josh Elser edited comment on HBASE-18906 at 10/17/17 4:24 PM:
--------------------------------------------------------------

bq. Checking the Phoenix master branch I could not see usage of these waitFor APIs. Though
it is having a wait logic

[~anoop.hbase], Yes, that's what was trying to be explained earlier. Phoenix does not presently
use (internal only?) APIs, instead they have hack-y logic which tries to guess at this.

The request was that "stable and consumable APIs" would be created by HBase for the purpose
of Phoenix safely consuming.

(edit: fixed grammar)


was (Author: elserj):
bq. Checking the Phoenix master branch I could not see usage of these waitFor APIs. Though
it is having a wait logic

[~anoop.hbase], Yes, that's what was trying to be explained earlier. Phoenix does not presently
use (internal only?) APIs, instead they have hack-y logic tries to guess at this.

The request was that "stable and consumable APIs" would be created by HBase for the purpose
of Phoenix safely consuming.

> 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)

Mime
View raw message