[
https://issues.apache.org/jira/browse/PIG-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cheolsoo Park updated PIG-2924:
-------------------------------
Attachment: PIG-2924.patch
I am attaching a patch that implements Bill's suggestion. To make the
computation of the output size plugable, I did the following:
- Added a new interface called PigStatsOutputSizeComputer.
- Added a default implementation of this interface called
FileBasedOutputSizeComputer.
- Added a new flag via which a custom output size computer can be registered.
- Added unit test cases for both file-based and non-file-based systems.
Basically, I followed the pattern that Bill introduced for the reducer
estimator in PIG-2574. Any comments would be appreciated.
Thanks!
> PigStats should not be assuming all Storage classes to be file-based storage
> ----------------------------------------------------------------------------
>
> Key: PIG-2924
> URL: https://issues.apache.org/jira/browse/PIG-2924
> Project: Pig
> Issue Type: Bug
> Components: tools
> Affects Versions: 0.9.2, 0.10.0
> Reporter: Harsh J
> Assignee: Cheolsoo Park
> Attachments: PIG-2924.patch
>
>
> Using PigStatsUtil (like Oozie does) to collect JobStats for jobs that use a
> HBaseStorage blows up when the stats are asked to be accumulated.
> This is because JobStats (which adds stuff up) is assuming all storages are
> file based and that it can do listStatus/etc. operations on their
> filespec-provided filename. For HBaseStorage, this is set to the tablename
> and there's no such file, leading to an exception (FileNotFound or Invalid
> URI - depending on using 'tablename' or 'hbase://tablename').
--
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
