[
https://issues.apache.org/jira/browse/ATLAS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-987:
------------------------------
Attachment: ATLAS-987-v6.patch
Fixed the following:
1. falcon-bridge has org.apache.atlas.falcon.service.AtlasService, but
falcon-shim had org.apache.atlas.falcon.hook.AtlasService. So, changed the
package names to match
2. There were check style failures in all the new modules. Please run 'mvn
clean install’ before submitting the patch
> Atlas hooks should avoid adding dependent libraries to component CLASSPATH
> --------------------------------------------------------------------------
>
> Key: ATLAS-987
> URL: https://issues.apache.org/jira/browse/ATLAS-987
> Project: Atlas
> Issue Type: Bug
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Attachments: ATLAS-987-v6.patch, ATLAS-987.2.patch,
> ATLAS-987.3.patch, ATLAS-987.4.patch, ATLAS-987.5.patch, ATLAS-987.patch
>
>
> Libraries used by Atlas hooks (like json, commons-configuration,
> commons-logging, etc) are added to component’s CLASSPATH. This can
> potentially impact the functioning of a component if the component requires a
> version of a library which is incompatible with the version used by Atlas
> hook.
> One approach to minimize such impact is to have Atlas hooks load the
> dependent libraries in its own class loader, instead of copying them to the
> component’s CLASSPATH. This will restrict the dependent libraries to be
> visible only to Atlas hooks, there by isolating the component from these
> libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
