[
https://issues.apache.org/jira/browse/CRUNCH-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459253#comment-13459253
]
Roman Shaposhnik commented on CRUNCH-68:
----------------------------------------
Matthias, that was the issue I was alluding to -- sorry for not being clear
enough (I'm just getting into Crunch code based from the Bigtop integration
side of things!).
> Crunch examples don't accept generic tool arguments
> ---------------------------------------------------
>
> Key: CRUNCH-68
> URL: https://issues.apache.org/jira/browse/CRUNCH-68
> Project: Crunch
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.3.0
> Reporter: Roman Shaposhnik
> Assignee: Josh Wills
> Fix For: 0.4.0
>
> Attachments: CRUNCH-68-Fix-command-line-parser-for-examples.patch
>
>
> Currently all crunch examples have the following code:
> {noformat}
> if (args.length != 3) {
> System.err.println();
> System.err.println("Usage: " + this.getClass().getName() + " [generic
> options] input output");
> System.err.println();
> GenericOptionsParser.printGenericCommandUsage(System.err);
> return 1;
> }
> {noformat}
> this is incorrect since run() gets to see all arguments even generic ones and
> thus you can't predict the value of
> args.length.
> This is also, unfortunately a major blocker, for using Crunch with Hadoop 2
> because of a MAPREDUCE-4068.
> Essentially at this point a combination of MAPREDUCE-4068 and inability to
> pass -libjars makes Crunch example DOA for Hadoop 2 clusters.
--
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
