[CRUNCH-533] Support custom TableInputFormats

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Component/s: IO
• Assignee: Micah Whitacre
• Reporter: Micah Whitacre
• Created: 30/Jun/15 01:53
• Updated: 12/Jul/19 20:14
• Resolved: 02/Jul/15 02:43

Description

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/

Issue Links

• is duplicated by: CRUNCH-687 Support supplying alternate InputFormat for HBaseSourceTarget