[
https://issues.apache.org/jira/browse/HBASE-22148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839788#comment-16839788
]
Sean Busbey commented on HBASE-22148:
-------------------------------------
My read on the dev@hbase thread "Replacement for CellUtil.setTimestamp()" (
https://s.apache.org/eWLd ) is that there's weak consensus for having something
to set timestamps at the {{LimitedPrivate(COPROCESSOR)}}.
That also lines up with the discussion that deprecated things in first place
(HBASE-18995). that jira has concern that LP(CP) will be needed for some
things, but folks didn't want to implement things until there was feedback from
downstream.
The LimitedPrivate designation should mean things remain stable within a given
minor release line, but they might change between them.
Is that stable enough for phoenix's use?
> 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)
