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

Francis Liu updated HIVE-2781:
------------------------------

    Description: 
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()
        Summary: HBaseSerDe should allow users to specify the timestamp passed 
to Puts   (was: HBaseSerDe should allow users to specify the timestap to be 
used in Puts )
    
> 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
>            Reporter: Francis Liu
>
> 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

        

Reply via email to