[
https://issues.apache.org/jira/browse/FALCON-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809891#comment-13809891
]
Ashish Singh commented on FALCON-162:
-------------------------------------
[~arpitgupta] the patch has issues. It fails with the error
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
(default-cli) on project falcon-main: Error reading assemblies: Error reading
descriptor at: src/main/assemblies/client-package.xml: Unrecognised tag:
'directory' (position: START_TAG seen ...<file>\n <directory>...
@63:24) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
(default-cli) on project falcon-main: Error reading assemblies: Error reading
descriptor at: src/main/assemblies/client-package.xml: Unrecognised tag:
'directory' (position: START_TAG seen ...<file>\n <directory>...
@63:24)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
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)
{noformat}
Looks like <file> tag doesn't support <directory> tag, <directory> tag is
supported only for <fileSet>.
> Update falcon scripts to let the user set the log and pid locations.
> --------------------------------------------------------------------
>
> Key: FALCON-162
> URL: https://issues.apache.org/jira/browse/FALCON-162
> Project: Falcon
> Issue Type: Bug
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: FALCON-162.patch, FALCON-162.patch
>
>
> Current falcon scripts hard code the location of the log and the pid dirs.
> Instead if we added the ability to source a falcon-env.sh which the user
> could provide then the user can overwrite these locations to some thing else.
> This would also allow the user a way to set JAVA_HOME and other env vars in a
> file rather than doing it in a shell. This is something similar to how hadoop
> works.
> Along with this change i also plan on changing the classpath to list dir/*
> instead of every jar file. Again this is similar to what hadoop 2 does.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
