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

Mubarak Seyed commented on HBASE-4720:
--------------------------------------

Thanks Stack.

bq. Suggest you not do stuff like below in future because it bloats your patch 
making it more susceptible to rot and besides is not related directly to what 
you are trying to your fix so distracting for reviewers (for the next time):
I had formatted the code using 
[-HBASE-3678-|https://issues.apache.org/jira/browse/HBASE-3678] 
{{eclipse_formatter_apache.xml}}. I apologize for messing up with format. Can 
you please advice on code formatting? (i believe hbase book also refers 
HBASE-3678 for code formatting)

bq. Is this safe? e.g. what if row has binary characters in it? Should these be 
base64'd or something?
Other test methods in 
{{src/test/java/org/apache/hadoop/hbase/rest/TestRowResources.java}} uses the 
same way to build the URI ({{deleteRow, deleteValue, putValuePB,}} etc). I just 
copied the code from other methods.

bq. You have some lines that are way too long.
{{eclipse-code-formatter.xml}} uses line length as 80, please advice on line 
length. 

{code}
<setting id="org.eclipse.jdt.core.formatter.comment.line_length" value="80"/>
{code}
                
> Implement atomic update operations (checkAndPut, checkAndDelete) for REST 
> client/server 
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-4720
>                 URL: https://issues.apache.org/jira/browse/HBASE-4720
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Daniel Lord
>            Assignee: Mubarak Seyed
>             Fix For: 0.94.0
>
>         Attachments: HBASE-4720.trunk.v1.patch, HBASE-4720.v1.patch, 
> HBASE-4720.v3.patch
>
>
> I have several large application/HBase clusters where an application node 
> will occasionally need to talk to HBase from a different cluster.  In order 
> to help ensure some of my consistency guarantees I have a sentinel table that 
> is updated atomically as users interact with the system.  This works quite 
> well for the "regular" hbase client but the REST client does not implement 
> the checkAndPut and checkAndDelete operations.  This exposes the application 
> to some race conditions that have to be worked around.  It would be ideal if 
> the same checkAndPut/checkAndDelete operations could be supported by the REST 
> client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to