Yes for editing i use eclipse in the same fashion. If i want to try out a job and see how it performs on hadoop I need job compiled fast.
On another note. I think there will be a lot of dead code in the job(with all the jar files bundles) Is there an optimiser for that i.e to remove classes which mahout never use indirectly I see loading jar takes 10-20 seconds when initializing mapper or reducer. It doesnt affect long running jobs but 20 sec overhead for processing 64MB chunk sucks On Fri, Feb 5, 2010 at 10:19 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > I usually do an initial compilation using mvn package. Then, during > development I use IntelliJ's incremental compilation which generally only > takes a few seconds. Since that compilation doesn't handle things like > copying resources, I get caught out and surprised now and again, but this > works almost all the time. > > On Fri, Feb 5, 2010 at 12:27 AM, Robin Anil <robin.a...@gmail.com> wrote: > > > When developing mahout core/util/examples we dont need to generate math > > often and dont need to tar gzip bzip2 the jar files. We are mostly > > concerned > > with the job file/ jar file. > > Cant there be another target like develop which does this. (waiting 2-3 > > mins > > for a 2 line change is frustrating) > > > > Robin > > > > > > -- > Ted Dunning, CTO > DeepDyve >
