[
https://issues.apache.org/jira/browse/HIVE-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214209#comment-13214209
]
Francis Liu commented on HIVE-2781:
-----------------------------------
Navis, my intention was a bit different when I filed this jira. I wouldn't want
to expose the timestamp field to users as we are using it internally for
dealing with concurrent writes and reads on a table. See attached patch. Though
I can a use case for your patch as well, not just what I had in mind for this
Jira :-).
> HBaseSerDe should allow users to specify the timestamp passed to Puts
> ----------------------------------------------------------------------
>
> Key: HIVE-2781
> URL: https://issues.apache.org/jira/browse/HIVE-2781
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 0.9.0
> Reporter: Francis Liu
> Assignee: Navis
> Fix For: 0.9.0
>
> Attachments: HIVE-2781.D1863.1.patch, HIVE-2781.D1863.2.patch,
> HIVE-2781.D1881.1.patch
>
>
> Users may want to specify the timestamp used for Put requests to hbase. Thus
> enabling users to have the same timestamp for a single batch of writes. Which
> would be useful for a number of things. HCatalog's HBase storageHandler
> implementation makes use of this feature to provide users with snapshot
> isolation and write transactions. My proposal is to add the timestamp option
> as a final static member:
> public static final long HBASE_PUT_TIMESTAMP = "hbase.put_timestamp"
> And passing this value to all the Puts created by serialize()
--
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
