[
https://issues.apache.org/jira/browse/AMBARI-21610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21610:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5
> EU: Modify configs to enable custom extensions functionality
> ------------------------------------------------------------
>
> Key: AMBARI-21610
> URL: https://issues.apache.org/jira/browse/AMBARI-21610
> Project: Ambari
> Issue Type: Task
> Affects Versions: 2.5.2
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21610.patch
>
>
> We need EU to modify the configs that we have changed to add the path to the
> class path.
> *Pre Upgrade* (say for hadoop in a BI-4.2.5 cluster)
> * There is an HDFS folder /iop/ext/4.2.5/hadoop where users have put their
> custom extension jars
> * On start of hadoop services we copy jars from HDFS to on disk location
> {{/usr/iop/current/ext/hadoop}}
> * All class path variables include the on disk path
> *Post Upgrade* (for HDP-2.6.2 cluster)
> * HDP clusters now have an HDFS folder /hdp/ext/2.6/hadoop where the users
> must copy the extension jars again (some jars may be new as its an upgrade)
> * On start of hadoop services we copy jars from the above location to disk at
> /usr/hdp/current/ext/hadoop
> * Class paths now should now have the above path
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
