hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-3880) Make mapper function in ImportTSV plug-able
Date Thu, 19 May 2011 00:33:47 GMT

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

Bill Graham updated HBASE-3880:
-------------------------------

    Attachment: HBASE-3880_2.patch

Here's a second version of the patch.

It contains the changes discussed above except I didn't change the {{setup}} method to public,
since that seems unnecessary. I did however add a {{doSetup}} method to split out the generic
setup functionality that a subclass might want from the required specific setup functionality
that a superclass needs (i.e. parser initialization). See the test mapper for an example.

> Make mapper function in ImportTSV plug-able
> -------------------------------------------
>
>                 Key: HBASE-3880
>                 URL: https://issues.apache.org/jira/browse/HBASE-3880
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Bill Graham
>            Assignee: Bill Graham
>         Attachments: HBASE-3880_1.patch, HBASE-3880_2.patch
>
>
> It would be really useful to allow the ability to specify a different Mapper for the
{{ImportTsv}} class to use than the current {{TsvImporter}}. This would allow transformations
to be made on the input data before being added to HBase. One suggestion is to add a new command
line option to specify a user defined mapper (UDM?). Or maybe instead we just refactor it
to be extended where a subclass can specify a new mapper.
> The mapper is statically defined and bound to the job though, so I'm not sure of the
best way to make it dynamically plug-able. Suggestions welcome.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message