Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.incubator.apache.org
Date: Fri, 8 Jul 2016 06:01:11 +0000 (UTC)
From: "Shwetha G S (JIRA)" <jira@apache.org>
To: dev@atlas.incubator.apache.org
Message-ID: <JIRA.12986501.1467597093000.55121.1467957671000@Atlassian.JIRA>
In-Reply-To: <JIRA.12986501.1467597093000@Atlassian.JIRA>
References: <JIRA.12986501.1467597093000@Atlassian.JIRA> <JIRA.12986501.1467597093786@arcas>
Subject: [jira] [Updated] (ATLAS-987) Atlas hooks should avoid adding
 dependent libraries to component CLASSPATH
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 08 Jul 2016 06:01:16 -0000


     [ https://issues.apache.org/jira/browse/ATLAS-987?page=3Dcom.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 falc=
on-shim had org.apache.atlas.falcon.hook.AtlasService. So, changed the pack=
age names to match
2. There were check style failures in all the new modules. Please run 'mvn =
clean install=E2=80=99 before submitting the patch


> Atlas hooks should avoid adding dependent libraries to component CLASSPAT=
H
> -------------------------------------------------------------------------=
-
>
>                 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.p=
atch, 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=E2=80=99s CLASSPATH. This can potentia=
lly impact the functioning of a component if the component requires a versi=
on 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 depe=
ndent libraries in its own class loader, instead of copying them to the com=
ponent=E2=80=99s CLASSPATH. This will restrict the dependent libraries to b=
e visible only to Atlas hooks, there by isolating the component from these =
libraries.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)