hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9689) Support using OperationAttributes through shell script
Date Wed, 16 Oct 2013 04:13:00 GMT

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

ramkrishna.s.vasudevan commented on HBASE-9689:
-----------------------------------------------

[~apurtell]
bq.There is no way to have a backwards compatible put command that does not take an attributes
hash, just a timestamp
You can do that.  
{code}
put 't1', 'r1', 'c1', 'value', {TIMESTAMP=>100}
{code}
What i meant was Timstamp cannot be specified as per the older way
{code}
put 't1','r1','value',ts
{code}
The problem is put accepts a set of parameters.  So if we avoid the ts parameter and specify
the ATTRIBUTE instead the timestamp is taken as 'mykeymyvalue'.

> Support using OperationAttributes through shell script
> ------------------------------------------------------
>
>                 Key: HBASE-9689
>                 URL: https://issues.apache.org/jira/browse/HBASE-9689
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.98.0
>
>         Attachments: HBASE-9689_1.patch, HBASE-9689_2.patch, HBASE-9689.patch
>
>
> Currently the ruby scripts for Put does not support setting of Operation Attributes through
shell.  
> It may be useful in some cases and also for testing.  And that would give a full  fledged
support using shell.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message