You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2013/11/06 20:32:17 UTC

[jira] [Commented] (FALCON-172) Improve the robustness of service-start.sh

    [ https://issues.apache.org/jira/browse/FALCON-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815188#comment-13815188 ] 

Venkatesh Seetharam commented on FALCON-172:
--------------------------------------------

FALCON-162 addresses this in a generic way. Can you please look into it to see if that satisfies these requirements. If so, appreciate if you could mark this as duplicate. FYI, FALCON-165 is simplifying the packaging as well.

> Improve the robustness of service-start.sh
> ------------------------------------------
>
>                 Key: FALCON-172
>                 URL: https://issues.apache.org/jira/browse/FALCON-172
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Haohui Mai
>            Priority: Minor
>         Attachments: FALCON-172.000.patch
>
>
> This jira intends to fix the following problems of the service-start.sh:
> * It should pick up the configuration in conf/falcon-env.sh automatically. This is the behavior in hadoop-core.
> * If HADOOP_PREFIX is set, it should add the dependency based on HADOOP_PREFIX rather than looking for hadoop in the system.
> * It should respect JAVA_HOME when calling jar.



--
This message was sent by Atlassian JIRA
(v6.1#6144)