[jira] [Commented] (ATLAS-655) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/ATLAS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362007#comment-15362007 ] Shwetha G S commented on ATLAS-655: --- Deleted https://dist.apache.org/repos/dist/release/incubator/atlas/0.5.0-incubating/ > Please delete old releases from mirroring system > > > Key: ATLAS-655 > URL: https://issues.apache.org/jira/browse/ATLAS-655 > Project: Atlas > Issue Type: Bug > Environment: > https://dist.apache.org/repos/dist/release/incubator/atlas/ >Reporter: Sebb >Assignee: Shwetha G S > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-956) StormAtlasHook is not working for topologies that do not refer to Hadoop related bolts
[
https://issues.apache.org/jira/browse/ATLAS-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reassigned ATLAS-956:
--
Assignee: Madhan Neethiraj
> StormAtlasHook is not working for topologies that do not refer to Hadoop
> related bolts
> --
>
> Key: ATLAS-956
> URL: https://issues.apache.org/jira/browse/ATLAS-956
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Madhan Neethiraj
>Priority: Critical
>
> Submitting simple topologies that do not have any Hadoop specific bolts or
> functionality is causing exceptions in StormAtlas Hook, like below:
> {code}
> 684 [main] INFO o.a.s.StormSubmitter - Generated ZooKeeper secret payload
> for MD5-digest: -8572156748850444065:-7480695850066516712
> 776 [main] INFO o.a.s.s.a.AuthUtils - Got AutoCreds []
> 780 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
> for backward compatibility. Please update your storm.yaml so it only has
> config nimbus.seeds
> 843 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
> for backward compatibility. Please update your storm.yaml so it only has
> config nimbus.seeds
> 857 [main] INFO o.a.s.StormSubmitter - Uploading topology jar
> /tmp/1cb29a4a36b011e6a028080027f12dac.jar to assigned location:
> /hadoop/storm/nimbus/inbox/stormjar-f7558579-b946-4add-91c0-ad5a5177864c.jar
> 873 [main] INFO o.a.s.StormSubmitter - Successfully uploaded topology jar
> to assigned location:
> /hadoop/storm/nimbus/inbox/stormjar-f7558579-b946-4add-91c0-ad5a5177864c.jar
> 874 [main] INFO o.a.s.StormSubmitter - Submitting topology
> WordCountid007f0100_date271916 in distributed mode with conf
> {"storm.zookeeper.topology.auth.scheme":"digest","storm.zookeeper.topology.auth.payload":"-8572156748850444065:-7480695850066516712","topology.workers":3,"topology.debug":true}
> 874 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
> for backward compatibility. Please update your storm.yaml so it only has
> config nimbus.seeds
> 1011 [main] INFO o.a.s.StormSubmitter - Finished submitting topology:
> WordCountid007f0100_date271916
> 1011 [main] INFO o.a.s.StormSubmitter - Initializing the registered
> ISubmitterHook [org.apache.atlas.storm.hook.StormAtlasHook]
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/conf/Configuration
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.storm.StormSubmitter.invokeSubmitterHook(StormSubmitter.java:282)
> at
> org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:258)
> at
> org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:311)
> at
> org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:157)
> at storm.starter.WordCountTopology.main(WordCountTopology.java:77)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.conf.Configuration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 7 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-987) Atlas hooks should avoid adding dependent libraries to component CLASSPATH
[ https://issues.apache.org/jira/browse/ATLAS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-987: --- Attachment: (was: ATLAS-987.3.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.2.patch, ATLAS-987.3.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)
Re: Review Request 49585: ATLAS-987: load dependent libraries of Atlas hooks in a separate class loader to avoid adding them to component CLASSPATH
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49585/ --- (Updated July 5, 2016, 1:24 a.m.) Review request for atlas. Changes --- Addressed review comments Bugs: ATLAS-987 https://issues.apache.org/jira/browse/ATLAS-987 Repository: atlas Description --- Dependent libraries of Atlas hooks are loaded in a separate class loader, there by making these libraries not visibile to components. Here is the summary of the changes: - current contents of atlas/hook/ directiries, including the hook class implementation, are moved under atlas/hook//atlas--plugin-impl directory - a new component specific shim library, that includes the hook class registered with the component, is placed in directory atlas/hook/ - the hook class in the shim library loads all files in atlas--plugin-impl directory in a classloader and forwards all the calls on the shim class to the real implementation class This implementation is same as the one used in Apache Ranger - more details in RANGER-586. Diffs (updated) - addons/falcon-bridge-shim/pom.xml PRE-CREATION addons/falcon-bridge-shim/src/main/java/org/apache/atlas/falcon/hook/AtlasService.java PRE-CREATION addons/falcon-bridge/pom.xml d79dda9 addons/hive-bridge-shim/pom.xml PRE-CREATION addons/hive-bridge-shim/src/main/java/org/apache/atlas/hive/hook/HiveHook.java PRE-CREATION addons/hive-bridge/pom.xml ddefdc2 addons/sqoop-bridge-shim/pom.xml PRE-CREATION addons/sqoop-bridge-shim/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java PRE-CREATION addons/sqoop-bridge/pom.xml c792945 addons/storm-bridge-shim/pom.xml PRE-CREATION addons/storm-bridge-shim/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java PRE-CREATION addons/storm-bridge/pom.xml 9e8bf2f plugin-classloader/pom.xml PRE-CREATION plugin-classloader/src/main/java/org/apache/atlas/plugin/classloader/AtlasPluginClassLoader.java PRE-CREATION plugin-classloader/src/main/java/org/apache/atlas/plugin/classloader/AtlasPluginClassLoaderUtil.java PRE-CREATION pom.xml f119525 Diff: https://reviews.apache.org/r/49585/diff/ Testing --- Verified that existing tests pass Verified Hive hook successfully sends notification to Kafka, which in turn was processed correctly by Atlas server Thanks, Madhan Neethiraj
[jira] [Updated] (ATLAS-987) Atlas hooks should avoid adding dependent libraries to component CLASSPATH
[ https://issues.apache.org/jira/browse/ATLAS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-987: --- Attachment: ATLAS-987.3.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.2.patch, ATLAS-987.3.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)
[jira] [Comment Edited] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361283#comment-15361283 ] Vimal Sharma edited comment on ATLAS-847 at 7/4/16 2:59 PM: [~Kalyanikashikar] Changes look good to me.However, "Previous" button does not fetch results more than one page old. Basically, after clicking "Next" a couple of times(say 4), I cannot navigate to page 2(or page 1) using "Previous" button. Can you please look into this. was (Author: svimal2106): [~Kalyanikashikar] After applying the patch and creating more than 100 audit events for a hive table, I find that only the most recent 100 audit events are fetched and paginated in sets of 25. Further, I still see that there are numerical labels for pages rather than "Previous" and "Next" buttons as suggested by Shwetha. Can you share the procedure you used to test this patch. I have attached the screenshot of audit page. > UI: Audit versioning does not paginate details from Atlas server > > > Key: ATLAS-847 > URL: https://issues.apache.org/jira/browse/ATLAS-847 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Kalyani Kashikar > Attachments: ATLAS-847.patch, audit_pagination.png > > > In ATLAS-664, the capability to view Audit events was added to the Atlas > admin UI. However, currently, the API call made only fetches the first 100 > events (which is the default if no count is sent). In order to fetch the next > set of events, further API calls need to be made to the Audit API, by > providing additional parameters in the API. This JIRA is to track the > required changes in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361283#comment-15361283 ] Vimal Sharma commented on ATLAS-847: [~Kalyanikashikar] After applying the patch and creating more than 100 audit events for a hive table, I find that only the most recent 100 audit events are fetched and paginated in sets of 25. Further, I still see that there are numerical labels for pages rather than "Previous" and "Next" buttons as suggested by Shwetha. Can you share the procedure you used to test this patch. I have attached the screenshot of audit page. > UI: Audit versioning does not paginate details from Atlas server > > > Key: ATLAS-847 > URL: https://issues.apache.org/jira/browse/ATLAS-847 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Kalyani Kashikar > Attachments: ATLAS-847.patch, audit_pagination.png > > > In ATLAS-664, the capability to view Audit events was added to the Atlas > admin UI. However, currently, the API call made only fetches the first 100 > events (which is the default if no count is sent). In order to fetch the next > set of events, further API calls need to be made to the Audit API, by > providing additional parameters in the API. This JIRA is to track the > required changes in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-847: --- Attachment: audit_pagination.png > UI: Audit versioning does not paginate details from Atlas server > > > Key: ATLAS-847 > URL: https://issues.apache.org/jira/browse/ATLAS-847 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Kalyani Kashikar > Attachments: ATLAS-847.patch, audit_pagination.png > > > In ATLAS-664, the capability to view Audit events was added to the Atlas > admin UI. However, currently, the API call made only fetches the first 100 > events (which is the default if no count is sent). In order to fetch the next > set of events, further API calls need to be made to the Audit API, by > providing additional parameters in the API. This JIRA is to track the > required changes in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 49499: ATLAS-970 : Remove glyphicon from login.jsp
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49499/ --- (Updated July 4, 2016, 10:20 a.m.) Review request for atlas, Gautam Borad, Madhan Neethiraj, and Hemanth Yamijala. Changes --- glyphicon reference removed from scss files Bugs: ATLAS-970 https://issues.apache.org/jira/browse/ATLAS-970 Repository: atlas Description --- Replace glyphicon with font awesome Diffs (updated) - dashboardv2/public/css/scss/form.scss 6802c12 dashboardv2/public/css/scss/loader.scss 080283a webapp/src/main/webapp/login.jsp cf5990a Diff: https://reviews.apache.org/r/49499/diff/ Testing --- Thanks, keval bhatt
[jira] [Commented] (ATLAS-970) Remove glyphicon from login.jsp
[ https://issues.apache.org/jira/browse/ATLAS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361135#comment-15361135 ] Keval Bhatt commented on ATLAS-970: --- [~shwethags] Review comments are addressed and patch is updated. > Remove glyphicon from login.jsp > --- > > Key: ATLAS-970 > URL: https://issues.apache.org/jira/browse/ATLAS-970 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Blocker > Attachments: ATLAS-970.1.patch, ATLAS-970.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-970) Remove glyphicon from login.jsp
[ https://issues.apache.org/jira/browse/ATLAS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-970: -- Attachment: ATLAS-970.1.patch > Remove glyphicon from login.jsp > --- > > Key: ATLAS-970 > URL: https://issues.apache.org/jira/browse/ATLAS-970 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Blocker > Attachments: ATLAS-970.1.patch, ATLAS-970.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-987) Atlas hooks should avoid adding dependent libraries to component CLASSPATH
[ https://issues.apache.org/jira/browse/ATLAS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-987: --- Attachment: ATLAS-987.2.patch Updated patch for the following: - added hadoop-common, gson, log4j libraries to all hooks as they are used from base class AtlasHook - added missing StormAtlasHook constructor > 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.2.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)
Re: Review Request 49585: ATLAS-987: load dependent libraries of Atlas hooks in a separate class loader to avoid adding them to component CLASSPATH
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49585/ --- (Updated July 4, 2016, 8:33 a.m.) Review request for atlas. Changes --- - added hadoop-common, json, log4j libraries in all hooks, as they are used in AtlasHook base class - added missing StromAtlasHook constructor Bugs: ATLAS-987 https://issues.apache.org/jira/browse/ATLAS-987 Repository: atlas Description --- Dependent libraries of Atlas hooks are loaded in a separate class loader, there by making these libraries not visibile to components. Here is the summary of the changes: - current contents of atlas/hook/ directiries, including the hook class implementation, are moved under atlas/hook//atlas--plugin-impl directory - a new component specific shim library, that includes the hook class registered with the component, is placed in directory atlas/hook/ - the hook class in the shim library loads all files in atlas--plugin-impl directory in a classloader and forwards all the calls on the shim class to the real implementation class This implementation is same as the one used in Apache Ranger - more details in RANGER-586. Diffs (updated) - addons/falcon-bridge-shim/pom.xml PRE-CREATION addons/falcon-bridge-shim/src/main/java/org/apache/atlas/falcon/hook/AtlasService.java PRE-CREATION addons/falcon-bridge/pom.xml d79dda9 addons/hive-bridge-shim/pom.xml PRE-CREATION addons/hive-bridge-shim/src/main/java/org/apache/atlas/hive/hook/HiveHook.java PRE-CREATION addons/hive-bridge/pom.xml ddefdc2 addons/sqoop-bridge-shim/pom.xml PRE-CREATION addons/sqoop-bridge-shim/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java PRE-CREATION addons/sqoop-bridge/pom.xml c792945 addons/storm-bridge-shim/pom.xml PRE-CREATION addons/storm-bridge-shim/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java PRE-CREATION addons/storm-bridge/pom.xml 9e8bf2f plugin-classloader/pom.xml PRE-CREATION plugin-classloader/src/main/java/org/apache/atlas/plugin/classloader/AtlasPluginClassLoader.java PRE-CREATION plugin-classloader/src/main/java/org/apache/atlas/plugin/classloader/AtlasPluginClassLoaderUtil.java PRE-CREATION pom.xml f119525 Diff: https://reviews.apache.org/r/49585/diff/ Testing --- Verified that existing tests pass Verified Hive hook successfully sends notification to Kafka, which in turn was processed correctly by Atlas server Thanks, Madhan Neethiraj
[jira] [Commented] (ATLAS-979) Search: search on boolean values is not working
[
https://issues.apache.org/jira/browse/ATLAS-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360983#comment-15360983
]
Hemanth Yamijala commented on ATLAS-979:
Yes.
> Search: search on boolean values is not working
> ---
>
> Key: ATLAS-979
> URL: https://issues.apache.org/jira/browse/ATLAS-979
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>
> Create an type with a boolean attribute and an entity of the type. Search
> using DSL with the query "typeName where boolean_attribute = true". This is
> failing with an exception as below:
> {code}
> org.apache.atlas.discovery.DiscoveryException: Invalid expression :
> hbase_table where isEnabled = true
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
> at
> org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> ...
> Caused by: org.apache.atlas.AtlasException: Cannot combine types: boolean and
> boolean
> at org.apache.atlas.query.TypeUtils$.combinedType(TypeUtils.scala:56)
> at
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType$lzycompute(Expressions.scala:639)
> at
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:628)
> at
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:623)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:672)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:667)
> at
> org.apache.atlas.query.QueryProcessor$.validate(QueryProcessor.scala:49)
> at
> org.apache.atlas.query.QueryProcessor.validate(QueryProcessor.scala)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:144)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:134)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-968) Set group information from UGI for Ldap authentication.
[ https://issues.apache.org/jira/browse/ATLAS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-968: -- Attachment: ATLAS-968-2.patch > Set group information from UGI for Ldap authentication. > --- > > Key: ATLAS-968 > URL: https://issues.apache.org/jira/browse/ATLAS-968 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-968-1.patch, ATLAS-968-2.patch, ATLAS-968.patch > > > For Ldap authentication the user's group information is not retrieved. so > setting > the group information from UGI for Ldap authentication type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 49441: ATLAS-968 - Set group information from UGI for Ldap authentication.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/49441/
---
(Updated July 4, 2016, 7:15 a.m.)
Review request for atlas, Madhan Neethiraj, Mehul Parikh, Shwetha GS, and
Hemanth Yamijala.
Changes
---
The patch includes changes done to handle review comments.
Bugs: ATLAS-968
https://issues.apache.org/jira/browse/ATLAS-968
Repository: atlas
Description
---
The patch includes changes for setting groups information from UGI in ldap type
in which group information is not retrived from ldap directory.
Diffs (updated)
-
distro/src/conf/atlas-application.properties cc0e4c1
webapp/src/main/java/org/apache/atlas/web/security/AtlasADAuthenticationProvider.java
cf83109
webapp/src/main/java/org/apache/atlas/web/security/AtlasAbstractAuthenticationProvider.java
5f1a245
webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java
6d56453
Diff: https://reviews.apache.org/r/49441/diff/
Testing
---
ran mvn clean install
created user in ldap ambari-qa which has groups associated in UGI and logged
in with it. groups retrived from UGI were proper.
http://172.22.89.116:21000/api/atlas/admin/session
{"userName":"ambari-qa","groups":["hadoop","users"]}
logged in with user ldapuser11 and no groups were set from UGI.
http://172.22.89.116:21000/api/atlas/admin/session
{"userName":"ldapuser11","groups":[]}
Thanks,
Nixon Rodrigues
[jira] [Assigned] (ATLAS-655) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/ATLAS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-655: - Assignee: Shwetha G S > Please delete old releases from mirroring system > > > Key: ATLAS-655 > URL: https://issues.apache.org/jira/browse/ATLAS-655 > Project: Atlas > Issue Type: Bug > Environment: > https://dist.apache.org/repos/dist/release/incubator/atlas/ >Reporter: Sebb >Assignee: Shwetha G S > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-456) Loader of all Ui functionality until the api response, On Esc stop loader
[ https://issues.apache.org/jira/browse/ATLAS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-456. --- Resolution: Not A Problem > Loader of all Ui functionality until the api response, On Esc stop loader > - > > Key: ATLAS-456 > URL: https://issues.apache.org/jira/browse/ATLAS-456 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg >Priority: Critical > > Loader for all the api call's from UI, > The loader to be shown until the backend Api is response is success or failure > If the Api is taking to long time to respond, On User Esc button press Loader > to be stopped. > This need's to implemented through out application, in frame work level > We need to show loader until the Api call is responded, > By block the screen for any other click's. > So that user will no be allowed to click any other button's, Only "Esc" to > stop the loade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-639) Exception for lineage request
[
https://issues.apache.org/jira/browse/ATLAS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-639:
--
Priority: Critical (was: Major)
> Exception for lineage request
> -
>
> Key: ATLAS-639
> URL: https://issues.apache.org/jira/browse/ATLAS-639
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Priority: Critical
> Fix For: trunk
>
>
> Exception in log for lineage request
> Steps to repro:
> create table j13 (col4 String);
> create table j14 (col5 String);
> insert into table j13 select * from j14;
> insert into table j14 select * from j13;
> Query for lineage of any of the above two entities..(also keep querying for
> any other request along with this). Lineage request is timed-out and below
> error messages are observed in the application log. The below messages are
> seen continously.(Clean the data dir and manual restart will fix this).
> Environment: Atlas running in embedded mode on local setup.
> {noformat}
> 2016-04-06 11:41:45,112 DEBUG - [qtp1936542270-298 -
> fecc3aa7-f4cf-4f6d-89a2-d973c05bc06f:] ~ graph commit
> (GraphTransactionInterceptor:44)
> 2016-04-06 11:41:45,112 DEBUG - [qtp1936542270-298 -
> fecc3aa7-f4cf-4f6d-89a2-d973c05bc06f:] ~ graph commit
> (GraphTransactionInterceptor:44)
> 2016-04-06 11:41:48,935 INFO - [main-SendThread(localhost:9026):] ~ Client
> session timed out, have not heard from server in 1669ms for sessionid
> 0x153ea2cd8da002b, closing socket connection and attempting reconnect
> (ClientCnxn:1096)
> 2016-04-06 11:41:48,935 INFO - [SessionTracker:] ~ Expiring session
> 0x153ea2cd8da002a, timeout of 1000ms exceeded (ZooKeeperServer:347)
> 2016-04-06 11:41:48,935 INFO - [main-SendThread(localhost:9026):] ~ Client
> session timed out, have not heard from server in 1917ms for sessionid
> 0x153ea2cd8da002a, closing socket connection and attempting reconnect
> (ClientCnxn:1096)
> 2016-04-06 11:41:48,935 INFO - [SessionTracker:] ~ Expiring session
> 0x153ea2cd8da002b, timeout of 1000ms exceeded (ZooKeeperServer:347)
> 2016-04-06 11:41:48,935 WARN -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream
> exception (NIOServerCnxn:357)
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x153ea2cd8da002b, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> 2016-04-06 11:41:48,935 INFO - [ProcessThread(sid:0 cport:-1)::] ~ Processed
> session termination for sessionid: 0x153ea2cd8da002a
> (PrepRequestProcessor:494)
> 2016-04-06 11:41:48,936 INFO - [ProcessThread(sid:0 cport:-1)::] ~ Processed
> session termination for sessionid: 0x153ea2cd8da002b
> (PrepRequestProcessor:494)
> 2016-04-06 11:41:48,936 INFO -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ Closed socket connection
> for client /127.0.0.1:51657 which had sessionid 0x153ea2cd8da002b
> (NIOServerCnxn:1007)
> 2016-04-06 11:41:48,936 WARN -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream
> exception (NIOServerCnxn:357)
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x153ea2cd8da002a, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> 2016-04-06 11:41:48,936 INFO -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ Closed socket connection
> for client /127.0.0.1:51652 which had sessionid 0x153ea2cd8da002a
> (NIOServerCnxn:1007)
> 2016-04-06 11:41:49,040 INFO - [main-EventThread:] ~ zookeeper state changed
> (Disconnected) (ZkClient:711)
> 2016-04-06 11:41:49,040 INFO - [main-EventThread:] ~ zookeeper state changed
> (Disconnected) (ZkClient:711)
> 2016-04-06 11:41:58,894 INFO - [main-SendThread(localhost:9026):] ~ Opening
> socket connection to server localhost/127.0.0.1:9026. Will not attempt to
> authenticate using SASL (unknown error) (ClientCnxn:975)
> 2016-04-06 11:41:58,894 INFO -
> [Curator-Framework-0-SendThread(localhost:9026):] ~ Client session timed out,
> have not heard from server in 11587ms for sessionid 0x153ea2cd8da0025,
> closing socket connection and attempting reconnect (ClientCnxn:1096)
> 2016-04-06 11:41:58,894 INFO - [main-SendThread(localhost:9026):] ~ Socket
> connection established to localhost/127.0.0.1:9026, initiating session
> (ClientCnxn:852)
> 2016-04-06 11:41:58,894 INFO - [main-SendThread(localhost:9026):] ~ Opening
> socket connection
[jira] [Updated] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly
[
https://issues.apache.org/jira/browse/ATLAS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-170:
--
Assignee: (was: Rohit)
> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
> Environment: HDP2.3.1
>Reporter: Herman Yu
>Priority: Blocker
> Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr).
> then associate this trait to an entity with "myvalue" as the value of the
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1
> record matched, but doesn't show the entity in the list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-987) Atlas hooks should avoid adding dependent libraries to component CLASSPATH
[ https://issues.apache.org/jira/browse/ATLAS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-987: --- Attachment: ATLAS-987.patch Review board URL: https://reviews.apache.org/r/49585/ > 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.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)
Review Request 49585: ATLAS-987: load dependent libraries of Atlas hooks in a separate class loader to avoid adding them to component CLASSPATH
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49585/ --- Review request for atlas. Bugs: ATLAS-987 https://issues.apache.org/jira/browse/ATLAS-987 Repository: atlas Description --- Dependent libraries of Atlas hooks are loaded in a separate class loader, there by making these libraries not visibile to components. Here is the summary of the changes: - current contents of atlas/hook/ directiries, including the hook class implementation, are moved under atlas/hook//atlas--plugin-impl directory - a new component specific shim library, that includes the hook class registered with the component, is placed in directory atlas/hook/ - the hook class in the shim library loads all files in atlas--plugin-impl directory in a classloader and forwards all the calls on the shim class to the real implementation class This implementation is same as the one used in Apache Ranger - more details in RANGER-586. Diffs - addons/falcon-bridge-shim/pom.xml PRE-CREATION addons/falcon-bridge-shim/src/main/java/org/apache/atlas/falcon/hook/AtlasService.java PRE-CREATION addons/falcon-bridge/pom.xml d79dda9 addons/hive-bridge-shim/pom.xml PRE-CREATION addons/hive-bridge-shim/src/main/java/org/apache/atlas/hive/hook/HiveHook.java PRE-CREATION addons/hive-bridge/pom.xml ddefdc2 addons/sqoop-bridge-shim/pom.xml PRE-CREATION addons/sqoop-bridge-shim/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java PRE-CREATION addons/sqoop-bridge/pom.xml c792945 addons/storm-bridge-shim/pom.xml PRE-CREATION addons/storm-bridge-shim/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java PRE-CREATION addons/storm-bridge/pom.xml 9e8bf2f plugin-classloader/pom.xml PRE-CREATION plugin-classloader/src/main/java/org/apache/atlas/plugin/classloader/AtlasPluginClassLoader.java PRE-CREATION plugin-classloader/src/main/java/org/apache/atlas/plugin/classloader/AtlasPluginClassLoaderUtil.java PRE-CREATION pom.xml f119525 Diff: https://reviews.apache.org/r/49585/diff/ Testing --- Verified that existing tests pass Verified Hive hook successfully sends notification to Kafka, which in turn was processed correctly by Atlas server Thanks, Madhan Neethiraj
