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 Mon, 28 Aug 2017 04:56:00 GMT

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

ramkrishna.s.vasudevan commented on HBASE-18649:

bq. lets not expose non public classes/interfaces here
Here we are not exposing it for the user to configure. Only the io.serializations are actually
exposed. Which includes "KVSerailization".
Generally the mapper's output value class are not configurable whereas we directly set them
if the user tries to use it. 
Since KV is private then we should expose only the interface Cell then as it is public. But
again am not sure if Mappers work with interfaces alone and do they need concrete implementations
as the type?

> 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

View raw message