Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 14 Mar 2013 23:16:12 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12637107.1363302917124.443898.1363302972995@arcas>
In-Reply-To: <JIRA.12637107.1363302917124@arcas>
References: <JIRA.12637107.1363302917124@arcas>
Subject: [jira] [Created] (HBASE-8115) Consolidate Import and ImportTsv into
 a single, user-extensible Import utility
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Nick Dimiduk created HBASE-8115:
-----------------------------------

             Summary: 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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira