hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18649) Deprecate KV Usage in MR to move to Cells in 3.0
Date Fri, 25 Aug 2017 08:12:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141357#comment-16141357
] 

ramkrishna.s.vasudevan commented on HBASE-18649:
------------------------------------------------

bq.Ya the ExtendedCell having direct APIs for doing these. But we have utils which take Cell
and serialize also right? The format will be KV format. 
One thing is that we can safely allow the KV format as the mapper/reducer's value class. And
safely do a type cast to ExtendedCell to use those APIs. But in other places it is not straight
forward. We may have to do some KV INFRA sizes to make up what we want. 
And more over the important thing is that KeyValue that is getting used now is
bq.@InterfaceAudience.Private
So making ExtendedCell as the mappers output value class in my opinion is not for the users
to set it. If they want to set it let them set it to KV which is anyway of type ExtendedCell.




> Deprecate KV Usage in MR to move to Cells in 3.0
> ------------------------------------------------
>
>                 Key: HBASE-18649
>                 URL: https://issues.apache.org/jira/browse/HBASE-18649
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>    Affects Versions: 2.0.0-alpha-2
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0, 3.0.0, 2.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message