hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1684) Backup (Export/Import) contrib tool for 0.20
Date Fri, 24 Jul 2009 05:54:14 GMT

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

stack commented on HBASE-1684:
------------------------------

What should the contrib be called? 'backupmr'?  How about dump?  ExportMR and ImportMR should
implement Tool.  See the HStoreFileToStoreFile for sample.  Then they can take command line
arguments.  Why have a map in ExportMR?  It does nothing.  Same for reducer?  Just use Identity
Map?  For ImportMR, reduce does nothing either.   Just don't have it in there and set reducer
to zero in the job setup.  Rather than a contrib, lets just add this to mapreduce package?


> Backup (Export/Import) contrib tool for 0.20
> --------------------------------------------
>
>                 Key: HBASE-1684
>                 URL: https://issues.apache.org/jira/browse/HBASE-1684
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: contrib
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1684-v1.patch
>
>
> Add a new Result/KeyValue based Export MapReduce job to contrib for 0.20.
> Make it in the hadoop 0.20 and hbase 0.20 MR API, and hbase 0.20 API (Result/Put).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message