Thank you both for the follow-up.

2 other questions that pertain to this:
1) I don't remember any natives being required for Oozie so is there a
reason why we don't release with a -bin like most other apache projects?
2) Are there any issues I might expect to run into when trying to run this
on EC2 backed by EMR?

--
Matt


On Thu, Dec 13, 2012 at 5:48 PM, Alejandro Abdelnur <[email protected]>wrote:

> Matt,
>
> Apache Oozie release artifacts are sources only. The easiest way to build
> the TARBALL is:
>
> * install Maven
> * run bin/mkdistro.sh -DskipTests
>
> Then follow the Quick Start instructions.
>
> I'll open a JIRA to add this to the docs.
>
>
> On Thu, Dec 13, 2012 at 3:36 PM, Matt Goeke <[email protected]>
> wrote:
>
> > All,
> >
> > I am falling back to Oozie 3.2 for now but can someone possibly explain
> how
> > Oozie 3.3 is supposed to be configured? I was hoping to just follow the
> > quick start guide but it seems like the packaging does not match up at
> all.
> >
> > Trying to work through it I ended up downloading maven and running a 'mvn
> > install' on the folder which built some of the hadooplibs but I am still
> > missing all of the bin scripts.
> >
> > --
> > Matt
> >
>
>
>
> --
> Alejandro
>

Reply via email to