You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ChiaPing Tsai (JIRA)" <ji...@apache.org> on 2016/11/06 11:19:59 UTC
[jira] [Updated] (HBASE-17034) HTable#exist and HTable#existAll are flaky

     [ https://issues.apache.org/jira/browse/HBASE-17034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ChiaPing Tsai updated HBASE-17034:
----------------------------------
    Description: 
# HTable#exist apply the default consistency, but HTable#existAll dosen’t
# HTable#existAll may change the passed Gets , but HTable#exist dosen’t. (HTable#get(Get, boolean) clones the passed Get)

So we have some issues outlined below.
# Can the passed Get be modified? If so, we can save the clone of Get. If not, the HTable#getScanner() modify the passed Scan for some unset variables, so it is ok to modify the passed Get I guess. 
# Should we assign the default Consistency to the passed Get which has an null value of Consistency?
# Should the HTable#exist be implemented by HTable#existAll? If so, it may be duplicated  to [HBASE-16623|https://issues.apache.org/jira/browse/HBASE-16623]. If not, it seems to me that we should unify all exist methods by AP. :)

Any comment? Thanks.

  was:

# HTable#exist apply the default consistency, but HTable#existAll dosen’t
# HTable#existAll may change the passed Gets , but HTable#exist dosen’t. (HTable#get(Get, boolean) clones the passed Get)

So we have some issues outlined below.
# Can the passed Get be modified? If so, we can save the clone of Get. If not, the HTable#getScanner() modify the passed Scan for some unset variables, so it is ok to modify the passed Get I guess. 
# Should we assign the default Consistency to the passed Get which has an null value of Consistency?
# Should the HTable#exist be implemented by HTable#existAll? If so, it may be duplicated  to [HBASE-16953|https://issues.apache.org/jira/browse/HBASE-16593]. If not, it seems to me that we should unify all exist methods by AP. :)

Any comment? Thanks.


> HTable#exist and HTable#existAll are flaky
> ------------------------------------------
>
>                 Key: HBASE-17034
>                 URL: https://issues.apache.org/jira/browse/HBASE-17034
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ChiaPing Tsai
>            Priority: Minor
>
> # HTable#exist apply the default consistency, but HTable#existAll dosen’t
> # HTable#existAll may change the passed Gets , but HTable#exist dosen’t. (HTable#get(Get, boolean) clones the passed Get)
> So we have some issues outlined below.
> # Can the passed Get be modified? If so, we can save the clone of Get. If not, the HTable#getScanner() modify the passed Scan for some unset variables, so it is ok to modify the passed Get I guess. 
> # Should we assign the default Consistency to the passed Get which has an null value of Consistency?
> # Should the HTable#exist be implemented by HTable#existAll? If so, it may be duplicated  to [HBASE-16623|https://issues.apache.org/jira/browse/HBASE-16623]. If not, it seems to me that we should unify all exist methods by AP. :)
> Any comment? Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)