You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Morbious <kn...@gmail.com> on 2015/04/17 12:47:10 UTC
Compile oozie 4.0.0
Hi,
I've tried compile oozie with patch recently.
Each time I did this I got an error :
[ERROR] Failed to execute goal on project oozie-webapp: Could not resolve
dependencies for project org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2:
Could not find artifact org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in
cdh.repo (https://repository.cloudera.com/content/groups/cloudera-repos) ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal on project oozie-webapp: Could not resolve dependencies for project
org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2: Could not find artifact
org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in cdh.repo (
https://repository.cloudera.com/content/groups/cloudera-repos)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
It seems that oozie-doc*.war doesn't exist.
I need to compile this due patch which allows me to use UTF8 properly.
Can anyone point me what I'm doing wrong ?
Best regards,
Morbious
Re: Oozie + Sqoop + MySql UPSERT
Posted by Aravindakshan Srinivasan <s_...@yahoo.com.INVALID>.
This is now resolved. Turned out to be a Sqoop issue.
From: Aravindakshan Srinivasan <s_...@yahoo.com>
To: "user@oozie.apache.org" <us...@oozie.apache.org>
Sent: Friday, May 8, 2015 8:53 PM
Subject: Oozie + Sqoop + MySql UPSERT
Friends,
I have an odd problem. I am trying to run an MySql upsert via Sqoop. It works fine from the edge node that has Sqoop 1.4.5 installed. When I try to run via Oozie, I get this error.
org.apache.sqoop.tool.ExportTool - Error during export: Mixed update/insert is not supported against the target database
This feature is available in the newer versions of Sqoop starting with Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first reaction was that the Sqoop jars in Oozie's sharelib are different and hence throwing this error. I tried copying the Sqoop jars from my edge node to the workflow/lib dir. It still didn't work.
Since then, I have tried everything I can think of, but can't get past this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to my rebuilt lib. Still no luck. What am I missing?
Thanks,Aravind
--------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
Re: Oozie + Sqoop + MySql UPSERT
Posted by Aravindakshan Srinivasan <s_...@yahoo.com>.
This is now resolved. Turned out to be a Sqoop issue.
Regards,Aravind
From: Aravindakshan Srinivasan <s_...@yahoo.com>
To: "user@sqoop.apache.org" <us...@sqoop.apache.org>
Sent: Friday, May 8, 2015 9:00 PM
Subject: Oozie + Sqoop + MySql UPSERT
Friends,
I have an odd problem. I am trying to run an MySql upsert via Sqoop. It works fine from the edge node that has Sqoop 1.4.5 installed. When I try to run via Oozie, I get this error.
org.apache.sqoop.tool.ExportTool - Error during export: Mixed update/insert is not supported against the target database
This feature is available in the newer versions of Sqoop starting with Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first reaction was that the Sqoop jars in Oozie's sharelib are different and hence throwing this error. As you know, the Sqoop via Oozie runs on the Hadoop compute nodes. I tried copying the Sqoop jars from my edge node to the workflow/lib dir. It still didn't work.
Since then, I have tried everything I can think of, but can't get past this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to my rebuilt lib. Still no luck. What am I missing?
Thanks,Aravind --------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
Re: Oozie + Sqoop + MySql UPSERT
Posted by Aravindakshan Srinivasan <s_...@yahoo.com>.
Wow, it did work. Why though?
Thanks a lot Abraham.
Regards,Aravind --------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
From: Abraham Elmahrek <ab...@cloudera.com>
To: "user@sqoop.apache.org" <us...@sqoop.apache.org>; Aravindakshan Srinivasan <s_...@yahoo.com>
Sent: Friday, May 8, 2015 11:52 PM
Subject: Re: Oozie + Sqoop + MySql UPSERT
I'd get rid of --driver and see if that works.
On Fri, May 8, 2015 at 11:14 AM, Aravindakshan Srinivasan <s_...@yahoo.com> wrote:
Hi Abraham,
Here's the Sqoop command that works.
sqoop export --connect jdbc:mysql://myhost.rds.amazonaws.com/DB1 --username XXX -password YYY --table test_table --columns "name,ts,age,salary" --update-key "name" --export-dir /user/aravind/test/year=2015/month=5/day=7/hour=19 --fields-terminated-by "\t" --update-mode allowinsert -m 1
The following workflow does not work.
<workflow-app xmlns="uri:oozie:workflow:0.2" name="ara_sqoop-wf"> <start to="ara_move_to_mysql"/> <action name="ara_move_to_mysql"> <sqoop xmlns="uri:oozie:sqoop-action:0.3"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <arg>export</arg> <arg>-libjars</arg> <arg>${wf_folder}lib/mysql-connector-java.jar</arg> <arg>--connect</arg> <arg>jdbc:mysql://myhost.rds.amazonaws.com/${mysql_db}</arg> <arg>--driver</arg> <arg>com.mysql.jdbc.Driver</arg> <arg>--username</arg> <arg>${mysql_usern}</arg> <arg>-password</arg> <arg>${mysql_pswd}</arg> <arg>--table</arg> <arg>${table_name}</arg> <arg>--columns</arg> <arg>"name,ts,age,salary"</arg> <arg>--update-key</arg> <arg>"name"</arg> <arg>--export-dir</arg> <arg>/user/aravind/test/year=2015/month=5/day=7/hour=19</arg> <arg>--fields-terminated-by</arg> <arg>"\t"</arg> <arg>--update-mode</arg> <arg>allowinsert</arg> <arg>-m</arg> <arg>1</arg> </sqoop> <ok to="end"/> <error to="fail"/> </action> <kill name="fail"> <message>Sqoop failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/></workflow-app>
Thanks,Aravind
From: Abraham Elmahrek <ab...@cloudera.com>
To: "user@sqoop.apache.org" <us...@sqoop.apache.org>; Aravindakshan Srinivasan <s_...@yahoo.com>
Sent: Friday, May 8, 2015 10:36 PM
Subject: Re: Oozie + Sqoop + MySql UPSERT
Can you send over your oozie job or sqoop command?
On Fri, May 8, 2015 at 8:30 AM, Aravindakshan Srinivasan <s_...@yahoo.com> wrote:
Friends,
I have an odd problem. I am trying to run an MySql upsert via Sqoop. It works fine from the edge node that has Sqoop 1.4.5 installed. When I try to run via Oozie, I get this error.
org.apache.sqoop.tool.ExportTool - Error during export: Mixed update/insert is not supported against the target database
This feature is available in the newer versions of Sqoop starting with Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first reaction was that the Sqoop jars in Oozie's sharelib are different and hence throwing this error. As you know, the Sqoop via Oozie runs on the Hadoop compute nodes. I tried copying the Sqoop jars from my edge node to the workflow/lib dir. It still didn't work.
Since then, I have tried everything I can think of, but can't get past this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to my rebuilt lib. Still no luck. What am I missing?
Thanks,Aravind --------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
Re: Oozie + Sqoop + MySql UPSERT
Posted by Abraham Elmahrek <ab...@cloudera.com>.
I'd get rid of --driver and see if that works.
On Fri, May 8, 2015 at 11:14 AM, Aravindakshan Srinivasan <
s_aravind@yahoo.com> wrote:
> Hi Abraham,
>
> Here's the Sqoop command that works.
>
> sqoop export --connect jdbc:mysql://myhost.rds.amazonaws.com/DB1
> --username XXX -password YYY --table test_table --columns
> "name,ts,age,salary" --update-key "name" --export-dir
> /user/aravind/test/year=2015/month=5/day=7/hour=19 --fields-terminated-by
> "\t" --update-mode allowinsert -m 1
>
> The following workflow does not work.
>
> <workflow-app xmlns="uri:oozie:workflow:0.2" name="ara_sqoop-wf">
> <start to="ara_move_to_mysql"/>
> <action name="ara_move_to_mysql">
> <sqoop xmlns="uri:oozie:sqoop-action:0.3">
> <job-tracker>${jobTracker}</job-tracker>
> <name-node>${nameNode}</name-node>
> <arg>export</arg>
> <arg>-libjars</arg>
> <arg>${wf_folder}lib/mysql-connector-java.jar</arg>
> <arg>--connect</arg>
> <arg>jdbc:mysql://myhost.rds.amazonaws.com/${mysql_db}
> <http://myhost.rds.amazonaws.com/$%7Bmysql_db%7D></arg>
> <arg>--driver</arg>
> <arg>com.mysql.jdbc.Driver</arg>
> <arg>--username</arg>
> <arg>${mysql_usern}</arg>
> <arg>-password</arg>
> <arg>${mysql_pswd}</arg>
> <arg>--table</arg>
> <arg>${table_name}</arg>
> <arg>--columns</arg>
> <arg>"name,ts,age,salary"</arg>
> <arg>--update-key</arg>
> <arg>"name"</arg>
> <arg>--export-dir</arg>
> <arg>/user/aravind/test/year=2015/month=5/day=7/hour=19</arg>
> <arg>--fields-terminated-by</arg>
> <arg>"\t"</arg>
> <arg>--update-mode</arg>
> <arg>allowinsert</arg>
> <arg>-m</arg>
> <arg>1</arg>
> </sqoop>
> <ok to="end"/>
> <error to="fail"/>
> </action>
> <kill name="fail">
> <message>Sqoop failed, error
> message[${wf:errorMessage(wf:lastErrorNode())}]</message>
> </kill>
> <end name="end"/>
> </workflow-app>
>
> Thanks,
> Aravind
>
> ------------------------------
> *From:* Abraham Elmahrek <ab...@cloudera.com>
> *To:* "user@sqoop.apache.org" <us...@sqoop.apache.org>; Aravindakshan
> Srinivasan <s_...@yahoo.com>
> *Sent:* Friday, May 8, 2015 10:36 PM
> *Subject:* Re: Oozie + Sqoop + MySql UPSERT
>
> Can you send over your oozie job or sqoop command?
>
>
>
> On Fri, May 8, 2015 at 8:30 AM, Aravindakshan Srinivasan <
> s_aravind@yahoo.com> wrote:
>
> Friends,
>
> I have an odd problem. I am trying to run an MySql upsert via Sqoop. It
> works fine from the edge node that has Sqoop 1.4.5 installed. When I try to
> run via Oozie, I get this error.
>
> org.apache.sqoop.tool.ExportTool - Error during export: Mixed
> update/insert is not supported against the target database
>
> This feature is available in the newer versions of Sqoop starting with
> Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first
> reaction was that the Sqoop jars in Oozie's sharelib are different and
> hence throwing this error. As you know, the Sqoop via Oozie runs on the
> Hadoop compute nodes. I tried copying the Sqoop jars from my edge node to
> the workflow/lib dir. It still didn't work.
>
>
>
> Since then, I have tried everything I can think of, but can't get past
> this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and
> tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to
> my rebuilt lib. Still no luck. What am I missing?
>
> Thanks,
> Aravind
>
>
> --------------------------------------------------------------------------------------------
> Aravind Srinivasan
>
> http://goodcynicsports.blogspot.com
>
> I have decided to stick with love. Hate is too great a burden to bear.
> - MLK, Jr.
>
> --------------------------------------------------------------------------------------------
>
>
>
>
>
>
>
Re: Oozie + Sqoop + MySql UPSERT
Posted by Aravindakshan Srinivasan <s_...@yahoo.com>.
Hi Abraham,
Here's the Sqoop command that works.
sqoop export --connect jdbc:mysql://myhost.rds.amazonaws.com/DB1 --username XXX -password YYY --table test_table --columns "name,ts,age,salary" --update-key "name" --export-dir /user/aravind/test/year=2015/month=5/day=7/hour=19 --fields-terminated-by "\t" --update-mode allowinsert -m 1
The following workflow does not work.
<workflow-app xmlns="uri:oozie:workflow:0.2" name="ara_sqoop-wf"> <start to="ara_move_to_mysql"/> <action name="ara_move_to_mysql"> <sqoop xmlns="uri:oozie:sqoop-action:0.3"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <arg>export</arg> <arg>-libjars</arg> <arg>${wf_folder}lib/mysql-connector-java.jar</arg> <arg>--connect</arg> <arg>jdbc:mysql://myhost.rds.amazonaws.com/${mysql_db}</arg> <arg>--driver</arg> <arg>com.mysql.jdbc.Driver</arg> <arg>--username</arg> <arg>${mysql_usern}</arg> <arg>-password</arg> <arg>${mysql_pswd}</arg> <arg>--table</arg> <arg>${table_name}</arg> <arg>--columns</arg> <arg>"name,ts,age,salary"</arg> <arg>--update-key</arg> <arg>"name"</arg> <arg>--export-dir</arg> <arg>/user/aravind/test/year=2015/month=5/day=7/hour=19</arg> <arg>--fields-terminated-by</arg> <arg>"\t"</arg> <arg>--update-mode</arg> <arg>allowinsert</arg> <arg>-m</arg> <arg>1</arg> </sqoop> <ok to="end"/> <error to="fail"/> </action> <kill name="fail"> <message>Sqoop failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/></workflow-app>
Thanks,Aravind
From: Abraham Elmahrek <ab...@cloudera.com>
To: "user@sqoop.apache.org" <us...@sqoop.apache.org>; Aravindakshan Srinivasan <s_...@yahoo.com>
Sent: Friday, May 8, 2015 10:36 PM
Subject: Re: Oozie + Sqoop + MySql UPSERT
Can you send over your oozie job or sqoop command?
On Fri, May 8, 2015 at 8:30 AM, Aravindakshan Srinivasan <s_...@yahoo.com> wrote:
Friends,
I have an odd problem. I am trying to run an MySql upsert via Sqoop. It works fine from the edge node that has Sqoop 1.4.5 installed. When I try to run via Oozie, I get this error.
org.apache.sqoop.tool.ExportTool - Error during export: Mixed update/insert is not supported against the target database
This feature is available in the newer versions of Sqoop starting with Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first reaction was that the Sqoop jars in Oozie's sharelib are different and hence throwing this error. As you know, the Sqoop via Oozie runs on the Hadoop compute nodes. I tried copying the Sqoop jars from my edge node to the workflow/lib dir. It still didn't work.
Since then, I have tried everything I can think of, but can't get past this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to my rebuilt lib. Still no luck. What am I missing?
Thanks,Aravind --------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
Re: Oozie + Sqoop + MySql UPSERT
Posted by Abraham Elmahrek <ab...@cloudera.com>.
Can you send over your oozie job or sqoop command?
On Fri, May 8, 2015 at 8:30 AM, Aravindakshan Srinivasan <
s_aravind@yahoo.com> wrote:
> Friends,
>
> I have an odd problem. I am trying to run an MySql upsert via Sqoop. It
> works fine from the edge node that has Sqoop 1.4.5 installed. When I try to
> run via Oozie, I get this error.
>
> org.apache.sqoop.tool.ExportTool - Error during export: Mixed
> update/insert is not supported against the target database
>
> This feature is available in the newer versions of Sqoop starting with
> Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first
> reaction was that the Sqoop jars in Oozie's sharelib are different and
> hence throwing this error. As you know, the Sqoop via Oozie runs on the
> Hadoop compute nodes. I tried copying the Sqoop jars from my edge node to
> the workflow/lib dir. It still didn't work.
>
>
>
> Since then, I have tried everything I can think of, but can't get past
> this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and
> tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to
> my rebuilt lib. Still no luck. What am I missing?
>
> Thanks,
> Aravind
>
>
> --------------------------------------------------------------------------------------------
> Aravind Srinivasan
>
> http://goodcynicsports.blogspot.com
>
> I have decided to stick with love. Hate is too great a burden to bear.
> - MLK, Jr.
>
> --------------------------------------------------------------------------------------------
>
>
>
>
Oozie + Sqoop + MySql UPSERT
Posted by Aravindakshan Srinivasan <s_...@yahoo.com>.
Friends,
I have an odd problem. I am trying to run an MySql upsert via Sqoop. It works fine from the edge node that has Sqoop 1.4.5 installed. When I try to run via Oozie, I get this error.
org.apache.sqoop.tool.ExportTool - Error during export: Mixed update/insert is not supported against the target database
This feature is available in the newer versions of Sqoop starting with Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first reaction was that the Sqoop jars in Oozie's sharelib are different and hence throwing this error. As you know, the Sqoop via Oozie runs on the Hadoop compute nodes. I tried copying the Sqoop jars from my edge node to the workflow/lib dir. It still didn't work.
Since then, I have tried everything I can think of, but can't get past this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to my rebuilt lib. Still no luck. What am I missing?
Thanks,Aravind --------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
Oozie + Sqoop + MySql UPSERT
Posted by Aravindakshan Srinivasan <s_...@yahoo.com.INVALID>.
Friends,
I have an odd problem. I am trying to run an MySql upsert via Sqoop. It works fine from the edge node that has Sqoop 1.4.5 installed. When I try to run via Oozie, I get this error.
org.apache.sqoop.tool.ExportTool - Error during export: Mixed update/insert is not supported against the target database
This feature is available in the newer versions of Sqoop starting with Sqoop 1.4.3, which is what my Oozie sharelib contains. Still, my first reaction was that the Sqoop jars in Oozie's sharelib are different and hence throwing this error. I tried copying the Sqoop jars from my edge node to the workflow/lib dir. It still didn't work.
Since then, I have tried everything I can think of, but can't get past this error. I have even rebuilt the Oozie sharelib with Sqoop 1.4.5 and tried both oozie.libpath and oozie.action.sharelib.for.sqoop pointing to my rebuilt lib. Still no luck. What am I missing?
Thanks,Aravind --------------------------------------------------------------------------------------------Aravind Srinivasan
http://goodcynicsports.blogspot.com
I have decided to stick with love. Hate is too great a burden to bear. - MLK, Jr.--------------------------------------------------------------------------------------------
Re: Compile oozie 4.0.0
Posted by Robert Kanter <rk...@cloudera.com>.
If you're using the CDH version of Oozie, you should use the Hadoop version
that it normally builds against. i.e.
mvn clean package assembly:single
If you want to use an arbitrary Hadoop version, you should use Apache's
Oozie release, and then you can override the hadoop version like you did;
however, for Hadoop 2.x, you should also add -Phadoop-2. i.e.
mvn clean package assembly:single -Dhadoop.version=2.5.0 -Phadoop-2
- Robert
On Sat, Apr 18, 2015 at 1:06 PM, Morbious <kn...@gmail.com>
wrote:
> Hi,
>
> I use:
>
> mvn clean package assembly:single -Dhadoop.version=2.5.0
>
> (http://archive.cloudera.com/cdh5/cdh/5/oozie/ENG_Building.html)
>
> Each time I get error about doc.war.
>
> Best regards,
>
> Morbious
>
> 2015-04-17 18:50 GMT+02:00 Robert Kanter <rk...@cloudera.com>:
>
> > Hi,
> >
> > What's the command you're using to compile?
> >
> >
> > - Robert
> >
> > On Fri, Apr 17, 2015 at 3:47 AM, Morbious <knowledgefromgroups@gmail.com
> >
> > wrote:
> >
> > > Hi,
> > >
> > > I've tried compile oozie with patch recently.
> > > Each time I did this I got an error :
> > >
> > > [ERROR] Failed to execute goal on project oozie-webapp: Could not
> resolve
> > > dependencies for project
> > org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2:
> > > Could not find artifact org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2
> in
> > > cdh.repo (
> https://repository.cloudera.com/content/groups/cloudera-repos)
> > > ->
> > > [Help 1]
> > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> > > goal on project oozie-webapp: Could not resolve dependencies for
> project
> > > org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2: Could not find
> artifact
> > > org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in cdh.repo (
> > > https://repository.cloudera.com/content/groups/cloudera-repos)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> > > at
> > >
> > >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at
> > >
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > > at
> > >
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > > at java.lang.reflect.Method.invoke(Method.java:497)
> > > at
> > >
> > >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> > > at
> > >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> > > at
> > >
> > >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> > > at
> > >
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > >
> > > It seems that oozie-doc*.war doesn't exist.
> > > I need to compile this due patch which allows me to use UTF8 properly.
> > > Can anyone point me what I'm doing wrong ?
> > >
> > > Best regards,
> > >
> > > Morbious
> > >
> >
>
Re: Compile oozie 4.0.0
Posted by Morbious <kn...@gmail.com>.
Hi,
I use:
mvn clean package assembly:single -Dhadoop.version=2.5.0
(http://archive.cloudera.com/cdh5/cdh/5/oozie/ENG_Building.html)
Each time I get error about doc.war.
Best regards,
Morbious
2015-04-17 18:50 GMT+02:00 Robert Kanter <rk...@cloudera.com>:
> Hi,
>
> What's the command you're using to compile?
>
>
> - Robert
>
> On Fri, Apr 17, 2015 at 3:47 AM, Morbious <kn...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I've tried compile oozie with patch recently.
> > Each time I did this I got an error :
> >
> > [ERROR] Failed to execute goal on project oozie-webapp: Could not resolve
> > dependencies for project
> org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2:
> > Could not find artifact org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in
> > cdh.repo (https://repository.cloudera.com/content/groups/cloudera-repos)
> > ->
> > [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> > goal on project oozie-webapp: Could not resolve dependencies for project
> > org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2: Could not find artifact
> > org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in cdh.repo (
> > https://repository.cloudera.com/content/groups/cloudera-repos)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:497)
> > at
> >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> > at
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> > at
> >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> >
> > It seems that oozie-doc*.war doesn't exist.
> > I need to compile this due patch which allows me to use UTF8 properly.
> > Can anyone point me what I'm doing wrong ?
> >
> > Best regards,
> >
> > Morbious
> >
>
Re: Compile oozie 4.0.0
Posted by Robert Kanter <rk...@cloudera.com>.
Hi,
What's the command you're using to compile?
- Robert
On Fri, Apr 17, 2015 at 3:47 AM, Morbious <kn...@gmail.com>
wrote:
> Hi,
>
> I've tried compile oozie with patch recently.
> Each time I did this I got an error :
>
> [ERROR] Failed to execute goal on project oozie-webapp: Could not resolve
> dependencies for project org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2:
> Could not find artifact org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in
> cdh.repo (https://repository.cloudera.com/content/groups/cloudera-repos)
> ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project oozie-webapp: Could not resolve dependencies for project
> org.apache.oozie:oozie-webapp:war:4.0.0-cdh5.3.2: Could not find artifact
> org.apache.oozie:oozie-docs:war:4.0.0-cdh5.3.2 in cdh.repo (
> https://repository.cloudera.com/content/groups/cloudera-repos)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>
> It seems that oozie-doc*.war doesn't exist.
> I need to compile this due patch which allows me to use UTF8 properly.
> Can anyone point me what I'm doing wrong ?
>
> Best regards,
>
> Morbious
>