[
https://issues.apache.org/jira/browse/HBASE-22148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808130#comment-16808130
]
stack commented on HBASE-22148:
-------------------------------
You are trying to ensure that each data table entry has a unique timestamp? Are
the timestamps in the index table always unique? If so, how is that done?
Each cell gets its own unique sequenceid if that'd help?
I had a look at PHOENIX-4089. The language is speculative and talks about
"...based on the locking we do, Phoenix thinks a different Put was the last one
than HBase does, leading to inconsistencies." Are we trying to reorder Cells
that have arrived at hbase by setting timestamps?
Just trying to understand.
> Provide an alternative to CellUtil.setTimestamp
> ------------------------------------------------
>
> Key: HBASE-22148
> URL: https://issues.apache.org/jira/browse/HBASE-22148
> Project: HBase
> Issue Type: New Feature
> Components: API, Coprocessors
> Affects Versions: 3.0.0
> Reporter: Thomas D'Silva
> Priority: Blocker
> Labels: phoenix
> Fix For: 3.0.0
>
>
> {{CellUtil.setTimestamp}} has been deprecated in 2.0 and is marked for
> removal in 3.0. Phoenix currently uses this api to set the timestamp of cells
> in its indexing coprocessor for tables that have mutable indexes. We can't
> use the CellBuilder api since this involves creating a copy of the cell which
> will be expensive.
> FYI @stack
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
