ChiaPing Tsai created HBASE-17034:
-------------------------------------
Summary: 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-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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
