Mailing-List: contact dev-help@mahout.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mahout.apache.org
Date: Tue, 19 Jun 2012 14:00:43 +0000 (UTC)
From: "Timothy Potter (JIRA)" <jira@apache.org>
To: dev@mahout.apache.org
Message-ID: <1211454804.29714.1340114443315.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <321161072.17389.1319142671555.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAHOUT-848) M/R job launching code should add
 Oozie's action.xml as a configuration resource of the Hadoop Configuration
 object
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAHOUT-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396776#comment-13396776 ] 

Timothy Potter commented on MAHOUT-848:
---------------------------------------

Ok, patch supplied on MAHOUT-1033
                
> M/R job launching code should add Oozie's action.xml as a configuration resource of the Hadoop Configuration object
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-848
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-848
>             Project: Mahout
>          Issue Type: Improvement
>          Components: Integration
>    Affects Versions: 0.6
>         Environment: oozie workflow
>            Reporter: Timothy Potter
>            Assignee: Grant Ingersoll
>            Priority: Minor
>              Labels: oozie
>             Fix For: 0.7
>
>         Attachments: MAHOUT-848.patch, MAHOUT-848.patch
>
>
> Here's an overview of what is happening:
> Oozie workflow has a sub-workflow (and in my case a sub-workflow to the sub-workflow, so 3 levels down) that launches a Mahout job, such as the vectorizer as a Java action. This job fails due to class loading issues, e.g. vectorizer code cannot load a Lucene class, which it's definitely in the job jar and definitely gets found just fine if launched from a simple Oozie (1-level) workflow.
> The solution is to include Oozie's action.xml as a configuration resource of the Hadoop Configuration object, i.e.
>         String oozieActionConfXml = System.getProperty("oozie.action.conf.xml");            
>         if (oozieActionConfXml != null) {
>             conf.addResource(new Path("file:///", oozieActionConfXml));
>         }
> As you can see, there's no adverse affects if not running in an Oozie workflow. This code could be added to AbstractJob with minimal impact and much benefit to those of us using Mahout in our Oozie workflows.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira