hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Csaba Skrabak (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16000) Table#checkAndPut() docs are too vague
Date Tue, 25 Oct 2016 09:47:59 GMT

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

Csaba Skrabak updated HBASE-16000:
----------------------------------
    Assignee:     (was: Csaba Skrabak)
      Status: Patch Available  (was: Open)

> Table#checkAndPut() docs are too vague
> --------------------------------------
>
>                 Key: HBASE-16000
>                 URL: https://issues.apache.org/jira/browse/HBASE-16000
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Nick Dimiduk
>            Priority: Minor
>              Labels: beginner, beginners
>         Attachments: hbase-16000.patch
>
>
> The docs for our CAS operations that accept a {{CompareOp}} are too vague. They're copied
from the part that implies {{CompareOp.EQUAL}}, which means they don't tell you how your op,
the provided {{value}}, and any present value are compared.
> Only by digging into HRegion.java can I see that the operation is, for example with CompareOp.GREATER,
we get {{value.compareTo(existingKeyValue) > 0}}. Javadocs should be explicit about the
order of operands.



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

Mime
View raw message