+1 For some time my pattern has been to use a Driver for each independent M/R algorithm and a Job to execute more than one Driver to accomplish some higher level of functionality (e.g. seq2sparse). But now, a lot of the drivers are themselves orchestrating atomic drivers. Adding the sequential execution mode has also made the drivers less atomic than I had originally intended.
-----Original Message----- From: Frank Scholten [mailto:[email protected]] Sent: Friday, November 04, 2011 1:50 AM To: [email protected] Subject: Re: [jira] [Created] (MAHOUT-870) Driver or Job? Let's pick one and be consistent. On Nov 4, 2011, at 2:26, Shannon Quinn <[email protected]> wrote: > My habit has been naming anything immediately accessible via bin/mahout a > "driver", anything else a "job". I favour this naming convention. > > I'm also inclined towards "job". > > On 11/3/11 9:06 PM, Sebastian Schelter wrote: >> I'd favor Jobs :) >> >> On 04.11.2011 01:57, Grant Ingersoll (Created) (JIRA) wrote: >>> Driver or Job? Let's pick one and be consistent. >>> ------------------------------------------------- >>> >>> Key: MAHOUT-870 >>> URL: https://issues.apache.org/jira/browse/MAHOUT-870 >>> Project: Mahout >>> Issue Type: Improvement >>> Reporter: Grant Ingersoll >>> Priority: Minor >>> >>> >>> Some things are Drivers, some are Jobs, but they all do the same thing. >>> Since we often use these as the main interface into our stuff, let's make >>> it easier for people to find things by being consistent w/ our naming. >>> >>> My vote is Driver. >>> >>> -- >>> 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 >>> >>> >
