You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Micah Whitacre (JIRA)" <ji...@apache.org> on 2015/06/30 03:55:06 UTC
[jira] [Updated] (CRUNCH-533) Support custom TableInputFormats
[ https://issues.apache.org/jira/browse/CRUNCH-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Micah Whitacre updated CRUNCH-533:
----------------------------------
Attachment: CRUNCH-533.patch
Patch that should allow the customization and a simple test showing the custom impl gets picked up.
> Support custom TableInputFormats
> --------------------------------
>
> Key: CRUNCH-533
> URL: https://issues.apache.org/jira/browse/CRUNCH-533
> Project: Crunch
> Issue Type: Improvement
> Components: IO
> Reporter: Micah Whitacre
> Assignee: Micah Whitacre
> Fix For: 0.13.0
>
> Attachments: CRUNCH-533.patch
>
>
> There are certain situations where a custom HBase TableInputFormat might help with performance improvements. While we could require them to create a completely custom HBaseSource, with a minor change consumer could be able to implement the pattern described in the blog very easily (e.g. they own still own their implementation but can easily integrate with Crunch).
> [1] - http://blog.cloudera.com/blog/2015/06/how-to-scan-salted-apache-hbase-tables-with-region-specific-key-ranges-in-mapreduce/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)