[
https://issues.apache.org/jira/browse/HBASE-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276565#comment-16276565
]
ramkrishna.s.vasudevan commented on HBASE-19112:
------------------------------------------------
bq. I have a use case that have a factory to rewrite the specified field of a
Cell. The cell impl with rewritten field is a static nested class which isn't
of type RawCell/ExtendedCell. All the custom cells will be pushed to server via
Put#add(Cell) and Table.put(Put).
Reading through your comments, I am not sure I get this fully. so when you want
to create a new cell with rewritten fields you will not use the Builder
(CellBuilder) where was you create a new Cell impl by passing the type byte (as
a byte) also to that new cell?
So can't we just use the CellBuilder way here too? And this is on the client
side I believe.
As per your last comment - yes RawCell is only CP exposed so they can read the
type as a byte too (if needed we can even use ENUM) but the point is they are
read onlys. So if at all they need a cell to be prepared out of it they can use
the RawCellBuilder only (that does not allow setting of seqId)? Infact they can
use CellBuilder also but since Tags cannot be set they need to go with
RawCellBuilder.
> Suspect methods on Cell to be deprecated
> ----------------------------------------
>
> Key: HBASE-19112
> URL: https://issues.apache.org/jira/browse/HBASE-19112
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: Josh Elser
> Assignee: ramkrishna.s.vasudevan
> Priority: Blocker
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19112_branch-2.patch
>
>
> [~chia7712] suggested on the [mailing
> list|https://lists.apache.org/thread.html/e6de9af26d9b888a358ba48bf74655ccd893573087c032c0fcf01585@%3Cdev.hbase.apache.org%3E]
> that we have some methods on Cell which should be deprecated for removal:
> * {{#getType()}}
> * {{#getTimestamp()}}
> * {{#getTag()}}
> * {{#getSequenceId()}}
> Let's make a pass over these (and maybe the rest) to make sure that there
> aren't others which are either implementation details or methods returning
> now-private-marked classes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
