hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10526) Using Cell instead of KeyValue in HFileOutputFormat
Date Fri, 14 Feb 2014 23:25:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jimmy Xiang updated HBASE-10526:

    Status: Patch Available  (was: Open)

Attached a patch that added a new class HFileOutputFormat2. To share the code, most of the
functions in HFileOutputFormat are moved to HFileOutputFormat2.

As long as old client applications don't use the package protected methods/class in HFileOutputFormat,
they will still work as before.

It's recommended to use HFileOutputFormat2.configureIncrementalLoad to configure a corresponding
Job.  If users want to configure the Job themselves, they still need to specify the output
value class to KeyValue (setOutputValueClass) because MR ensures the output value class is
an actual class instead of interface/abstract class.

> Using Cell instead of KeyValue in HFileOutputFormat
> ---------------------------------------------------
>                 Key: HBASE-10526
>                 URL: https://issues.apache.org/jira/browse/HBASE-10526
>             Project: HBase
>          Issue Type: Sub-task
>          Components: mapreduce
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>         Attachments: hbase-10526.patch
> HFileOutputFormat/KeyValueSortReducer use KeyValue. We should deprecate them and use
Cell instead.

This message was sent by Atlassian JIRA

View raw message