You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/01/24 23:36:37 UTC

[jira] [Commented] (HBASE-10416) Improvements to the import flow

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

Lars Hofhansl commented on HBASE-10416:
---------------------------------------

looks good to me. Thanks Vasu.

> Improvements to the import flow
> -------------------------------
>
>                 Key: HBASE-10416
>                 URL: https://issues.apache.org/jira/browse/HBASE-10416
>             Project: HBase
>          Issue Type: New Feature
>          Components: mapreduce
>            Reporter: Vasu Mariyala
>         Attachments: HBASE-10416.patch
>
>
> Following improvements can be made to the Import logic
> a) Make the import extensible (i.e., remove the filter from being a static member of Import and make it an instance variable of the mapper, make the mappers or variables of interest protected. )
> b) Make sure that the Import calls filterRowKey method of the filter (Useful if we want to filter the data of an organization based on the row key or using filters like PrefixFilter which filter the data in filterRowKey method rather than the filterKeyValue method). The existing test case in TestImportExport#testWithFilter works with this assumption but is so far successful because there is only one row inserted into the table.
> c) Provide an option to specify the durability during the import (Specifying the Durability as SKIP_WAL would improve the performance of restore considerably.) [~lhofhansl] suggested that this should be a parameter to the import.
> d) Some minor refactoring to avoid building a comma separated string for the filter args.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)