[
https://issues.apache.org/jira/browse/HBASE-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797129#comment-13797129
]
Andrew Purtell commented on HBASE-9689:
---------------------------------------
bq. What i meant was Timstamp cannot be specified as per the older way
Yes, that was my question exactly. So if anyone wants to use the shell to test
puts, including messing with timestamps, and has learned the old way, after
this change now what they know will not work. I am wondering if there is a way
to keep the old way of specifying timestamps as an alternative.
Of course it's fine that if someone wants to set operation attributes, that the
old way won't work _for that case_.
> 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)
