Thanks for your suggestions! I think I go the route with a custom XML property file and using the -conf switch when starting the MR-job.
Thanks again for your support. Much appreciated! Regards, Thomas -----Original Message----- From: Doug Meil [mailto:[email protected]] Sent: Donnerstag, 22. September 2011 01:36 To: [email protected] Subject: Re: MR-Job custom property management? If you need to pass args to a mapper-task for example, using the Configuration object (as Stack suggested) is a common pattern. But just don't stick anything huge in there because that config is apparently copied repeatedly in the MR framework. On 9/21/11 12:09 PM, "Stack" <[email protected]> wrote: >On Wed, Sep 21, 2011 at 1:05 AM, Steinmaurer Thomas ><[email protected]> wrote: >> when writing/executing a self-written MR-Job. How are you guys handle >> custom properties? As command-line arguments when starting the MR-job >> or via a property file? >> > >Command-line args works or passing w/ -D if your main is using >GenericOptionsParser then add them to the Job if they need to be passed >out to the cluster or add them to Configuration that is included in job >or distributed out on cluster. > >There are probably more kosher ways of doing this. > >St.Ack
