[
https://issues.apache.org/jira/browse/HBASE-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290721#comment-16290721
]
ramkrishna.s.vasudevan commented on HBASE-19112:
------------------------------------------------
bq.The server side code still has to work only with getTypeByte(). getType is
only for the client side expose. And the fake cells will always throw Exception
on getType() call. So we would never be able to use that in our server side
compares and ops.
My assumpiton here is that server side will be made to work with ExtendedCell
and so we are safer there. Yes if some code in the server tries to pass min/max
type getType() it iwll fail. I think that is probably expected?
bq. I think the hooks like prePut() can allow CP users to do this. These cell
impls also has to impl the getTypeByte().
Here again, should the CP user go with the RawCellBuilder way only? If so he
will only have access to the normal data types and no min/max. If so we should
be ok right? Again am not sure if am trying to answer the question correctly or
may not be getting the issue here precisely.
> 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,
> HBASE-19112_branch-2_1.patch, HBASE-19112_master.patch,
> HBASE-19112_master_1.patch, HBASE-19112_master_1.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)
