[
https://issues.apache.org/jira/browse/CRUNCH-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606959#comment-14606959
]
Josh Wills commented on CRUNCH-533:
-----------------------------------
+1-- LGTM.
> 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)
