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

Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2012/03/19 22:47:39 UTC

[jira] [Updated] (BIGTOP-276) Standardize how clients create classpaths and java.library.paths

     [ https://issues.apache.org/jira/browse/BIGTOP-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-276:
------------------------------------

    Fix Version/s:     (was: 0.3.0)
                   0.4.0
    
> Standardize how clients create classpaths and java.library.paths
> ----------------------------------------------------------------
>
>                 Key: BIGTOP-276
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-276
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: General
>    Affects Versions: 0.2.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>
> We need to standardize how clients (hadoop, pig, hive, sqoop, flume etc) create their classpath and java.library.path. It remains to be seen if we can also address the issue of log4j loglevels uniformly across the stack. The initial idea is to refactor the relevant bits of code from the hadoop launcher script into a universal script that'll be part of bigtop-utils.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira