You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Xuesen Liang (JIRA)" <ji...@apache.org> on 2017/01/11 01:44:58 UTC

[jira] [Assigned] (HBASE-8115) Consolidate Import and ImportTsv into a single, user-extensible Import utility

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

Xuesen Liang reassigned HBASE-8115:
-----------------------------------

    Assignee: Xuesen Liang

> Consolidate Import and ImportTsv into a single, user-extensible Import utility
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-8115
>                 URL: https://issues.apache.org/jira/browse/HBASE-8115
>             Project: HBase
>          Issue Type: Sub-task
>          Components: mapreduce, Usability
>            Reporter: Nick Dimiduk
>            Assignee: Xuesen Liang
>
> Import and ImportTsv are very similar tools. The distinction between them is the data input format they consume. Once they've configured their mappers, the rest is pretty much identical. ImportTsv is designed to be an extensible import utility, allowing the mapper to be replaced via configuration. In theory, Import's mapper could be substituted. Let's put these together, making ImportTsv a working example of how to extend Import.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)