Re: Review Request 59799: ATLAS-1766 : Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues]

> On June 6, 2017, 8:50 p.m., Suma Shivaprasad wrote:
> > distro/src/conf/atlas-application.properties
> > Lines 81 (patched)
> > <https://reviews.apache.org/r/59799/diff/1/?file=1741121#file1741121line81>
> >
> > why is auto commit set to true. This will cause issues when there is a 
> > transient failure on Atlas server and no retries will be attempted

Have added code to commit the record offset.


- Nixon


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59799/#review177095
-------


On June 21, 2017, 1:11 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59799/
> ---
> 
> (Updated June 21, 2017, 1:11 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
> Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch include changes that implements kafka new-consumer api for 
> kafkaConsumer for Atlas Notification System.
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties 5e59528 
>   notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
> PRE-CREATION 
>   notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaMessage.java 
> PRE-CREATION 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 
> 16c0eb2 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
> 8bd31fd 
>   
> notification/src/main/java/org/apache/atlas/notification/AbstractMessageDeserializer.java
>  9585827 
>   
> notification/src/main/java/org/apache/atlas/notification/AbstractNotificationConsumer.java
>  d4d78de 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
>  a99cb10 
>   notification/src/test/java/org/apache/atlas/kafka/KafkaConsumerTest.java 
> ad7d93e 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationMockTest.java
>  2126be6 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
> a810029 
>   
> notification/src/test/java/org/apache/atlas/notification/AbstractNotificationConsumerTest.java
>  13f2f0b 
>   typesystem/src/test/resources/atlas-application.properties c4ce5ea 
>   
> webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  2f8245d 
>   
> webapp/src/test/java/org/apache/atlas/notification/EntityNotificationIT.java 
> ac3b538 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerKafkaTest.java
>  18fd2ee 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
>  bdb60a2 
>   webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
> b59d3ee 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
>  310b2e3 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java
>  98a7abc 
> 
> 
> Diff: https://reviews.apache.org/r/59799/diff/4/
> 
> 
> Testing
> ---
> 
> Tested Kafka consumer on local embeded kafka /zookeeper env.
> Tested Atlas Hive hook notifications.
> Excecute Quick Start script.
> 
> Due to change in kafkaconsumer api the current notification related UT/IT's 
> need to changed, i have not included this change in this patch but will 
> included it shortly.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

Re: Review Request 59799: ATLAS-1766 : Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59799/
---

(Updated June 21, 2017, 1:11 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
Sarath Subramanian.


Changes
---

This is patch handles review comments and fix for unit test and integration 
cases.

Tested the consumer from ATLAS_HOOK topics from hive db after creating hive 
tables.


Repository: atlas


Description
---

This patch include changes that implements kafka new-consumer api for 
kafkaConsumer for Atlas Notification System.


Diffs (updated)
-

  distro/src/conf/atlas-application.properties 5e59528 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaMessage.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 16c0eb2 
  notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
8bd31fd 
  
notification/src/main/java/org/apache/atlas/notification/AbstractMessageDeserializer.java
 9585827 
  
notification/src/main/java/org/apache/atlas/notification/AbstractNotificationConsumer.java
 d4d78de 
  
notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
 a99cb10 
  notification/src/test/java/org/apache/atlas/kafka/KafkaConsumerTest.java 
ad7d93e 
  
notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationMockTest.java
 2126be6 
  notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
a810029 
  
notification/src/test/java/org/apache/atlas/notification/AbstractNotificationConsumerTest.java
 13f2f0b 
  typesystem/src/test/resources/atlas-application.properties c4ce5ea 
  
webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
 2f8245d 
  webapp/src/test/java/org/apache/atlas/notification/EntityNotificationIT.java 
ac3b538 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerKafkaTest.java
 18fd2ee 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
 bdb60a2 
  webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
b59d3ee 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
 310b2e3 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java
 98a7abc 


Diff: https://reviews.apache.org/r/59799/diff/4/

Changes: https://reviews.apache.org/r/59799/diff/3-4/


Testing
---

Tested Kafka consumer on local embeded kafka /zookeeper env.
Tested Atlas Hive hook notifications.
Excecute Quick Start script.

Due to change in kafkaconsumer api the current notification related UT/IT's 
need to changed, i have not included this change in this patch but will 
included it shortly.


Thanks,

Nixon Rodrigues

[jira] [Created] (ATLAS-1890) IntegrationTest cases failing in BaseResourceIT.waitForNotification method

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1890:
--

 Summary: IntegrationTest cases failing in 
BaseResourceIT.waitForNotification method
 Key: ATLAS-1890
 URL: https://issues.apache.org/jira/browse/ATLAS-1890
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


Problem:-

This test cases are failing in BaseResourceIT.waitForNotification method.
In waitForNotification method it waits for certain Time for Kafka notification 
of the entity created/update/deleted etc to read from KafkaTopic.

Currently for Integration tests in Atlas, a metadata server is running on port 
31000 along berkely-db store and kafka/zookeeper for notifitication.
This Atlas services is used by All Integration tests that are running from 
maven test suite.
Since testcases run independent of eachother and if they access shared like 
kafka notification via consumer, the consumer will results different type of 
results and also with some IO and timing issues.

{code}
testEntityDeduping(org.apache.atlas.web.integration.EntityJerseyResourceIT)  
Time elapsed: 61.463 sec  <<< FAILURE!
java.lang.Exception: Waiting timed out after 6000 msec
at 
org.apache.atlas.web.integration.EntityJerseyResourceIT.testEntityDeduping(EntityJerseyResourceIT.java:221)


EntityV2JerseyResourceIT.testEntityDeduping:170->BaseResourceIT.waitForNotification:633->BaseResourceIT.waitFor:625
 »
EntityNotificationIT.testDeleteEntity:108->BaseResourceIT.waitForNotification:633->BaseResourceIT.waitFor:625
 »
{code}


The purpose of waitForNotification method is to valid if notifications reach 
the Kafka topic.
I propose to remove this dependeny to check the entity created notification on 
kafka topic from the above IntegrationTest.
The validation of created/update/deleted notification of entity into kafka 
topic can be done seperate UT/IT.

Let me know your thoughts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-1878) NPE when a request without any query path lands on atlas

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053223#comment-16053223
 ] 

Nixon Rodrigues commented on ATLAS-1878:


Thanks [~sarath.ku...@gmail.com] and [~apoorvnaik] for the  review.

Committed patch on following brach

* master -> 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/906f3651
* 0.8-incubating -> 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/fca6855e

> NPE when a request without any query path lands on atlas
> 
>
> Key: ATLAS-1878
> URL: https://issues.apache.org/jira/browse/ATLAS-1878
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1878.patch
>
>
> {noformat}
> 2017-06-16 07:02:13,515 WARN  - [pool-2-thread-10:] ~ got exception trying to 
> get groups for user admin: id: admin: no such user
> id: admin: no such user
>  (ShellBasedUnixGroupsMapping:87)
> 2017-06-16 07:02:13,515 ERROR - [pool-2-thread-10:] ~ Exception while 
> fetching groups  (AtlasAbstractAuthenticationProvider:120)
> java.io.IOException: No groups found for user admin
> at org.apache.hadoop.security.Groups.noGroupsForUser(Groups.java:190)
> at org.apache.hadoop.security.Groups.access$400(Groups.java:69)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:307)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:257)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3542)
> at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2323)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2286)
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2201)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3953)
> at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3957)
> at 
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4875)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:215)
> at 
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:113)
> at 
> org.apache.atlas.web.filters.AtlasKnoxSSOAuthenticationFilter.doFilter(AtlasKnoxSSOAuthenticationFilter.java:171)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.StaleTransactionCleanupFilter.doFilter(StaleTransactionCleanupFilter.java:55)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:85)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:158)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:200)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.FilterChainProx

[jira] [Updated] (ATLAS-1878) NPE when a request without any query path lands on atlas

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1878:
---
Fix Version/s: 0.8.1-incubating

> NPE when a request without any query path lands on atlas
> 
>
> Key: ATLAS-1878
> URL: https://issues.apache.org/jira/browse/ATLAS-1878
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1878.patch
>
>
> {noformat}
> 2017-06-16 07:02:13,515 WARN  - [pool-2-thread-10:] ~ got exception trying to 
> get groups for user admin: id: admin: no such user
> id: admin: no such user
>  (ShellBasedUnixGroupsMapping:87)
> 2017-06-16 07:02:13,515 ERROR - [pool-2-thread-10:] ~ Exception while 
> fetching groups  (AtlasAbstractAuthenticationProvider:120)
> java.io.IOException: No groups found for user admin
> at org.apache.hadoop.security.Groups.noGroupsForUser(Groups.java:190)
> at org.apache.hadoop.security.Groups.access$400(Groups.java:69)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:307)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:257)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3542)
> at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2323)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2286)
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2201)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3953)
> at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3957)
> at 
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4875)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:215)
> at 
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:113)
> at 
> org.apache.atlas.web.filters.AtlasKnoxSSOAuthenticationFilter.doFilter(AtlasKnoxSSOAuthenticationFilter.java:171)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.StaleTransactionCleanupFilter.doFilter(StaleTransactionCleanupFilter.java:55)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:85)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:158)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:200)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214)
> at 
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
> at 
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
> at 
> org.spring

[jira] [Updated] (ATLAS-1878) NPE when a request without any query path lands on atlas

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1878:
---
Attachment: ATLAS-1878.patch

This patch handles NPE in getAPI method.

> NPE when a request without any query path lands on atlas
> 
>
> Key: ATLAS-1878
> URL: https://issues.apache.org/jira/browse/ATLAS-1878
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1878.patch
>
>
> {noformat}
> 2017-06-16 07:02:13,515 WARN  - [pool-2-thread-10:] ~ got exception trying to 
> get groups for user admin: id: admin: no such user
> id: admin: no such user
>  (ShellBasedUnixGroupsMapping:87)
> 2017-06-16 07:02:13,515 ERROR - [pool-2-thread-10:] ~ Exception while 
> fetching groups  (AtlasAbstractAuthenticationProvider:120)
> java.io.IOException: No groups found for user admin
> at org.apache.hadoop.security.Groups.noGroupsForUser(Groups.java:190)
> at org.apache.hadoop.security.Groups.access$400(Groups.java:69)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:307)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:257)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3542)
> at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2323)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2286)
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2201)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3953)
> at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3957)
> at 
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4875)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:215)
> at 
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:113)
> at 
> org.apache.atlas.web.filters.AtlasKnoxSSOAuthenticationFilter.doFilter(AtlasKnoxSSOAuthenticationFilter.java:171)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.StaleTransactionCleanupFilter.doFilter(StaleTransactionCleanupFilter.java:55)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:85)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:158)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:200)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214)
> at 
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
> at 
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
> at 
> org.spring

[jira] [Assigned] (ATLAS-1878) NPE when a request without any query path lands on atlas

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1878:
--

Assignee: Nixon Rodrigues

> NPE when a request without any query path lands on atlas
> 
>
> Key: ATLAS-1878
> URL: https://issues.apache.org/jira/browse/ATLAS-1878
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.9-incubating
>
>
> {noformat}
> 2017-06-16 07:02:13,515 WARN  - [pool-2-thread-10:] ~ got exception trying to 
> get groups for user admin: id: admin: no such user
> id: admin: no such user
>  (ShellBasedUnixGroupsMapping:87)
> 2017-06-16 07:02:13,515 ERROR - [pool-2-thread-10:] ~ Exception while 
> fetching groups  (AtlasAbstractAuthenticationProvider:120)
> java.io.IOException: No groups found for user admin
> at org.apache.hadoop.security.Groups.noGroupsForUser(Groups.java:190)
> at org.apache.hadoop.security.Groups.access$400(Groups.java:69)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:307)
> at org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:257)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3542)
> at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2323)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2286)
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2201)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3953)
> at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3957)
> at 
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4875)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:215)
> at 
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:113)
> at 
> org.apache.atlas.web.filters.AtlasKnoxSSOAuthenticationFilter.doFilter(AtlasKnoxSSOAuthenticationFilter.java:171)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.StaleTransactionCleanupFilter.doFilter(StaleTransactionCleanupFilter.java:55)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:85)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:158)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:200)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at 
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214)
> at 
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
> at 
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
> at 
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
> at 

[jira] [Updated] (ATLAS-1863) Set default value for primitive types attributes in entity based on attributeDef in Typedef

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1863:
---
Attachment: ATLAS-1863.3.patch

> Set default value for primitive types attributes in entity based on 
> attributeDef in Typedef
> ---
>
> Key: ATLAS-1863
> URL: https://issues.apache.org/jira/browse/ATLAS-1863
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>    Reporter: Nixon Rodrigues
>Assignee: Ruchi Solani
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1863.2.patch, ATLAS-1863.3.patch, ATLAS-1863.patch
>
>
> While creating entity if attribute value are not set explicitly for primitive 
> type which are optional, then default value should be set from attributedef.
> eg of typedef attributeDef
> {code}
> "attributeDefs": [{
>   "name": "sourceCode",
>   "typeName": "string",
>   "isOptional": true,
>   "cardinality": "SINGLE",
>   "valuesMinCount": 0,
>   "valuesMaxCount": 1,
>   "isUnique": false,
>   "isIndexable": true,
>   "defaultValue": "xyz"
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 59799: ATLAS-1766 : Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59799/
---

(Updated June 14, 2017, 3:19 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
Sarath Subramanian.


Changes
---

This patch handles review comments from Sarath and testcases fix.

# 2 test cases related to offset autocommit false are failing are commented.


Repository: atlas


Description
---

This patch include changes that implements kafka new-consumer api for 
kafkaConsumer for Atlas Notification System.


Diffs (updated)
-

  distro/src/conf/atlas-application.properties 5e59528 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaMessage.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 16c0eb2 
  notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
8bd31fd 
  
notification/src/main/java/org/apache/atlas/notification/AbstractMessageDeserializer.java
 9585827 
  
notification/src/main/java/org/apache/atlas/notification/AbstractNotificationConsumer.java
 d4d78de 
  
notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
 a99cb10 
  notification/src/test/java/org/apache/atlas/kafka/KafkaConsumerTest.java 
ad7d93e 
  
notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationMockTest.java
 2126be6 
  notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
a810029 
  
notification/src/test/java/org/apache/atlas/notification/AbstractNotificationConsumerTest.java
 13f2f0b 
  typesystem/src/test/resources/atlas-application.properties c4ce5ea 
  
webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
 2f8245d 
  webapp/src/test/java/org/apache/atlas/notification/EntityNotificationIT.java 
ac3b538 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerKafkaTest.java
 18fd2ee 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
 bdb60a2 
  webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
b59d3ee 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
 310b2e3 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java
 98a7abc 


Diff: https://reviews.apache.org/r/59799/diff/3/

Changes: https://reviews.apache.org/r/59799/diff/2-3/


Testing
---

Tested Kafka consumer on local embeded kafka /zookeeper env.
Tested Atlas Hive hook notifications.
Excecute Quick Start script.

Due to change in kafkaconsumer api the current notification related UT/IT's 
need to changed, i have not included this change in this patch but will 
included it shortly.


Thanks,

Nixon Rodrigues

[jira] [Commented] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047656#comment-16047656
 ] 

Nixon Rodrigues commented on ATLAS-1823:


Thanks [~kevalbhatt] for the review,

Committed patch on following branches.

* master 
https://git1-us-west.apache.org/repos/asf/incubator-atlas/repo?p=incubator-atlas.git;a=commit;h=894a91f6097969073c8356fd6aac6490b6b619d9

* 0.8.incubating 
https://git1-us-west.apache.org/repos/asf/incubator-atlas/repo?p=incubator-atlas.git;a=commit;h=4076597903ce5aad8280d6fd083f6e76ec858f01

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues resolved ATLAS-1823.

   Resolution: Fixed
Fix Version/s: 0.8.1-incubating

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 59876: ATLAS-1832 - If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59876/#review177718
---


Ship it!




Ship It!

- Nixon Rodrigues


On June 13, 2017, 6:59 a.m., Kalyani Kashikar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59876/
> ---
> 
> (Updated June 13, 2017, 6:59 a.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-1832
> https://issues.apache.org/jira/browse/ATLAS-1832
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Step to reproduce : - 
> 
> Create tag without attribute.
> Tag detail page shows the edit button whether attribute is present or not.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/js/templates/audit/CreateAuditTableLayoutView_tmpl.html 
> fc8e6cc 
>   dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js cdbd00f 
> 
> 
> Diff: https://reviews.apache.org/r/59876/diff/2/
> 
> 
> Testing
> ---
> 
> If no attribute is present in tag then detail page does not show edit button.
> It only visiable when attribute is present in tag.
> 
> 
> Thanks,
> 
> Kalyani Kashikar
> 
>

Re: Review Request 60014: ATLAS-1872: Spring based bean ordering/configuration change

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60014/#review177667
---


Ship it!




Ship It!

- Nixon Rodrigues


On June 12, 2017, 6:21 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60014/
> ---
> 
> (Updated June 12, 2017, 6:21 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
> Sarath Subramanian, and Suma Shivaprasad.
> 
> 
> Bugs: ATLAS-1872
> https://issues.apache.org/jira/browse/ATLAS-1872
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. In a kerberized environment Atlas fails to start as the LoginProcessor 
> doesn't perform login before bean creation
> 2. HBaseAuditRepository should be default instead of NoopEntityAuditRepository
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
>  89ca7480 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/NoopEntityAuditRepository.java
>  7c39ce9b 
>   webapp/src/main/java/org/apache/atlas/web/listeners/LoginProcessor.java 
> e21656e7 
>   webapp/src/main/java/org/apache/atlas/web/setup/KerberosAwareListener.java 
> PRE-CREATION 
>   webapp/src/main/webapp/WEB-INF/web.xml d2d08f5a 
> 
> 
> Diff: https://reviews.apache.org/r/60014/diff/1/
> 
> 
> Testing
> ---
> 
> mvn clean package (success)
> mvn clean install (partial success with known failures)
> 
> Started Atlas manually and verified that the LoginProcessor.login in invoked 
> well before any bean creation.
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Re: Review Request 59799: ATLAS-1766 : Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues]

> On June 7, 2017, 6:56 p.m., Suma Shivaprasad wrote:
> > notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java
> > Line 129 (original), 133 (patched)
> > <https://reviews.apache.org/r/59799/diff/1/?file=1741124#file1741124line138>
> >
> > any reason this was removed?

With this property kafkaconsumer fails connect and ends up with exception, 
tested this on local embedded kafka, need to test on external standalone kafka


- Nixon


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59799/#review177208
---


On June 12, 2017, 3:02 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59799/
> ---
> 
> (Updated June 12, 2017, 3:02 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
> Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch include changes that implements kafka new-consumer api for 
> kafkaConsumer for Atlas Notification System.
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties 5e59528 
>   notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
> PRE-CREATION 
>   notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaMessage.java 
> PRE-CREATION 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 
> 16c0eb2 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
> 8bd31fd 
>   
> notification/src/main/java/org/apache/atlas/notification/AbstractMessageDeserializer.java
>  9585827 
>   
> notification/src/main/java/org/apache/atlas/notification/AbstractNotificationConsumer.java
>  d4d78de 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
>  a99cb10 
>   notification/src/test/java/org/apache/atlas/kafka/KafkaConsumerTest.java 
> ad7d93e 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationMockTest.java
>  2126be6 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
> a810029 
>   
> notification/src/test/java/org/apache/atlas/notification/AbstractNotificationConsumerTest.java
>  13f2f0b 
>   
> webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  2f8245d 
>   
> webapp/src/test/java/org/apache/atlas/notification/EntityNotificationIT.java 
> ac3b538 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerKafkaTest.java
>  18fd2ee 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
>  bdb60a2 
>   webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
> b59d3ee 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
>  310b2e3 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java
>  98a7abc 
> 
> 
> Diff: https://reviews.apache.org/r/59799/diff/2/
> 
> 
> Testing
> ---
> 
> Tested Kafka consumer on local embeded kafka /zookeeper env.
> Tested Atlas Hive hook notifications.
> Excecute Quick Start script.
> 
> Due to change in kafkaconsumer api the current notification related UT/IT's 
> need to changed, i have not included this change in this patch but will 
> included it shortly.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

Re: Review Request 59799: ATLAS-1766 : Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59799/
---

(Updated June 12, 2017, 3:02 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
Sarath Subramanian.


Changes
---

This patch includes review comments by Apoorv & Suma. Also includes testcase 
changes for new-consumer api.
Testcase related auto.commit offset and few others are pending and commented.


Repository: atlas


Description
---

This patch include changes that implements kafka new-consumer api for 
kafkaConsumer for Atlas Notification System.


Diffs (updated)
-

  distro/src/conf/atlas-application.properties 5e59528 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaMessage.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 16c0eb2 
  notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
8bd31fd 
  
notification/src/main/java/org/apache/atlas/notification/AbstractMessageDeserializer.java
 9585827 
  
notification/src/main/java/org/apache/atlas/notification/AbstractNotificationConsumer.java
 d4d78de 
  
notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
 a99cb10 
  notification/src/test/java/org/apache/atlas/kafka/KafkaConsumerTest.java 
ad7d93e 
  
notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationMockTest.java
 2126be6 
  notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
a810029 
  
notification/src/test/java/org/apache/atlas/notification/AbstractNotificationConsumerTest.java
 13f2f0b 
  
webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
 2f8245d 
  webapp/src/test/java/org/apache/atlas/notification/EntityNotificationIT.java 
ac3b538 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerKafkaTest.java
 18fd2ee 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
 bdb60a2 
  webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
b59d3ee 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
 310b2e3 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java
 98a7abc 


Diff: https://reviews.apache.org/r/59799/diff/2/

Changes: https://reviews.apache.org/r/59799/diff/1-2/


Testing
---

Tested Kafka consumer on local embeded kafka /zookeeper env.
Tested Atlas Hive hook notifications.
Excecute Quick Start script.

Due to change in kafkaconsumer api the current notification related UT/IT's 
need to changed, i have not included this change in this patch but will 
included it shortly.


Thanks,

Nixon Rodrigues

Re: Review Request 59441: KNOX-788 :- Apache Atlas Admin UI Support through Knox

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59441/
---

(Updated June 9, 2017, 2:31 p.m.)


Review request for atlas, Knox, David Radley, Larry McCay, and Madhan Neethiraj.


Changes
---

This patch includes changed to remove policy with anoymous user from service 
definition.

Tested Atlas UI and api with this change.


Bugs: KNOX-788
https://issues.apache.org/jira/browse/KNOX-788


Repository: knox


Description
---

This patch includes service definition and rewrite rules xml for Atlas Admin UI 
to support proxy through Knox.
It is dependent on KNOX-789 and ATLAS-1823


Diffs (updated)
-

  
gateway-service-definitions/src/main/resources/services/atlas/0.8.0/rewrite.xml 
PRE-CREATION 
  
gateway-service-definitions/src/main/resources/services/atlas/0.8.0/service.xml 
PRE-CREATION 


Diff: https://reviews.apache.org/r/59441/diff/2/

Changes: https://reviews.apache.org/r/59441/diff/1-2/


Testing
---

Tested Atlas UI for all the CRUD operation for the UI pages, UI is loading fine.
Login & Logout functionality.

https://knox-host:8443/gateway/ui/atlas/index#!/detailPage/3683a3a3-b1c2-4a66-9ed2-ab40c15ebed9


Thanks,

Nixon Rodrigues

[jira] [Created] (ATLAS-1866) Documentation for PAM type authentication.

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1866:
--

 Summary: Documentation for PAM type authentication.
 Key: ATLAS-1866
 URL: https://issues.apache.org/jira/browse/ATLAS-1866
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues
Assignee: Shi Wang






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1804) Allow PAM for authentication

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1804:
---
Attachment: ATLAS-1804.3.patch

> Allow PAM for authentication
> 
>
> Key: ATLAS-1804
> URL: https://issues.apache.org/jira/browse/ATLAS-1804
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 0001-ATLAS-1804.patch, ATLAS-1804.3.patch
>
>
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (ATLAS-1804) Allow PAM for authentication

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reopened ATLAS-1804:


There was testcase fail so reopening the jira

> Allow PAM for authentication
> 
>
> Key: ATLAS-1804
> URL: https://issues.apache.org/jira/browse/ATLAS-1804
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 0001-ATLAS-1804.patch
>
>
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 59494: ATLAS-1804 Allow PAM for authentication

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59494/#review177295
---


Ship it!




Ship It!

- Nixon Rodrigues


On June 7, 2017, 9:12 p.m., Shi Wang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59494/
> ---
> 
> (Updated June 7, 2017, 9:12 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik and Nixon Rodrigues.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type.
> 
> 
> Diffs
> -
> 
>   webapp/pom.xml 4132912 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasAuthenticationProvider.java
>  80d6604 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
>  PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/security/PamLoginModule.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/security/PamPrincipal.java 
> PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/web/security/UserAuthorityGranter.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/59494/diff/2/
> 
> 
> Testing
> ---
> 
> create a pam file atlas-login under /etc/pam.d/
> 
> in the file using unix login module for testing.
> 
> content could be something like:
> authsufficientpam_unix.so
> account sufficientpam_unix.so
> 
> create a unix user with password.
> login to atlas ui with the unix user will success.
> 
> 
> Thanks,
> 
> Shi Wang
> 
>

[jira] [Created] (ATLAS-1863) Set default value for primitive types attributes in entity based on attributeDef in Typedef

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1863:
--

 Summary: Set default value for primitive types attributes in 
entity based on attributeDef in Typedef
 Key: ATLAS-1863
 URL: https://issues.apache.org/jira/browse/ATLAS-1863
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-intg
Reporter: Nixon Rodrigues
Assignee: Ruchi Solani
Priority: Critical
 Fix For: 0.9-incubating


While creating entity if attribute value are not set explicitly for primitive 
type which are optional, then default value should be set from attributedef.

eg of typedef attributeDef

{code}
"attributeDefs": [  {
"name": "sourceCode",
"typeName": "string",
"isOptional": true,
"cardinality": "SINGLE",
"valuesMinCount": 0,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true,
"defaultValue": "xyz"
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1861) Documentation for Creating entities through web UI for inbuilt & self-defined types.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1861:
---
External issue URL:   (was: 
https://issues.apache.org/jira/browse/ATLAS-1860)

> Documentation for Creating entities through web UI for inbuilt & self-defined 
> types.
> 
>
> Key: ATLAS-1861
> URL: https://issues.apache.org/jira/browse/ATLAS-1861
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Nixon Rodrigues
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1860) Cannot create entities through web UI for self-defined types

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038396#comment-16038396
 ] 

Nixon Rodrigues commented on ATLAS-1860:


[~xiaqinglin]
By default if there in no properties Atlas loads the default type list which 
you are getting now.

for selected type, add types name delimited with comma
atlas.ui.editable.entity.types=hdfs_path,hbase_table,hbase_column

for All Types add * as value
atlas.ui.editable.entity.types=*

Hope this helps

> Cannot create entities through web UI for self-defined types
> 
>
> Key: ATLAS-1860
> URL: https://issues.apache.org/jira/browse/ATLAS-1860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.9-incubating
>Reporter: qinglin,xia
>  Labels: atlas
> Attachments: createdTypes.png, 
> only_default_types_can_be_created_using_web_ui.png
>
>
> Currently the default types that can be created using the atlas web ui are 
> only "hdfs_path,hbase_table,hbase_column,hbase_column_family,kafka_topic"
> But when I created types using the restful api, for example, in the attached 
> pic "createdTypes.png", I created type: HBaseNamespace, I would want to 
> create entities of type HBaseNamespace through the web ui, but the web ui 
> does not showed the updated type of HBase Namespace for me to create 
> entities. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1861) Documentation for Creating entities through web UI for inbuilt & self-defined types.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1861:
---
Issue Type: Improvement  (was: Bug)

> Documentation for Creating entities through web UI for inbuilt & self-defined 
> types.
> 
>
> Key: ATLAS-1861
> URL: https://issues.apache.org/jira/browse/ATLAS-1861
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Nixon Rodrigues
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1861) Documentation for Creating entities through web UI for inbuilt & self-defined types.

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1861:
--

 Summary: Documentation for Creating entities through web UI for 
inbuilt & self-defined types.
 Key: ATLAS-1861
 URL: https://issues.apache.org/jira/browse/ATLAS-1861
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1860) Cannot create entities through web UI for self-defined types

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues resolved ATLAS-1860.

Resolution: Not A Bug

Its not a bug.


[~xiaqinglin]

Add a new property  *atlas.ui.editable.entity.types=** in 
atlas-application.properties and restart Atlas, this should load all the Atlas 
Entity Types.

I will file a JIRA to provide documentation for  create entities through web UI 
for self-defined types feature.



> Cannot create entities through web UI for self-defined types
> 
>
> Key: ATLAS-1860
> URL: https://issues.apache.org/jira/browse/ATLAS-1860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.9-incubating
>Reporter: qinglin,xia
>  Labels: atlas
> Attachments: createdTypes.png, 
> only_default_types_can_be_created_using_web_ui.png
>
>
> Currently the default types that can be created using the atlas web ui are 
> only "hdfs_path,hbase_table,hbase_column,hbase_column_family,kafka_topic"
> But when I created types using the restful api, for example, in the attached 
> pic "createdTypes.png", I created type: HBaseNamespace, I would want to 
> create entities of type HBaseNamespace through the web ui, but the web ui 
> does not showed the updated type of HBase Namespace for me to create 
> entities. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1766:
---
Attachment: ATLAS-1766.1.patch

> Atlas with Kafka SASL_SSL protocol
> --
>
> Key: ATLAS-1766
> URL: https://issues.apache.org/jira/browse/ATLAS-1766
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Sandeep Nemuri
>    Assignee: Nixon Rodrigues
> Attachments: ATLAS-1766.1.patch
>
>
> Creating this jira to add support to Kafka SASL_SSL protocol for Atlas.
> Atlas is currently using old consumer api which doesn't support SSL 
> protocols. To support SSL protocol the consumer code should be re-written in 
> new consumer api.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 59799: ATLAS-1766 : Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59799/
---

Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
Sarath Subramanian.


Repository: atlas


Description
---

This patch include changes that implements kafka new-consumer api for 
kafkaConsumer for Atlas Notification System.


Diffs
-

  distro/src/conf/atlas-application.properties 5e59528 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
PRE-CREATION 
  notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 16c0eb2 
  notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
8bd31fd 
  
notification/src/main/java/org/apache/atlas/notification/AbstractMessageDeserializer.java
 9585827 
  
notification/src/main/java/org/apache/atlas/notification/AbstractNotificationConsumer.java
 d4d78de 
  
notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
 a99cb10 
  
webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
 2f8245d 


Diff: https://reviews.apache.org/r/59799/diff/1/


Testing
---

Tested Kafka consumer on local embeded kafka /zookeeper env.
Tested Atlas Hive hook notifications.
Excecute Quick Start script.

Due to change in kafkaconsumer api the current notification related UT/IT's 
need to changed, i have not included this change in this patch but will 
included it shortly.


Thanks,

Nixon Rodrigues

[jira] [Assigned] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1766:
--

Assignee: Nixon Rodrigues

> Atlas with Kafka SASL_SSL protocol
> --
>
> Key: ATLAS-1766
> URL: https://issues.apache.org/jira/browse/ATLAS-1766
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Sandeep Nemuri
>    Assignee: Nixon Rodrigues
>
> Creating this jira to add support to Kafka SASL_SSL protocol for Atlas.
> Atlas is currently using old consumer api which doesn't support SSL 
> protocols. To support SSL protocol the consumer code should be re-written in 
> new consumer api.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1832) If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1832:
---
Component/s: atlas-webui

> If no attribute is present in tag  then showing edit-button for a tag in tags 
> tab on entity page.
> -
>
> Key: ATLAS-1832
> URL: https://issues.apache.org/jira/browse/ATLAS-1832
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Chrome
>    Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
> Attachments: edit attribute for tag bug .png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1832) If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1832:
---
Affects Version/s: 0.8-incubating

> If no attribute is present in tag  then showing edit-button for a tag in tags 
> tab on entity page.
> -
>
> Key: ATLAS-1832
> URL: https://issues.apache.org/jira/browse/ATLAS-1832
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Chrome
>    Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
> Attachments: edit attribute for tag bug .png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1832) If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1832:
--

 Summary: If no attribute is present in tag  then showing 
edit-button for a tag in tags tab on entity page.
 Key: ATLAS-1832
 URL: https://issues.apache.org/jira/browse/ATLAS-1832
 Project: Atlas
  Issue Type: Bug
 Environment: Chrome
Reporter: Nixon Rodrigues
Assignee: Kalyani Kashikar
 Attachments: edit attribute for tag bug .png





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1809) UI : Update button in Edit tag attributes window should be enabled only when any update is done

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026098#comment-16026098
 ] 

Nixon Rodrigues commented on ATLAS-1809:


+1 for the patch.


> UI : Update button in Edit tag attributes window should be enabled only when 
> any update is done
> ---
>
> Key: ATLAS-1809
> URL: https://issues.apache.org/jira/browse/ATLAS-1809
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
>Priority: Minor
> Attachments: ATLAS-1809.patch
>
>
> Even though no update is made to any of the attributes of tag associated to 
> entity, "Update" button is enabled in Edit Tag window . Audit is also 
> generated with event 'Tag Updated'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1811) UI : Audit Events are not shown in sorted order based on time sometimes.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026097#comment-16026097
 ] 

Nixon Rodrigues commented on ATLAS-1811:


+1 for the patch.


> UI : Audit Events are not shown in sorted order based on time sometimes.
> 
>
> Key: ATLAS-1811
> URL: https://issues.apache.org/jira/browse/ATLAS-1811
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1811.patch, AuditDetailsUnordered.png
>
>
> Created an entity and made did many tag association , dis-association and tag 
> update to that entity. All audit details are captured but not displayed in 
> sorted order based on timestamp value present in audit response. A few 
> entries are missing order.
> Attached the screenshot .



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026095#comment-16026095
 ] 

Nixon Rodrigues commented on ATLAS-1817:


+1 for the patch.


> UI : n+1 pages are created, even though only n*25 instances are retrieved.
> --
>
> Key: ATLAS-1817
> URL: https://issues.apache.org/jira/browse/ATLAS-1817
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1817.patch
>
>
> 1.Created 50 tables.
> 2.First page showed 1-25 tables , second page 26 -50 tables .
> 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty 
> response.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1810) UI : Audit details of any tag event (Added,Updated) has only tag name and event.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026091#comment-16026091
 ] 

Nixon Rodrigues commented on ATLAS-1810:


+1 for the patch.

> UI : Audit details of any tag event (Added,Updated) has only tag name and 
> event.
> 
>
> Key: ATLAS-1810
> URL: https://issues.apache.org/jira/browse/ATLAS-1810
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
>Priority: Minor
> Attachments: ATLAS-1810.patch
>
>
> On clicking Details of Audit events like "Tag Added" , "Tag updated" in Audit 
> tab , Details window shows only the Audit event and tag name. Tag attributes 
> are not displayed. Since "Edit Attribute of Tag" feature is introduced, it 
> would be good to display the attributes of tag like it does for Entities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1808) UI : All selected entities are assigned to tag when Assign Tag corresponding to 1 entity is clicked.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026092#comment-16026092
 ] 

Nixon Rodrigues commented on ATLAS-1808:


+1 for the patch.


> UI : All selected entities are assigned to tag when Assign Tag corresponding 
> to 1 entity is clicked.
> 
>
> Key: ATLAS-1808
> URL: https://issues.apache.org/jira/browse/ATLAS-1808
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Attachments: ATLAS-1808.1.patch, ATLAS-1808.patch
>
>
> Steps:
> 1. Searched for type hive_table which listed 10 results.
> 2. Selected all the entities (using check box).
> 3. Clicked on Assign tag button corresponding to the first result ex : table1 
> ( "+" sign button with class a.InputTagAdd.assignTag)
> 4. Selected the tag to be assigned ex:tag1
> 5. Expected tag1 would be assigned to only table1 though all the entities are 
> selected. But all the entities are assigned to tag1.
> Note : Didn't click on Button with text  " + Assign Tag" (class : 
> a.inputAssignTag.multiSelectTag.assignTag.btnAssign) after selecting multiple 
> entities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Graduate Apache Atlas Project from Incubator

[Nixon Rodrigues]

pose to
> establish a
> >> Project Management Committee charged with the creation and maintenance
> of
> >> open-source software, for distribution at no charge to the public,
> related
> >> to a data management platform That provides real-time, consistent access
> >> to data-intensive applications throughout widely distributed cloud
> >> architectures.
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Atlas Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >> RESOLVED,that the Apache Atlas Project be and hereby is responsible for
> >> the creation and maintenance of software related to a data management
> >> platform that provides real-time, consistent access to data-intensive
> >> applications throughout widely distributed cloud architectures.
> >>
> >> RESOLVED, that the office of "Vice President, Apache Atlas" be and
> >> hereby is created, the person holding such office to serve at the
> >> direction of the Board of Directors as the chair of the Apache Atlas
> >> Project, and to have primary responsibility for management of the
> projects
> >> within the scope of responsibility of the Apache Atlas Project; and be
> it
> >> Further.
> >>
> >>>RESOLVED,that the persons listed immediately below be and hereby are
> >>>appointed to serve as the initial members of the Apache Atlas Project:
> >>
> >> Aaron Dossett adoss...@target.com <mailto:adoss...@target.com>
> >> Andrew Ahn a...@apache.org <mailto:a...@apache.org>
> >> Anil Varma ava...@slb.com <mailto:ava...@slb.com>
> >> Arun C. Murthy acmur...@apache.org <mailto:acmur...@apache.org>
> >> Apoorv Naik apoorvn...@apache.org <mailto:apoorvn...@apache.org>
> >> Ayub Pathan ayubpat...@apache.org <mailto:ayubpat...@apache.org>
> >> Barbara Stortz bsto...@sap.com <mailto:bsto...@sap.com>
> >> Chris Hyzer chy...@aetna.com <mailto:chy...@aetna.com>
> >> Daniel Markwat dmark...@aetna.com <mailto:dmark...@aetna.com>
> >> Darshan Kumar darshanku...@apache.org <mailto:darshanku...@apache.org>
> >> Dave Kantor dkan...@apache.org <mailto:dkan...@apache.org>
> >> David Kaspar dkas...@merck.com <mailto:dkas...@merck.com>
> >> Dennis Fusaro dfus...@aetna.com <mailto:dfus...@aetna.com>
> >> Greg Senia gse...@aetna.com <mailto:gse...@aetna.com>
> >> Harish Butani rhbut...@apache.org <mailto:rhbut...@apache.org>
> >> Hemanth Yamijala yhema...@apache.org <mailto:yhema...@apache.org>
> >> Ivo Lasek ila...@merck.com <mailto:ila...@merck.com>
> >> James Vollmer ja...@target.com <mailto:ja...@target.com>
> >> Jeffrey Hagelberg jnhagelb...@apache.org <mailto:jnhagelb...@apache.org
> >
> >> Jitendra Pandey jiten...@apache.org <mailto:jiten...@apache.org>
> >> Jon Maron jma...@apache.org <mailto:jma...@apache.org>
> >> Kalyani Kalshikar kalyanikashi...@apache.org <mailto:kalyanikashikar@
> >> apache.org>
> >> Keval Bhatt kbhatt kbh...@apache.org <mailto:kbh...@apache.org>
> >> Madhan Neethiraj mad...@apache.org <mailto:mad...@apache.org>
> >> Mitch Schussler mschuss...@apache.org <mailto:mschuss...@apache.org>
> >> Neeru Gupta guptane...@us.ibm.com <mailto:guptane...@us.ibm.com>
> >> Nixon Rodrigues ni...@apache.org <mailto:ni...@apache.org>
> >> Sarath Subramanian sar...@apache.org <mailto:sar...@apache.org>
> >> Shwetha GS  shweth...@apache.org <mailto:shweth...@apache.org>
> >> Srikanth Sundarrajan srik...@apache.org <mailto:srik...@apache.org>
> >> Suma Shivaprasad suma...@apache.org <mailto:suma...@apache.org>
> >> Suresh Srinivas ssur...@apache.org <mailto:ssur...@apache.org>
> >> Tom Beerbower tbeerbo...@apache.org <mailto:tbeerbo...@apache.org>
> >> Venkat Ranganathan vranganat...@apache.org <mailto:vranganathan@apache.
> org>
> >> Venkatesh Seetharam venkat...@apache.org <mailto:venkat...@apache.org>
> >> Vimal Sharma svimal2...@apache.org <mailto:svimal2...@apache.org>
> >> Vinod Kumar Vavilapalli vino...@apache.org <mailto:vino...@apache.org>
> >> Viswanath Avasarala vavasar...@slb.com <mailto:vavasar...@slb.com>
> >>
> >>
> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that "Madhan Neethiraj" be
> >> appointed to the office of Vice President, Apache Atlas, to serve in
> >> accordance with and
> >> subject to the direction of the Board of Directors and the Bylaws of the
> >> Foundation until death, resignation, retirement, removal or
> >> disqualification, or until a successor is appointed; and be it further
> >> RESOLVED, that the initial Apache Atlas PMC be and hereby is tasked with
> >> the creation of a set of bylaws intended to encourage open development
> and
> >> increased participation in the Apache Atlas Project; and be it further
> >>
> >> RESOLVED, that the Apache Atlas Project be and hereby is tasked with the
> >> migration of the Apache Incubator Atlas podling; and be it further
> >>
> >> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> >> Atlas polling encumbered upon the Apache Incubator Project are hereafter
> >> discharged.
> >>
> >> Thanks
> >> Suma
> >>
> >>
> >
>

Re: Review Request 59494: ATLAS-1804 Allow PAM for authentication

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59494/#review175896
---




webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
Lines 60 (patched)
<https://reviews.apache.org/r/59494/#comment249256>

loginModuleName & controlFlag are constant values, make no sense 
initializing for every user login call, they qualify to be static member 
variable.



webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
Lines 62 (patched)
<https://reviews.apache.org/r/59494/#comment249254>

The"atlas.authentication.method.pam" is application based property and it 
is getting called for every getPamAuthentication call,

Should be called constructor or init method or method with @postconstruct



webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
Lines 69 (patched)
<https://reviews.apache.org/r/59494/#comment249247>

can add opening and closing brackets {} for better readability.



webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
Lines 75 (patched)
<https://reviews.apache.org/r/59494/#comment249258>

From line # 60 to line 81 code can be initialized once in init method, 
please check



webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
Lines 105 (patched)
<https://reviews.apache.org/r/59494/#comment249259>

From where is the groups for user come from for PAM authentication ?  

I tested PAM based authentication and got DATA_SCIENTIST always.

For LDAP/AD if spring authentication does not returns user group then  
groups are retrived from UNIX/Hadoop UGI using 
getAuthenticationWithGrantedAuthorityFromUGI, check 
AtlasADAuthenticationProvider for more details.



webapp/src/main/java/org/apache/atlas/web/security/UserAuthorityGranter.java
Lines 29 (patched)
<https://reviews.apache.org/r/59494/#comment249255>

Remove this comment


- Nixon Rodrigues


On May 23, 2017, 6:20 p.m., Shi Wang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59494/
> ---
> 
> (Updated May 23, 2017, 6:20 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik and Nixon Rodrigues.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type.
> 
> 
> Diffs
> -
> 
>   webapp/pom.xml 045ccdb 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasAuthenticationProvider.java
>  953d737 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasPamAuthenticationProvider.java
>  PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/security/PamLoginModule.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/security/PamPrincipal.java 
> PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/web/security/UserAuthorityGranter.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/59494/diff/1/
> 
> 
> Testing
> ---
> 
> create a pam file atlas-login under /etc/pam.d/
> 
> in the file using unix login module for testing.
> 
> content could be something like:
> authsufficientpam_unix.so
> account sufficientpam_unix.so
> 
> create a unix user with password.
> login to atlas ui with the unix user will success.
> 
> 
> Thanks,
> 
> Shi Wang
> 
>

Re: Review Request 59439: KNOX-789 :- Apache Atlas REST API support

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59439/
---

(Updated May 22, 2017, 10:59 a.m.)


Review request for atlas, Knox, Larry McCay, and Madhan Neethiraj.


Bugs: KNOX-789
https://issues.apache.org/jira/browse/KNOX-789


Repository: knox


Description
---

This patch includes service definition and rewrite rules for Atlas API to 
support proxy through Knox.


Diffs
-

  
gateway-service-definitions/src/main/resources/services/atlas-api/0.8.0/rewrite.xml
 PRE-CREATION 
  
gateway-service-definitions/src/main/resources/services/atlas-api/0.8.0/service.xml
 PRE-CREATION 


Diff: https://reviews.apache.org/r/59439/diff/1/


Testing
---

Tested the api from curl and also from Atlas admin UI


[root@rd-atl-080517-2 bin]# curl -i -k -L -u admin:admin -X GET  
'https://knox-host:8443/gateway/ui/atlas/api/atlas/v2/types/typedefs?type=classification&_=1495442879421'
HTTP/1.1 200 OK
Date: Mon, 22 May 2017 08:50:03 GMT
Date: Mon, 22 May 2017 08:50:03 GMT
Set-Cookie: ATLASSESSIONID=oscz5x1nocfn14y4bj0yv52vs;Path=/;HttpOnly
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Frame-Options: DENY
Content-Type: application/json; charset=UTF-8
Server: Jetty(9.2.12.v20150709)
Content-Length: 2070

{"enumDefs":[],"structDefs":[],"classificationDefs":[{"category":"CLASSIFICATION","guid":"abce22ee-a6ed-40f3-816a-555049997b71","createTime":1495108634535,"updateTime":1495108634535,"version":1,"name":"KnoxProxy","description":"KnoxProxy","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"2410969e-f592-4db8-82d7-47bf6996d090","createTime":1495011488803,"updateTime":1495011488803,"version":1,"name":"PII","description":"PII
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"ac122a83-37e1-4c60-a260-2a262c98b2f8","createTime":1495011490270,"updateTime":1495011490270,"version":1,"name":"JdbcAccess","description":"JdbcAccess
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"7bff86b0-a77e-43a0-9577-c125196bb497","createTime":1495011490296,"updateTime":1495011490296,"version":1,"name":"Log
 Data","description":"LogData Classification","
 
typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"1099a2a2-932a-4f1d-9f6c-4ed04021f88e","createTime":1495011488817,"updateTime":1495011488817,"version":1,"name":"Metric","description":"Metric
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"228842fe-7035-4fd2-9c6c-48b1d74a0995","createTime":1495011487356,"updateTime":1495011487356,"version":1,"name":"Dimension","description":"Dimension
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"900d0441-393e-4b2f-b6f5-161d5b057d36","createTime":1495011489541,"updateTime":1495011489541,"version":1,"name":"ETL","description":"ETL
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"42d1752d-58de-4816-8bcb-7157eda14d7f","createTime":1495011488088,"updateTime":1495011488088,"version":1,"name":"Fact","description":"Fact
 Classification
 ","typeVersion":"1.0","attributeDefs":[],"superTypes":[]}],"entityDefs":[]}


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1819:
---
Description: 
1. Created a tag tag1.
2. Created a table table1.
3. tag1 is *not associated* to table1
The following query returns 500 Internal server error. 
{code}
/api/atlas/v2/entity/guid//classification/tag1
{code}

Exception thrown :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
Attached the complete exception trace thrown in application logs.

4. Now created another tag tag2 and associated table1 to tag2.
5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
expected error code 404.

That is , when any tag is already associated to the entity, search for the 
unassociated tag throws 404 , else 500.

  was:
1. Created a tag tag1.
2. Created a table table1.
3. tag1 is *not associated* to table1
The following query returns 500 Internal server error. 
{code}
/api/atlas/v2/entity/guid//tag1
{code}

Exception thrown :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
Attached the complete exception trace thrown in application logs.

4. Now created another tag tag2 and associated table1 to tag2.
5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
expected error code 404.

That is , when any tag is already associated to the entity, search for the 
unassociated tag throws 404 , else 500.


> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ArrayOutOfBoundsException.txt
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1823:
---
Fix Version/s: 0.9-incubating

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1823:
---
Attachment: ATLAS-1823.patch

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1823:
--

Assignee: Nixon Rodrigues

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1823:
--

 Summary: UI - Change in base path URL for few api/images to make 
it relative from path it is accessed.
 Key: ATLAS-1823
 URL: https://issues.apache.org/jira/browse/ATLAS-1823
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


The currently in Atlas the base path for api and few image are relative to root 
of the application, ie it always resolves to http://.
Which causing issue when Atlas UI is accessed for Knox Proxy.

Proposing following changes in path to make it relative from path it is 
accessed.

{code}
-
+
{code}

{code}
-baseUrl: '/api/atlas',
-baseUrlV2: '/api/atlas/v2',
+baseUrl: 'api/atlas',
+baseUrlV2: 'api/atlas/v2',
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1767) Support KNOX SSO Token based authentication on Atlas REST API calls

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1767:
---
Fix Version/s: 0.8-incubating

> Support KNOX SSO Token based authentication on Atlas REST API calls
> ---
>
> Key: ATLAS-1767
> URL: https://issues.apache.org/jira/browse/ATLAS-1767
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1767.patch
>
>
> Currently Authentication for Atlas with Knox SSO is supported for broswer 
> based userAgent only.
> Removing this restriction to support KNOX SSO Token based authentication on 
> Atlas REST API calls from all user-agents with hadoop-jwt cookie in header.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1806) Error while redirecting it to Tag tab after doing advance search and creating entity

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1806:
--

 Summary: Error while redirecting it to Tag tab after doing advance 
search and creating entity
 Key: ATLAS-1806
 URL: https://issues.apache.org/jira/browse/ATLAS-1806
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues
 Attachments: SS11.png

 Steps to reproduce:-
1.Do an Advance Search
2.Then create an entity
3.Click on search tab
4.Now click on Tags Tab

Error:- It would redirect back to Search Tab which is incorrect



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1759) UI - Add checkbox to exclude/include deleted entities in schema table.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012327#comment-16012327
 ] 

Nixon Rodrigues commented on ATLAS-1759:


+1 for the patch.

> UI - Add checkbox to exclude/include deleted entities in schema table.
> --
>
> Key: ATLAS-1759
> URL: https://issues.apache.org/jira/browse/ATLAS-1759
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1759.1.patch, ATLAS-1759.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [QUESTION] Change Findbugs to fail a build on error

[Nixon Rodrigues]

Jan,

Appreciate your effort to improve Atlas code quality.

I think we should keep a threshold limit for  findbugs issue, if new code
introduced adds code issue and cross the limit it should fails the build.
Is this possible ?

Nixon

On Tue, May 16, 2017 at 1:47 AM, Jan Hentschel <
jan.hentsc...@ultratendency.com> wrote:

> Hi,
>
>
>
> I filed ATLAS-1789 for fixing the Findbugs issues throughout the codebase.
> Currently these issues don’t let the build fail. Just want to start a
> discussion on whether to change the configuration to fail the build on
> Findbugs errors. Any opinions?
>
>
>
> Best, Jan
>
>

[jira] [Commented] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006216#comment-16006216
 ] 

Nixon Rodrigues commented on ATLAS-1776:


Verified, +1 for the patch

> Include historical entities in UI : A query is made and cancelled every time 
> the check box is checked/unchecked showing "Invalid expression:null" 
> notification
> --
>
> Key: ATLAS-1776
> URL: https://issues.apache.org/jira/browse/ATLAS-1776
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1776.1.patch, ATLAS-1776.2.patch
>
>
> Steps to replicate :
> 1.In basic search , searched for type "hive_table".
> 2.Checked "Include historical entities" 
> 3. Unchecked it. At this time the following query is made twice :
> http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table
> first of the 2 queries is cancelled and Invalid Expression : null 
> notification pops up.
> Note : This happens only when clicking on the "Include historical entities" 
> text . On checking / unchecking the check box itself, no such extra queries 
> are made.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1759) UI - Add checkbox to exclude/include deleted entities in schema table.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004731#comment-16004731
 ] 

Nixon Rodrigues commented on ATLAS-1759:


Thanks [~Kalyanikashikar] for the patch. Verified the schema UI, it works fine.

Committed the patch.
* master - 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/1decc731
* 0.8-incubating - 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7882ec26

> UI - Add checkbox to exclude/include deleted entities in schema table.
> --
>
> Key: ATLAS-1759
> URL: https://issues.apache.org/jira/browse/ATLAS-1759
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1759.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 58988: ATLAS-1759 : UI - Add checkbox to exclude/include deleted entities in schema table.

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58988/#review174474
---


Ship it!




Ship It!

- Nixon Rodrigues


On May 4, 2017, 11:49 a.m., Kalyani Kashikar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58988/
> ---
> 
> (Updated May 4, 2017, 11:49 a.m.)
> 
> 
> Review request for atlas, keval bhatt and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-1759
> https://issues.apache.org/jira/browse/ATLAS-1759
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add checkbox for schema table to exclude/include deleted entities.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/js/templates/schema/SchemaTableLayoutView_tmpl.html 
> c133d1f 
>   dashboardv2/public/js/views/schema/SchemaLayoutView.js 75714f0 
> 
> 
> Diff: https://reviews.apache.org/r/58988/diff/1/
> 
> 
> Testing
> ---
> 
> Verified added checkbox in schema table to include deleted entities.
> 
> 
> Thanks,
> 
> Kalyani Kashikar
> 
>

[jira] [Created] (ATLAS-1771) Atlas UI - While deleting Tag the Confirmation Popup appears incorrectly in IE-9

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1771:
--

 Summary: Atlas UI - While deleting Tag the Confirmation Popup 
appears incorrectly in IE-9
 Key: ATLAS-1771
 URL: https://issues.apache.org/jira/browse/ATLAS-1771
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
 Environment: Browser - IE-9
Reporter: Nixon Rodrigues
 Attachments: SS3.jpg





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1767) Support KNOX SSO Token based authentication on Atlas REST API calls

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1767:
---
Attachment: ATLAS-1767.patch

> Support KNOX SSO Token based authentication on Atlas REST API calls
> ---
>
> Key: ATLAS-1767
> URL: https://issues.apache.org/jira/browse/ATLAS-1767
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1767.patch
>
>
> Currently Authentication for Atlas with Knox SSO is supported for broswer 
> based userAgent only.
> Removing this restriction to support KNOX SSO Token based authentication on 
> Atlas REST API calls from all user-agents with hadoop-jwt cookie in header.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 59023: ATLAS-1767 :- Support KNOX SSO Token based authentication on Atlas REST API calls

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59023/
---

Review request for atlas, Apoorv Naik, Ayub Pathan, Madhan Neethiraj, and 
Sarath Subramanian.


Repository: atlas


Description
---

This patch includes change to support knox sso authentication from all 
user-agent when knox cookie header are being in request header.


Diffs
-

  
webapp/src/main/java/org/apache/atlas/web/filters/AtlasKnoxSSOAuthenticationFilter.java
 c3219b9 


Diff: https://reviews.apache.org/r/59023/diff/1/


Testing
---

Verified authentication from various scenarios.

* From Browser with Knox Authentication

* From Login Page browser

* From from Curl client with various header option

* With knox hadoop-jwt-cookie header
curl -kivL --negotiate -u :  http://:21000/api/atlas/session --cookie 
"hadoop-jwt=eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImlzcyI6IktOT1hTU08iLCJleHAiOjE0OTQyODc3MDF9.aj5E0bqTlmnn42gxBm0geogNpX6XwXaEFhDrt-0ANbQpsF2gL2Fn8Lb9hBu9x2R9WFiCv9Wc2H58mW93H_k17yQFqHnJc5OfFOnQ-oI4BYABe7Wi4HkmD3ocRHXc6coY9RbR7Tu6FYT-8ZNH99FgmU20XqXFnmTUgxQYSosjXzU"

* With Kerberos negotiate header
curl -kivL --negotiate -u :  http://:21000/api/atlas/admin/session

* With Basic Auth Header
curl -kivL -u admin:admin  http://:21000/api/atlas/session

* From Jersey Java Client ie verified Quick Start script


Thanks,

Nixon Rodrigues

[jira] [Created] (ATLAS-1767) Support KNOX SSO Token based authentication on Atlas REST API calls

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1767:
--

 Summary: Support KNOX SSO Token based authentication on Atlas REST 
API calls
 Key: ATLAS-1767
 URL: https://issues.apache.org/jira/browse/ATLAS-1767
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.8-incubating
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 0.9-incubating


Currently Authentication for Atlas with Knox SSO is supported for broswer based 
userAgent only.
Removing this restriction to support KNOX SSO Token based authentication on 
Atlas REST API calls from all user-agents with hadoop-jwt cookie in header.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1707:
---
Attachment: ATLAS-1707.3.patch

This patch ATLAS-1707.3.patch contains missing font file 
"toadOcfmlt9b38dHJxOBGEo0As1BFRXtCDhS66znb_k.woff2"

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1707.2.patch, ATLAS-1707.3.patch, 
> ATLAS-1707.patch, index.html, index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reopened ATLAS-1707:


font file -> toadOcfmlt9b38dHJxOBGEo0As1BFRXtCDhS66znb_k.woff2 is missing, so 
re-opening this issue.

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1707.2.patch, ATLAS-1707.patch, index.html, 
> index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1737) UI - Delete tag(classification) from UI.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1737:
---
Attachment: Atlas-1737 issue.png

> UI - Delete tag(classification) from UI.
> 
>
> Key: ATLAS-1737
> URL: https://issues.apache.org/jira/browse/ATLAS-1737
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, Atlas-1737 
> issue.png, ATLAS-1737.patch
>
>
> Ability to delete tag from UI using API 
> (api/atlas/v2/types/typedefs?type=classification) DELETE method.
> _Tags which are not assigned to any entity can be only deleted._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1737) UI - Delete tag(classification) from UI.

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988567#comment-15988567
 ] 

Nixon Rodrigues commented on ATLAS-1737:


[~Kalyanikashikar], I tried testing your patch and found one issue which should 
be fixed before patch goes in.

Steps to reproduce the issue.
1) Create a new tag "tagfordelete"
2) Search for the newly created tag by clicking on ellipses(...)
3) Go to Tags tab and then delete the newly created tag.
4) Now to click on Search Tab, by default it is making a search call  for the 
deleted tag
{code}
http://localhost:21000/api/atlas/v2/search/basic?limit=25=tagfordelete&_=1493373025839
 
{code}
I think UI is caching the previous search keyword, can you look into this ?

Nixon


> UI - Delete tag(classification) from UI.
> 
>
> Key: ATLAS-1737
> URL: https://issues.apache.org/jira/browse/ATLAS-1737
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, ATLAS-1737.patch
>
>
> Ability to delete tag from UI using API 
> (api/atlas/v2/types/typedefs?type=classification) DELETE method.
> _Tags which are not assigned to any entity can be only deleted._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] Ready to graduate?

[Nixon Rodrigues]

Chris, Thanks for initiating this discuss.

 +1 for the graduation process for Atlas.


Nixon



On Thu, Apr 27, 2017 at 10:41 AM, Vimal Sharma 
wrote:

> +1 for graduation.
>
> Atlas community has been a pleasure to work with and we have rapidly
> developed new features and improvements to the project.
>
> Thanks
> Vimal
>
>
>
>
> On 4/27/17, 9:47 AM, "Hemanth Yamijala"  wrote:
>
> >+1 from me as well.
> >
> >It has been a pleasure  being involved with Atlas and see the product and
> community grow.
> >
> >Thanks, Chris, for starting this thread.
> >
> >Hemanth
> >
> >From: Jakob Homan 
> >Sent: Thursday, April 27, 2017 4:27 AM
> >To: dev@atlas.incubator.apache.org
> >Subject: Re: [DISCUSS] Ready to graduate?
> >
> >+1.
> >
> >I've not been very involved with the day-to-day bits of the project as
> >Mentor, so when the new PMC is constituted, there's no need to include
> >me.  But I'll stay a fan of Atlas after graduation.
> >
> >-Jakob
> >
> >On 26 April 2017 at 15:29, Suma Shivaprasad
> > wrote:
> >> +1. Agreed
> >>
> >> The community is really vibrant/active with many companies involved in
> >> shaping the roadmap and features.
> >>  It has also grown a lot from past year with a lot of interest from
> users
> >> and this is a great time to propose for graduation
> >>
> >> I volunteer to start working on the graduation and take this forward if
> no
> >> one else has any objections.
> >>
> >> Thanks
> >> Suma
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Apr 26, 2017 at 2:03 AM, Nigel L Jones 
> wrote:
> >>
> >>>
> >>>
> >>> +1 from me.
> >>>
> >>> The Atlas community is vibrant, we have engagement from multiple
> companies,
> >>> and the industry interest around governance is immense, as witnessed at
> >>> recent conferences. It's exciting to see it evolve and getting it into
> a
> >>> TLP will be another tick in the box as seen by potential users.
> >>>
> >>> Let's go for it!
> >>>
> >>> -Original Message-
> >>> From: Mandy Chessell [mailto:mandy_chess...@uk.ibm.com]
> >>> Sent: 26 April 2017 07:30
> >>> To: dev@atlas.incubator.apache.org
> >>> Subject: Re: [DISCUSS] Ready to graduate?
> >>>
> >>> Hello Chris,
> >>> No concerns at all ... we have a vibrant, multi-company community that
> is
> >>> working together to expand Atlas's capability to be THE open metadata
> and
> >>> governance platform for data and analytics.  Many other
> >>> people/organizations are eager to consume the results.   Moving the
> >>> project out of incubation sends a strong message to our stakeholders
> and
> >>> users that Atlas is here to stay and through that we can strengthen the
> >>> community further.
> >>>
> >>> All the best
> >>> Mandy
> >>> ___
> >>> Mandy Chessell CBE FREng CEng FBCS
> >>> IBM Distinguished Engineer
> >>>
> >>> Master Inventor
> >>> Member of the IBM Academy of Technology
> >>> Visiting Professor, Department of Computer Science, University of
> Sheffield
> >>>
> >>> Email: mandy_chess...@uk.ibm.com
> >>> LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49
> >>>
> >>> Assistant: Janet Brooks - jsbrook...@uk.ibm.com
> >>>
> >>>
> >>>
> >>> From:   Chris Douglas 
> >>> To: dev@atlas.incubator.apache.org
> >>> Date:   26/04/2017 01:45
> >>> Subject:[DISCUSS] Ready to graduate?
> >>>
> >>>
> >>>
> >>> Hey Atlas folk-
> >>>
> >>> The name search JIRA is filled in [1] (thanks Madhan!), pending
> approval
> >>> from VP trademarks. Independent of its resolution, does the community
> feel
> >>> it is ready to graduate?
> >>>
> >>> As far as I've observed, the project is more than ready to be a
> top-level
> >>> project. Are there any concerns we should discuss before we proceed?
> >>>
> >>> The process, roughly:
> >>> 1. Community discussion of graduation
> >>> 2. [VOTE] to graduate (PPMC votes binding) 3. Cite thread in
> >>> general@incubator for discussion/vote (IPMC votes
> >>> binding)
> >>> 4. Add a resolution to the board agenda establishing Atlas as a
> top-level
> >>> project 5. ASF board approves the resolution at its next meeting, Atlas
> >>> becomes a TLP
> >>>
> >>> The project will also need to pick a chair for the new PMC. We can
> discuss
> >>> that when we post the resolution. -C
> >>>
> >>> [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118
> >>>
> >>>
> >>> Unless stated otherwise above:
> >>> IBM United Kingdom Limited - Registered in England and Wales with
> number
> >>> 741598.
> >>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
> 3AU
> >>>
> >>>
> >
> >
>

[jira] [Commented] (ATLAS-1752) Atlas Group mapping for ranger doesn't work if using kerberos authentication

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982942#comment-15982942
 ] 

Nixon Rodrigues commented on ATLAS-1752:


This patch is dependent on ATLAS-1680 and could not create review request for 
it due some error in review board.

> Atlas Group mapping for ranger doesn't work if using kerberos authentication
> 
>
> Key: ATLAS-1752
> URL: https://issues.apache.org/jira/browse/ATLAS-1752
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
> Environment: secure
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1752.patch
>
>
> {code}
> [DI50253@devbir1en3l ~]$ curl --negotiate -u : -X GET 
> "http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
>  
>  
>  
>  
> Error 403 {AuthorizationError:You are not authorized 
> for READ on [ENTITY] : *} 
>  
> HTTP ERROR 403 
> Problem accessing 
> /api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f. Reason: 
>  {AuthorizationError:You are not authorized for READ 
> on [ENTITY] : *}Powered by 
> Jetty:// 
>  
>  
> I checked ID of the user and they belong to the group that is in ranger.
> If he uses ldap authentication then it group mapping works
> [DI50253@devbir1en3l ~]$ curl -u DI50253: -X GET 
> "http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
>  
> {"requestId":"qtp1641313620-23 - 
> \/api\/atlas\/entities\/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f - 
> 3f71704c-75e4-40dc-9796-4827e5997ea6","definition":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f","version":0,"typeName":"hive_db","state":"ACTIVE"},"typeName":"hive_db","values":{"name":"dz_1_disc","location":"hdfs:\/\/devbir1\/data\/discovery\/dz_1\/disc","description":null,"ownerType":{"value":"USER","ordinal":1},"qualifiedName":"dz_1_disc@devbir1","owner":"hive","clusterName":"devbir1","parameters":null},"traitNames":[],"traits":{}}}
>  
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1752) Atlas Group mapping for ranger doesn't work if using kerberos authentication

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1752:
---
Attachment: ATLAS-1752.patch

> Atlas Group mapping for ranger doesn't work if using kerberos authentication
> 
>
> Key: ATLAS-1752
> URL: https://issues.apache.org/jira/browse/ATLAS-1752
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
> Environment: secure
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1752.patch
>
>
> {code}
> [DI50253@devbir1en3l ~]$ curl --negotiate -u : -X GET 
> "http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
>  
>  
>  
>  
> Error 403 {AuthorizationError:You are not authorized 
> for READ on [ENTITY] : *} 
>  
> HTTP ERROR 403 
> Problem accessing 
> /api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f. Reason: 
>  {AuthorizationError:You are not authorized for READ 
> on [ENTITY] : *}Powered by 
> Jetty:// 
>  
>  
> I checked ID of the user and they belong to the group that is in ranger.
> If he uses ldap authentication then it group mapping works
> [DI50253@devbir1en3l ~]$ curl -u DI50253: -X GET 
> "http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
>  
> {"requestId":"qtp1641313620-23 - 
> \/api\/atlas\/entities\/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f - 
> 3f71704c-75e4-40dc-9796-4827e5997ea6","definition":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f","version":0,"typeName":"hive_db","state":"ACTIVE"},"typeName":"hive_db","values":{"name":"dz_1_disc","location":"hdfs:\/\/devbir1\/data\/discovery\/dz_1\/disc","description":null,"ownerType":{"value":"USER","ordinal":1},"qualifiedName":"dz_1_disc@devbir1","owner":"hive","clusterName":"devbir1","parameters":null},"traitNames":[],"traits":{}}}
>  
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1752) Atlas Group mapping for ranger doesn't work if using kerberos authentication

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1752:
--

 Summary: Atlas Group mapping for ranger doesn't work if using 
kerberos authentication
 Key: ATLAS-1752
 URL: https://issues.apache.org/jira/browse/ATLAS-1752
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8-incubating
 Environment: secure
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 0.8-incubating, 0.9-incubating


{code}
[DI50253@devbir1en3l ~]$ curl --negotiate -u : -X GET 
"http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
 
 
 
 
Error 403 {AuthorizationError:You are not authorized 
for READ on [ENTITY] : *} 
 
HTTP ERROR 403 
Problem accessing /api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f. 
Reason: 
 {AuthorizationError:You are not authorized for READ on 
[ENTITY] : *}Powered by Jetty:// 

 
 

I checked ID of the user and they belong to the group that is in ranger.

If he uses ldap authentication then it group mapping works

[DI50253@devbir1en3l ~]$ curl -u DI50253: -X GET 
"http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
 
{"requestId":"qtp1641313620-23 - 
\/api\/atlas\/entities\/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f - 
3f71704c-75e4-40dc-9796-4827e5997ea6","definition":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f","version":0,"typeName":"hive_db","state":"ACTIVE"},"typeName":"hive_db","values":{"name":"dz_1_disc","location":"hdfs:\/\/devbir1\/data\/discovery\/dz_1\/disc","description":null,"ownerType":{"value":"USER","ordinal":1},"qualifiedName":"dz_1_disc@devbir1","owner":"hive","clusterName":"devbir1","parameters":null},"traitNames":[],"traits":{}}}
 
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1739) Remote debug Apache Atlas Admin

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1739:
--

Assignee: Nixon Rodrigues

> Remote debug Apache Atlas Admin
> ---
>
> Key: ATLAS-1739
> URL: https://issues.apache.org/jira/browse/ATLAS-1739
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Muhammad Imran
>Assignee: Nixon Rodrigues
>
> I want to remote debug Apache Atlas admin in Eclipse. Where exactly I have to 
> set JVM debug options in Apache Atlas package?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1738) Remote debug Apache Atlas Admin

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues resolved ATLAS-1738.

Resolution: Duplicate

> Remote debug Apache Atlas Admin
> ---
>
> Key: ATLAS-1738
> URL: https://issues.apache.org/jira/browse/ATLAS-1738
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Muhammad Imran
>
> I want to remote debug Apache Atlas admin in Eclipse. Where exactly I have to 
> set JVM debug options in Apache Atlas package?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1739) Remote debug Apache Atlas Admin

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues resolved ATLAS-1739.

Resolution: Resolved

> Remote debug Apache Atlas Admin
> ---
>
> Key: ATLAS-1739
> URL: https://issues.apache.org/jira/browse/ATLAS-1739
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Muhammad Imran
>
> I want to remote debug Apache Atlas admin in Eclipse. Where exactly I have to 
> set JVM debug options in Apache Atlas package?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1739) Remote debug Apache Atlas Admin

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976904#comment-15976904
 ] 

Nixon Rodrigues commented on ATLAS-1739:


[~m.imran.tariq]

In atlas_start.py, add jvm debug argument to this variable 
{noformat}
DEFAULT_JVM_OPTS="-Dlog4j.configuration=atlas-log4j.xml 
-Djava.net.preferIPv4Stack=true -server  <%debug option string%>"
{noformat}

if you are using atlas-env.sh then add to ATLAS_OPTS var

> Remote debug Apache Atlas Admin
> ---
>
> Key: ATLAS-1739
> URL: https://issues.apache.org/jira/browse/ATLAS-1739
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Muhammad Imran
>
> I want to remote debug Apache Atlas admin in Eclipse. Where exactly I have to 
> set JVM debug options in Apache Atlas package?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 58419: ATLAS-1707 : Atlas WUI on continues loading behind FireWall

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58419/
---

Review request for atlas, keval bhatt and Madhan Neethiraj.


Bugs: ATLAS-1707
https://issues.apache.org/jira/browse/ATLAS-1707


Repository: atlas


Description
---

Bug Details: Atlas is behind a FW in which does return a response. We Identify 
index.html was loading googleapis css does not have a timeout and proceed with 
the WUI;

Fix:-
Removed reference to external css and font file & copied fonts and css file 
locally.


Diffs
-

  dashboardv2/public/css/googlefonts.css PRE-CREATION 
  dashboardv2/public/index.html 9f1d941 
  
dashboardv2/public/js/external_lib/fonts/ODelI1aHBYDBqgeIAH2zlNV_2ngZ8dMf8fLgjYEouxg.woff2
 PRE-CREATION 
  
dashboardv2/public/js/external_lib/fonts/toadOcfmlt9b38dHJxOBGCOFnW3Jk0f09zW_Yln67Ac.woff2
 PRE-CREATION 
  
dashboardv2/public/js/external_lib/fonts/toadOcfmlt9b38dHJxOBGEo0As1BFRXtCDhS66znb_k.woff2
 PRE-CREATION 


Diff: https://reviews.apache.org/r/58419/diff/1/


Testing
---

Tested Atlas UI and fonts files served from atlas server.
packaging, unit test case and rat:check is tested.


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1707:
---
Attachment: ATLAS-1707.patch

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Attachments: ATLAS-1707.patch, index.html, index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1732) After Zoom_out from Lineage view scroll stopped working

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965832#comment-15965832
 ] 

Nixon Rodrigues commented on ATLAS-1732:


Also cherrypicked on 0.8-incubating, commit id - 
34c3f8d5b9c65d07900eff36b28792e30d46848cv

> After Zoom_out from Lineage view scroll stopped working
> ---
>
> Key: ATLAS-1732
> URL: https://issues.apache.org/jira/browse/ATLAS-1732
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1732.patch
>
>
> Steps to reproduce.
> * Collapse Lineage window.
> * Then click on zoom-in button
> * Then click on zoom-out button
> After performing the above step you will see scroll stopped working. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1732) After Zoom_out from Lineage view scroll stopped working

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965820#comment-15965820
 ] 

Nixon Rodrigues commented on ATLAS-1732:


+1 for the patch. Verified the UI change.
Committed to master, commit id - 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c3813d29

Thanks [~kevalbhatt] for the patch.

> After Zoom_out from Lineage view scroll stopped working
> ---
>
> Key: ATLAS-1732
> URL: https://issues.apache.org/jira/browse/ATLAS-1732
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1732.patch
>
>
> Steps to reproduce.
> * Collapse Lineage window.
> * Then click on zoom-in button
> * Then click on zoom-out button
> After performing the above step you will see scroll stopped working. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1727) Mask userdetails in quick Start utility

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1727:
---
Attachment: ATLAS-1727.patch

> Mask userdetails in quick Start utility 
> 
>
> Key: ATLAS-1727
> URL: https://issues.apache.org/jira/browse/ATLAS-1727
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Attachments: ATLAS-1727.patch
>
>
> Quick Start utility requires username and password.
> Its better to hide the password part of it



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 58353: ATLAS-1727: Mask userdetails in quick Start utility

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58353/
---

Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


Bugs: ATLAS-1727
https://issues.apache.org/jira/browse/ATLAS-1727


Repository: atlas


Description
---

Bug details :- Quick Start utility requires username and password.Its better to 
hide the password part of it.
Used console.readPassword method of System.console to readpassword and thereby 
hidding the password detail.


Diffs
-

  common/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java 6430fb1 


Diff: https://reviews.apache.org/r/58353/diff/1/


Testing
---

Tested Quick start and atlas_admin.py utilities and they working fine.
Packaging going fine.


Thanks,

Nixon Rodrigues

[jira] [Commented] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964341#comment-15964341
 ] 

Nixon Rodrigues commented on ATLAS-1714:


+1 for the patch, patch applies well, verified the fix.

> UI : Properties tab doesn't load when an entity has attribute of type array 
> of integers 
> 
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Attachments: ATLAS-1714.patch
>
>
> Created a type with array of integers as on of its attributes :
> {code}
>   { 
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity 
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable 
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate 
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender 
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at 
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1727) Mask userdetails in quick Start utility

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1727:
--

Assignee: Nixon Rodrigues

> Mask userdetails in quick Start utility 
> 
>
> Key: ATLAS-1727
> URL: https://issues.apache.org/jira/browse/ATLAS-1727
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
>
> Quick Start utility requires username and password.
> Its better to hide the password part of it



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1727) Mask userdetails in quick Start utility

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1727:
--

 Summary: Mask userdetails in quick Start utility 
 Key: ATLAS-1727
 URL: https://issues.apache.org/jira/browse/ATLAS-1727
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


Quick Start utility requires username and password.
Its better to hide the password part of it



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1697:
---
Attachment: ATLAS-1697.patch

> import-hive.sh script logs debug/info logs on console instead of 
> import-hive.log  log file.
> ---
>
> Key: ATLAS-1697
> URL: https://issues.apache.org/jira/browse/ATLAS-1697
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1697.patch, atlas-log4j.xml, import-hive.sh
>
>
> Found the issue of hive import script logs not being appended to log file. 
> For import-hive the log file path of import-hive.log  is configured in script 
> and the logs should append to this log file. 
> Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  
> But the atlas-log4j.xml referenced from class-path is from typesystem module 
> in which it is mentioned to output debug logs on console and also do not not 
> have file appender in it. 
> {noformat}
> log4j: Using URL 
> [jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
>  for automatic log4j configuration.
> 
> 
> 
> 
> {noformat}
> The fix for appending logs in 
> /usr/hdp/current/atlas-server/logs/import-hive.log  file.
> # change the typesystem module atlas-log.xml and add log appender tag but it 
> cannot be edited since it packaged in jar
> # referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
> and *\{atlas.log.dir\}* in this file are already expanded and also the file 
> may not be present on server where hive is running. 
> # Have a copy 
> [atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
>  for import hive and update path in import-hive.sh to use this 
> atlas-log4j.xml [ This is workaround if hit by this issue ]
> {noformat}
> JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
> -Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 58234: ATLAS-1697 : import-hive.sh script logs debug/info logs on console instead of import-hive.log log file

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58234/
---

Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


Bugs: ATLAS-1697
https://issues.apache.org/jira/browse/ATLAS-1697


Repository: atlas


Description
---

Found the issue of hive import script logs not being appended to log file.

Solution Implementation to solve the issue.

1) Have a atlas-hive-import-log4j.xml dedicated to import hive script process 
inside hive-bridge module.
2) Change the current reference of atlas-logj.xml and refer to 
atlas-hive-import-log4j.xml


Diffs
-

  addons/hive-bridge/src/bin/import-hive.sh 1032aa2 
  addons/hive-bridge/src/main/resources/atlas-hive-import-log4j.xml 
PRE-CREATION 


Diff: https://reviews.apache.org/r/58234/diff/1/


Testing
---

Tested the logs appending after running the import-hive script.
Build and testcases are executing fine.


Thanks,

Nixon Rodrigues

[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Nixon Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956553#comment-15956553
 ] 

Nixon Rodrigues commented on ATLAS-1707:


[~emattosHWX]

You are right Atlas should run in Self contain env without making request to 
external js/css resources. Will fix this in coming release.

You can download the css from 
https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic
 
and copy the css in webapp/css directory of Atlas Server and change the link  
to downloaded css file in index.html which you have referred. This is should 
solve the issue you are facing.



> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Attachments: index.html, index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1707:
--

Assignee: Nixon Rodrigues

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Attachments: index.html, index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1697:
---
Attachment: import-hive.sh
atlas-log4j.xml

As suggested in #3 for workaround, i have updated the atlas-log4j.xml path in 
import-hive.log and uploaded this files to this jira.
Follow below steps
- cd /usr/hdp/current/atlas-server/hook-bin/
- Copy the import-hive.sh and atlas-log4.xml in hook-bin directory
- Give executable permission to import-hive.sh file is needed.
- Execute import-hive.sh script

{noformat}
[root@rs-atl-28-3 hook-bin]# ./import-hive.sh
Using Hive configuration directory [/etc/hive/conf]
Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log
Enter username for atlas :-

Enter password for atlas :-

Hive Data Model imported successfully!!!
{noformat}

INFO logs will be appended to /usr/hdp/current/atlas-server/logs/import-hive.log

> import-hive.sh script logs debug/info logs on console instead of 
> import-hive.log  log file.
> ---
>
> Key: ATLAS-1697
> URL: https://issues.apache.org/jira/browse/ATLAS-1697
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: atlas-log4j.xml, import-hive.sh
>
>
> Found the issue of hive import script logs not being appended to log file. 
> For import-hive the log file path of import-hive.log  is configured in script 
> and the logs should append to this log file. 
> Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  
> But the atlas-log4j.xml referenced from class-path is from typesystem module 
> in which it is mentioned to output debug logs on console and also do not not 
> have file appender in it. 
> {noformat}
> log4j: Using URL 
> [jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
>  for automatic log4j configuration.
> 
> 
> 
> 
> {noformat}
> The fix for appending logs in 
> /usr/hdp/current/atlas-server/logs/import-hive.log  file.
> # change the typesystem module atlas-log.xml and add log appender tag but it 
> cannot be edited since it packaged in jar
> # referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
> and *\{atlas.log.dir\}* in this file are already expanded and also the file 
> may not be present on server where hive is running. 
> # Have a copy 
> [atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
>  for import hive and update path in import-hive.sh to use this 
> atlas-log4j.xml [ This is workaround if hit by this issue ]
> {noformat}
> JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
> -Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1680) Support for browser login using kerberos kytab

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1680:
--

Assignee: Nixon Rodrigues

> Support for browser login using kerberos kytab
> --
>
> Key: ATLAS-1680
> URL: https://issues.apache.org/jira/browse/ATLAS-1680
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
> Fix For: trunk, 0.9-incubating
>
> Attachments: ATLAS-1680.patch
>
>
> After following the steps mentioned in the below link
> https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM
> Browser login using kerberos keytab is not going through.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1680) Support for browser login using kerberos kytab

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1680:
---
Attachment: ATLAS-1680.patch

> Support for browser login using kerberos kytab
> --
>
> Key: ATLAS-1680
> URL: https://issues.apache.org/jira/browse/ATLAS-1680
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ayub Khan
> Fix For: trunk, 0.9-incubating
>
> Attachments: ATLAS-1680.patch
>
>
> After following the steps mentioned in the below link
> https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM
> Browser login using kerberos keytab is not going through.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 58081: (ATLAS-1680) Support for browser login using kerberos keytab

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58081/
---

Review request for atlas, Apoorv Naik, Ayub Pathan, and Madhan Neethiraj.


Bugs: ATLAS-1680
https://issues.apache.org/jira/browse/ATLAS-1680


Repository: atlas


Description
---

This patch included fix to Support  browser to login using kerberos keytab.
By adding new property 
atlas.authentication.method.kerberos.support.keytab.browser.login=true it is 
enabled.
by default it is disabled, so that it fallback to login page.
If property is enabled, kinit is done with keytab/principal and browser is 
configured for it, then it atlas will autheticate with this principal.
If property is enabled but kinit is not done, then it will fallback to login 
page.


Diffs
-

  
webapp/src/main/java/org/apache/atlas/web/filters/AtlasAuthenticationFilter.java
 9ead75f 


Diff: https://reviews.apache.org/r/58081/diff/1/


Testing
---

Validate Atlas login in kerberos mode. With & without the new property 
atlas.authentication.method.kerberos.support.keytab.browser.login
mvn package and testcase running fine.


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1697:
---
Request participants: Madhan Neethiraj  (was: )

> import-hive.sh script logs debug/info logs on console instead of 
> import-hive.log  log file.
> ---
>
> Key: ATLAS-1697
> URL: https://issues.apache.org/jira/browse/ATLAS-1697
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
>
> Found the issue of hive import script logs not being appended to log file. 
> For import-hive the log file path of import-hive.log  is configured in script 
> and the logs should append to this log file. 
> Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  
> But the atlas-log4j.xml referenced from class-path is from typesystem module 
> in which it is mentioned to output debug logs on console and also do not not 
> have file appender in it. 
> {noformat}
> log4j: Using URL 
> [jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
>  for automatic log4j configuration.
> 
> 
> 
> 
> {noformat}
> The fix for appending logs in 
> /usr/hdp/current/atlas-server/logs/import-hive.log  file.
> # change the typesystem module atlas-log.xml and add log appender tag but it 
> cannot be edited since it packaged in jar
> # referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
> and *\{atlas.log.dir\}* in this file are already expanded and also the file 
> may not be present on server where hive is running. 
> # Have a copy 
> [atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
>  for import hive and update path in import-hive.sh to use this 
> atlas-log4j.xml [ This is workaround if hit by this issue ]
> {noformat}
> JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
> -Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1697:
---
Description: 
Found the issue of hive import script logs not being appended to log file. 

For import-hive the log file path of import-hive.log  is configured in script 
and the logs should append to this log file. 

Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  

But the atlas-log4j.xml referenced from class-path is from typesystem module in 
which it is mentioned to output debug logs on console and also do not not have 
file appender in it. 

{noformat}
log4j: Using URL 
[jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
 for automatic log4j configuration.





{noformat}
The fix for appending logs in 
/usr/hdp/current/atlas-server/logs/import-hive.log  file.

# change the typesystem module atlas-log.xml and add log appender tag but it 
cannot be edited since it packaged in jar
# referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
and *\{atlas.log.dir\}* in this file are already expanded and also the file may 
not be present on server where hive is running. 
# Have a copy 
[atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
 for import hive and update path in import-hive.sh to use this atlas-log4j.xml 
[ This is workaround if hit by this issue ]
{noformat}
JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
-Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
{noformat}

  was:
Found the issue of hive import script logs not being appended to log file. 

For import-hive the log file path of import-hive.log  is configured in script 
and the logs should append to this log file. 

Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  

But the atlas-log4j.xml referenced from class-path is from typesystem module in 
which it is mentioned to output debug logs on console and also do not not have 
file appender in it. 

{noformat}
log4j: Using URL 
[jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
 for automatic log4j configuration.





{noformat}
The fix for appending logs in 
/usr/hdp/current/atlas-server/logs/import-hive.log  file.

# change the typesystem module atlas-log.xml and add log appender tag but it 
cannot be edited since it packaged in jar
# referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
and *\{atlas.log.dir\}* in this file are already expanded and also the file may 
not be present on server where hive is running. 
# Have a copy 
[atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
 for import hive and update path in import-hive.sh to use this atlas-log4j.xml
{noformat}
JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
-Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
{noformat}


> import-hive.sh script logs debug/info logs on console instead of 
> import-hive.log  log file.
> ---
>
> Key: ATLAS-1697
> URL: https://issues.apache.org/jira/browse/ATLAS-1697
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>    Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
>
> Found the issue of hive import script logs not being appended to log file. 
> For import-hive the log file path of import-hive.log  is configured in script 
> and the logs should append to this log file. 
> Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  
> But the atlas-log4j.xml referenced from class-path is from typesystem module 
> in which it is mentioned to output debug logs on console and also do not not 
> have file appender in it. 
> {noformat}
> log4j: Using URL 
> [jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
>  for automatic log4j configuration.
> 
> 
> 
> 
> {noformat}
> The fix for appending logs in 
> /usr/hdp/current/atlas-server/logs/import-hive.log  file.
> # change the typesystem module atlas-log.xml and add log appender tag but it 
> cannot be edited since it packaged in jar
> # referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
> and *\{atlas.log.dir\}* in this file are already expanded and also the file 
> may not be present on server where hive is runn

[jira] [Created] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1697:
--

 Summary: import-hive.sh script logs debug/info logs on console 
instead of import-hive.log  log file.
 Key: ATLAS-1697
 URL: https://issues.apache.org/jira/browse/ATLAS-1697
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8-incubating
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 0.9-incubating


Found the issue of hive import script logs not being appended to log file. 

For import-hive the log file path of import-hive.log  is configured in script 
and the logs should append to this log file. 

Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  

But the atlas-log4j.xml referenced from class-path is from typesystem module in 
which it is mentioned to output debug logs on console and also do not not have 
file appender in it. 

{noformat}
log4j: Using URL 
[jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
 for automatic log4j configuration.





{noformat}
The fix for appending logs in 
/usr/hdp/current/atlas-server/logs/import-hive.log  file.

# change the typesystem module atlas-log.xml and add log appender tag but it 
cannot be edited since it packaged in jar
# referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
and *\{atlas.log.dir\}* in this file are already expanded and also the file may 
not be present on server where hive is running. 
# Have a copy 
[atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
 for import hive and update path in import-hive.sh to use this atlas-log4j.xml
{noformat}
JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
-Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1198) Move from Guice + Spring to only Spring

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1198:
--

Assignee: Apoorv Naik  (was: Nixon Rodrigues)

> Move from Guice + Spring to only Spring
> ---
>
> Key: ATLAS-1198
> URL: https://issues.apache.org/jira/browse/ATLAS-1198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.9-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>
> Right now we're using both Guice and Spring and dependency injection which is 
> not a ideal combination. As Atlas evolves as a product we can leverage the 
> spring framework to avoid re-inventing the wheel like caching, transaction 
> management etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1198) Move from Guice + Spring to only Spring

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1198:
--

Assignee: Nixon Rodrigues  (was: Apoorv Naik)

> Move from Guice + Spring to only Spring
> ---
>
> Key: ATLAS-1198
> URL: https://issues.apache.org/jira/browse/ATLAS-1198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.9-incubating
>Reporter: Apoorv Naik
>    Assignee: Nixon Rodrigues
>
> Right now we're using both Guice and Spring and dependency injection which is 
> not a ideal combination. As Atlas evolves as a product we can leverage the 
> spring framework to avoid re-inventing the wheel like caching, transaction 
> management etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1198) Move from Guice + Spring to only Spring

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1198:
---
Request participants: Ruchi Solani  (was: )

> Move from Guice + Spring to only Spring
> ---
>
> Key: ATLAS-1198
> URL: https://issues.apache.org/jira/browse/ATLAS-1198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.9-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>
> Right now we're using both Guice and Spring and dependency injection which is 
> not a ideal combination. As Atlas evolves as a product we can leverage the 
> spring framework to avoid re-inventing the wheel like caching, transaction 
> management etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1671:
---
Request participants:   (was: bhavik patel)

> Client IP is not populated for Atlas service in audit tab of Ranger
> ---
>
> Key: ATLAS-1671
> URL: https://issues.apache.org/jira/browse/ATLAS-1671
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Atlas with ranger plugin on
>Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1671.patch, atlas_client_IP.png
>
>
> Client IP is not populated for Atlas service in audit tab of Ranger, refer 
> attached image
>  
> !atlas_client_IP.png|width=300,height=300!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1671:
---
Request participants: bhavik patel  (was: )

> Client IP is not populated for Atlas service in audit tab of Ranger
> ---
>
> Key: ATLAS-1671
> URL: https://issues.apache.org/jira/browse/ATLAS-1671
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Atlas with ranger plugin on
>Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1671.patch, atlas_client_IP.png
>
>
> Client IP is not populated for Atlas service in audit tab of Ranger, refer 
> attached image
>  
> !atlas_client_IP.png|width=300,height=300!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 57769: ATLAS-1671 :- Client IP is not populated for Atlas service in audit tab of Ranger

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57769/
---

Review request for atlas, Apoorv Naik and Madhan Neethiraj.


Bugs: ATLAS-1671
https://issues.apache.org/jira/browse/ATLAS-1671


Repository: atlas


Description
---

This patch incudes fix in Atlas for client IP is not populated for Atlas 
service in audit tab of Ranger.


Diffs
-

  
authorization/src/main/java/org/apache/atlas/authorize/AtlasAccessRequest.java 
377aca7 
  
authorization/src/main/java/org/apache/atlas/authorize/simple/AtlasAuthorizationUtils.java
 1b4661e 
  
authorization/src/test/java/org/apache/atlas/authorize/simple/SimpleAtlasAuthorizerTest.java
 a3fc489 
  webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
0dfdeb2 


Diff: https://reviews.apache.org/r/57769/diff/1/


Testing
---

Tested Atlas with Atlas-Ranger plugin on and client IP is recorded and shown in 
RangerAdmin->Audit->Acess UI properly.
Tested Atlas build and the testcases goes well.


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1671:
---
Description: 
Client IP is not populated for Atlas service in audit tab of Ranger, refer 
attached image
 
!atlas_client_IP.png|width=300,height=300!


> Client IP is not populated for Atlas service in audit tab of Ranger
> ---
>
> Key: ATLAS-1671
> URL: https://issues.apache.org/jira/browse/ATLAS-1671
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Atlas with ranger plugin on
>Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1671.patch, atlas_client_IP.png
>
>
> Client IP is not populated for Atlas service in audit tab of Ranger, refer 
> attached image
>  
> !atlas_client_IP.png|width=300,height=300!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1671:
---
Attachment: ATLAS-1671.patch

> Client IP is not populated for Atlas service in audit tab of Ranger
> ---
>
> Key: ATLAS-1671
> URL: https://issues.apache.org/jira/browse/ATLAS-1671
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Atlas with ranger plugin on
>Reporter: Nixon Rodrigues
>    Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1671.patch, atlas_client_IP.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1671:
--

 Summary: Client IP is not populated for Atlas service in audit tab 
of Ranger
 Key: ATLAS-1671
 URL: https://issues.apache.org/jira/browse/ATLAS-1671
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.8-incubating
 Environment: Atlas with ranger plugin on
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 0.9-incubating
 Attachments: atlas_client_IP.png





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (ATLAS-1666) Improve on Overly Broad Throws

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reopened ATLAS-1666:


> Improve on Overly Broad Throws
> --
>
> Key: ATLAS-1666
> URL: https://issues.apache.org/jira/browse/ATLAS-1666
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1666.1.patch, ATLAS-1666.patch
>
>
> Methods in the following classes throws generic exception. This makes it hard 
> for callers to effectively handle errors and recover. Although, this does not 
> impact functionality. It would be valuable to improve on this.
> Below is a files that have this pattern: 
> 1. _ActiveInstanceState.java_
> 2. _AbstractParam.java_
> 3. _QuickStart.java_
> 4. _SetupSteps.java_
> 5. _FalconHook.java_
> 6. _AtlasLdapAuthenticationProvider.java_
> 7. _FalconEventPublisher.java_
> 8. _AtlasADAuthenticationProvider.java_
> 9. _StormHook.java_
> 10. _FalconBridge.java_
> 11. _EmbeddedServer.java_
> 12. _StormTopologyUtil.java_
> 13. _SqoopHook.java_
> 14. _HiveHook.java_
> 15. _HiveMetaStoreBridge.java_
> General approach to refactoring would be define an error code in 
> _AtlasErrorCode_ and throw _AtlasBaseException_.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: New PPMC member to Apache Atlas: Madhan Neethiraj

[Nixon Rodrigues]

Congratulations Madhan!, Thanks for all your hard work and guidance to take
Atlas to new orbit.

Best wishes,
Nixon


On Fri, Mar 17, 2017 at 9:27 AM, Hemanth Yamijala 
wrote:

> Atlas dev community,
>
> Atlas PPMC has invited Madhan Neethiraj to join us as a PPMC member
> and we are glad that he has accepted.
>
> Congratulations, Madhan! Thanks for all your hard work on Atlas.
>
> Hemanth
>

Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 1 (dev group vote)

[Nixon Rodrigues]

   - Verified Checksum and Signature
   - Build Atlas using embedded hbase/solr was successful.
   - Ran QuickStart and QuickStart V1 and verified basic functionality -
   tags, entities, lineage and taxonomy/terms.
   - Created entities from Create entity UI.
   - UI is looking proper in Firefox,Chrome and IE 11 browser.


+1 (non-binding vote) for the release.

Nixon

On Wed, Mar 8, 2017 at 1:30 PM, Madhan Neethiraj  wrote:

> Atlas team,
>
>
>
> Apache Atlas 0.8 (incubating) release candidate #1 is now available for a
> vote within dev community. Links to the release artifacts are given below.
> Can you please review and vote?
>
>
>
> This update includes fix for the following JIRAS: ATLAS-1648, ATLAS-1655,
> ATLAS-1656, ATLAS-1657, ATLAS-1658
>
>
>
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>
> Here is my +1
>
>
>
> Thanks,
>
> Madhan
>
>
>
>
>
> List of improvements and issues addressed in this release:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND%
> 20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.
> 8-incubating%20ORDER%20BY%20key%20DESC
>
>
>
> Git tag for the release: https://github.com/apache/
> incubator-atlas/tree/release-0.8-rc1
>
>
>
> Sources for the release: https://dist.apache.org/repos/
> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.
> 8-incubating-sources.tar.gz
>
>
>
> Source release verification:
>
>   PGP Signature:  https://dist.apache.org/repos/
> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.
> 8-incubating-sources.tar.gz.asc
>
>   MD5 Hash:   https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-
> incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz.md5
>
>
>
> Keys to verify the signature of the release artifacts are available at:
> https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS
>
>
>
>
>
>
>
>
>
>