[jira] [Created] (ATLAS-1890) IntegrationTest cases failing in BaseResourceIT.waitForNotification method
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
[
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.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
>
[jira] [Updated] (ATLAS-1878) NPE when a request without any query path lands on atlas
[
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.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at
>
[jira] [Updated] (ATLAS-1878) NPE when a request without any query path lands on atlas
[
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.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at
>
[jira] [Assigned] (ATLAS-1878) NPE when a request without any query path lands on atlas
[
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
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>
[jira] [Updated] (ATLAS-1863) Set default value for primitive types attributes in entity based on attributeDef in Typedef
[
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)
[jira] [Commented] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.
[
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.
[
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)
[jira] [Created] (ATLAS-1866) Documentation for PAM type authentication.
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
[ 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
[ 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)
[jira] [Created] (ATLAS-1863) Set default value for primitive types attributes in entity based on attributeDef in Typedef
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.
[ 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
[ 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.
[ 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 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
[ 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
[ 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)
[jira] [Assigned] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol
[ 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.
[ 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.
[ 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 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
[ 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.
[ 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.
[ 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.
[ 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.
[ 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)
[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.
[
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.
[
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.
[
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.
[
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 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
[ 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 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.
[ 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)
[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
[ 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.
[ 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)
[jira] [Created] (ATLAS-1771) Atlas UI - While deleting Tag the Confirmation Popup appears incorrectly in IE-9
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
[ 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)
[jira] [Created] (ATLAS-1767) Support KNOX SSO Token based authentication on Atlas REST API calls
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
[ 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
[ 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.
[ 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.
[
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)
[jira] [Commented] (ATLAS-1752) Atlas Group mapping for ranger doesn't work if using kerberos authentication
[
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
[
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 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
[ 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
[ 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
[ 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
[
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)
[jira] [Updated] (ATLAS-1707) Atlas WUI on continues loading behind FireWall
[ 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
[ 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
[ 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
[ 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)
[jira] [Commented] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
[
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
[ 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 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.
[
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)
[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall
[ 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
[ 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.
[
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
[ 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
[ 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)
[jira] [Updated] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.
[
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.
[
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 running.
> # Have a copy
>
[jira] [Created] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.
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
[ 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
[ 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
[ 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
[ 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
[ 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)
[jira] [Updated] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger
[ 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
[ 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 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
[ 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)
[jira] [Commented] (ATLAS-1628) Restrict user from entering text in datepicker input
[ https://issues.apache.org/jira/browse/ATLAS-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894453#comment-15894453 ] Nixon Rodrigues commented on ATLAS-1628: +1 for the patch. > Restrict user from entering text in datepicker input > > > Key: ATLAS-1628 > URL: https://issues.apache.org/jira/browse/ATLAS-1628 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1628.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1538) Make AtlasLdapAuthenticationProvider like Ranger for OpenLdap type
[ https://issues.apache.org/jira/browse/ATLAS-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1538: --- Attachment: ATLAS-1538-1.patch > Make AtlasLdapAuthenticationProvider like Ranger for OpenLdap type > -- > > Key: ATLAS-1538 > URL: https://issues.apache.org/jira/browse/ATLAS-1538 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.7-incubating, 0.7.1-incubating >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-1538-1.patch, ATLAS-1538.patch > > > Currently in Altas , AtlasLdapAuthenticationProvider has > getLdapBindAuthentication method which used for openldap authentication. > Adding new method getLdapAuthentication as a fallback to take care of > failures in login. > I propose AtlasLdapAuthenticationProvider to be like Ranger -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1590) UI : Edit Button is enabled for Deleted entities.
[ https://issues.apache.org/jira/browse/ATLAS-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880595#comment-15880595 ] Nixon Rodrigues commented on ATLAS-1590: +1 for the patch. > UI : Edit Button is enabled for Deleted entities. > - > > Key: ATLAS-1590 > URL: https://issues.apache.org/jira/browse/ATLAS-1590 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > Attachments: ATLAS-1590.patch > > > Deleted a kafka_topic entity using REST API. Add Tag ,Add Term button are not > displayed but edit button is displayed and enabled in the detailsPage of > deleted kafka_topic entity. Though no update is succeeded when trying to > update , the edit button could be removed for deleted entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1487) Create Entity in UI : types list doesn't list fs_permissions (struct type) hence no entity could be created for it.
[ https://issues.apache.org/jira/browse/ATLAS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880587#comment-15880587 ] Nixon Rodrigues commented on ATLAS-1487: Patch applies well , tested the fix. +1 for the patch, > Create Entity in UI : types list doesn't list fs_permissions (struct type) > hence no entity could be created for it. > --- > > Key: ATLAS-1487 > URL: https://issues.apache.org/jira/browse/ATLAS-1487 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-1487.patch > > > hdfs_path and fs_path have PosixPermissions as one of the (optional) > attributes which is of type fs_permissions (struct) . When creating entity > in UI , the types list (/api/atlas/v2/types/entitydef) doesn't return > fs_permissions hence no entity could be created for it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted
[
https://issues.apache.org/jira/browse/ATLAS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878413#comment-15878413
]
Nixon Rodrigues commented on ATLAS-1567:
The issue was occurring because hadoop-common jar being present in two
locations.
{noformat}
java.lang.LinkageError: loader constraint violation: when resolving method
"org.apache.falcon.security.CurrentUser.getAuthenticatedUGI()Lorg/apache/hadoop/security/UserGroupInformation;"
the class loader (instance of
org/apache/atlas/plugin/classloader/AtlasPluginClassLoader) of the current
class, org/apache/atlas/falcon/Util/EventUtil, and the class loader (instance
of sun/misc/Launcher$AppClassLoader) for the method's defining class,
org/apache/falcon/security/CurrentUser, have different Class objects for the
type org/apache/hadoop/security/UserGroupInformation used in the signature
at org.apache.atlas.falcon.Util.EventUtil.getUser(EventUtil.java:55)
at
org.apache.atlas.falcon.service.AtlasService.addEntity(AtlasService.java:127)
at
org.apache.atlas.falcon.service.AtlasService.onAdd(AtlasService.java:67)
at
org.apache.atlas.falcon.service.AtlasService.onAdd(AtlasService.java:120)
{noformat}
This I have removed hadoop-common jar from falcon hook packaging by changing
the falcon pom.xml.
Verified that hadoop-common jar is not packaged in
hook/falcon/atlas-falcon-plugin-impl/ distribution.
I have attached patch for it.
> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a
> falcon cluster entity is submitted
>
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1567.patch
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster,
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorizing user=hrt_qa against request=RequestParts{resource='entities',
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorization for action=submit will be done in the API
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> All locks released on
[jira] [Updated] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted
[
https://issues.apache.org/jira/browse/ATLAS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-1567:
---
Attachment: ATLAS-1567.patch
> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a
> falcon cluster entity is submitted
>
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1567.patch
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster,
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorizing user=hrt_qa against request=RequestParts{resource='entities',
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorization for action=submit will be done in the API
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> All locks released on cl1 (AbstractEntityManager:489)
> 2017-02-17 19:23:40,050 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> {Action:submit, Dimensions:{colo=NULL, entityType=cluster}, Status:
> SUCCEEDED, Time-taken:26995845 ns} (METRIC:38)
> 2017-02-17 19:23:40,051 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202
> performed
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
> (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:40,051 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202
> performed
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
> (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:51,101 WARN - [HiveClientCache-cleaner-0:] ~ Evicted client
> has non-zero user count: 1 (metastore:443)
> {noformat}
> Falcon running command - showing hook jars classpath
> {noformat}
> [root@ctr-e129-1487033772569-4286-01-04 conf]# ps axu | grep -i falcon
> falcon 66767 0.2 0.2 9242152 751692 ? Sl Feb16 4:00
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m
[jira] [Assigned] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted
[
https://issues.apache.org/jira/browse/ATLAS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues reassigned ATLAS-1567:
--
Assignee: Nixon Rodrigues
> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a
> falcon cluster entity is submitted
>
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster,
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorizing user=hrt_qa against request=RequestParts{resource='entities',
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorization for action=submit will be done in the API
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> All locks released on cl1 (AbstractEntityManager:489)
> 2017-02-17 19:23:40,050 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~
> {Action:submit, Dimensions:{colo=NULL, entityType=cluster}, Status:
> SUCCEEDED, Time-taken:26995845 ns} (METRIC:38)
> 2017-02-17 19:23:40,051 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202
> performed
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
> (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:40,051 INFO - [726486469@qtp-1828868503-10 -
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202
> performed
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
> (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:51,101 WARN - [HiveClientCache-cleaner-0:] ~ Evicted client
> has non-zero user count: 1 (metastore:443)
> {noformat}
> Falcon running command - showing hook jars classpath
> {noformat}
> [root@ctr-e129-1487033772569-4286-01-04 conf]# ps axu | grep -i falcon
> falcon 66767 0.2 0.2 9242152 751692 ? Sl Feb16 4:00
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -noverify
> -Dfalcon.embeddedmq=True
[jira] [Commented] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI
[
https://issues.apache.org/jira/browse/ATLAS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878187#comment-15878187
]
Nixon Rodrigues commented on ATLAS-1502:
Thanks Keval for review and commit.
Commit Id http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/dbfca622
> UI to create/update entities - configuration to restrict entity-types
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI
> allows an user to create entity of any entity-type - including the superTypes
> like Referenceable, Asset, Process, etc. It may not be useful to support
> entity creation of many such entity-types via UI. Restricting the UI to
> support only a subset of entities would make the UI more usable and avoid
> potential confusion.
> It should be possible to configure the list of entity-types supported via a
> configuration, to enable deployments to satisfy specific needs. I would
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow
> create/edit of any type of entity
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI
[
https://issues.apache.org/jira/browse/ATLAS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878014#comment-15878014
]
Nixon Rodrigues edited comment on ATLAS-1502 at 2/22/17 12:56 PM:
--
Sometimes there was issue in loading atlas application properties from
classpath using PropertiesConfiguration api, so changed this to use
org.apache.atlas.ApplicationProperties which internally wraps
PropertiesConfiguration which loads application properties from conf directory.
I have added this fix in ATLAS-1502-1.patch
was (Author: nixonrodrigues):
Sometimes there was issue in loading atlas application properties using
PropertiesConfiguration api, so changed this to use
org.apache.atlas.ApplicationProperties which internally wraps
PropertiesConfiguration which loads application properties from conf directory.
I have added this fix in ATLAS-1502-1.patch
> UI to create/update entities - configuration to restrict entity-types
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI
> allows an user to create entity of any entity-type - including the superTypes
> like Referenceable, Asset, Process, etc. It may not be useful to support
> entity creation of many such entity-types via UI. Restricting the UI to
> support only a subset of entities would make the UI more usable and avoid
> potential confusion.
> It should be possible to configure the list of entity-types supported via a
> configuration, to enable deployments to satisfy specific needs. I would
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow
> create/edit of any type of entity
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI
[
https://issues.apache.org/jira/browse/ATLAS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-1502:
---
Fix Version/s: 0.8-incubating
> UI to create/update entities - configuration to restrict entity-types
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI
> allows an user to create entity of any entity-type - including the superTypes
> like Referenceable, Asset, Process, etc. It may not be useful to support
> entity creation of many such entity-types via UI. Restricting the UI to
> support only a subset of entities would make the UI more usable and avoid
> potential confusion.
> It should be possible to configure the list of entity-types supported via a
> configuration, to enable deployments to satisfy specific needs. I would
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow
> create/edit of any type of entity
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI
[
https://issues.apache.org/jira/browse/ATLAS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-1502:
---
Attachment: ATLAS-1502-1.patch
Sometimes there was issue in loading atlas application properties using
PropertiesConfiguration api, so changed this to use
org.apache.atlas.ApplicationProperties which internally wraps
PropertiesConfiguration which loads application properties from conf directory.
I have added this fix in ATLAS-1502-1.patch
> UI to create/update entities - configuration to restrict entity-types
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI
> allows an user to create entity of any entity-type - including the superTypes
> like Referenceable, Asset, Process, etc. It may not be useful to support
> entity creation of many such entity-types via UI. Restricting the UI to
> support only a subset of entities would make the UI more usable and avoid
> potential confusion.
> It should be possible to configure the list of entity-types supported via a
> configuration, to enable deployments to satisfy specific needs. I would
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow
> create/edit of any type of entity
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[ https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1546: --- Attachment: ATLAS-1546.4.patch Changed to LOG.warn instead LOG.error in isLoginKeytabBased & isLoginTicketBased method in ATLAS-1546.4.patch > Hive hook should choose appropriate JAAS config if host uses kerberos > ticket-cache > -- > > Key: ATLAS-1546 > URL: https://issues.apache.org/jira/browse/ATLAS-1546 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > Fix For: 0.8-incubating > > Attachments: ATLAS-1546.1.patch, ATLAS-1546.2.patch, > ATLAS-1546.3.patch, ATLAS-1546.4.patch, ATLAS-1546.patch, hiveenviro, > hiveserver2_log.txt, hiveserver2-site.xml, hive-site.xml, hs2.log.gz > > > In a kerberized environment, Atlas hook uses JAAS configuration section named > "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment > this configuration section is set to use the keytab and principal of > HiveServer2 process. The hook running in HiveCLI might fail to authenticate > with Kafka if the user can't read the configured keytab. > Given that HiveCLI users would have performed kinit, the hook in HiveCLI > should use the ticket-cache generated by kinit. When ticket cache is not > available (for example in HiveServer2), the hook should use the configuration > provided in KafkaClient JAAS section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[ https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869781#comment-15869781 ] Nixon Rodrigues commented on ATLAS-1546: Thanks [~kevalbhatt] for commit. Commit Id : http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/20fb5894 > Hive hook should choose appropriate JAAS config if host uses kerberos > ticket-cache > -- > > Key: ATLAS-1546 > URL: https://issues.apache.org/jira/browse/ATLAS-1546 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > Fix For: 0.8-incubating > > Attachments: ATLAS-1546.1.patch, ATLAS-1546.2.patch, > ATLAS-1546.3.patch, ATLAS-1546.patch, hiveenviro, hiveserver2_log.txt, > hiveserver2-site.xml, hive-site.xml, hs2.log.gz > > > In a kerberized environment, Atlas hook uses JAAS configuration section named > "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment > this configuration section is set to use the keytab and principal of > HiveServer2 process. The hook running in HiveCLI might fail to authenticate > with Kafka if the user can't read the configured keytab. > Given that HiveCLI users would have performed kinit, the hook in HiveCLI > should use the ticket-cache generated by kinit. When ticket cache is not > available (for example in HiveServer2), the hook should use the configuration > provided in KafkaClient JAAS section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[ https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1546: --- Attachment: ATLAS-1546.3.patch Fixed CheckStyle Error for AtlasHook & InMemoryJAASConfiguration classes. > Hive hook should choose appropriate JAAS config if host uses kerberos > ticket-cache > -- > > Key: ATLAS-1546 > URL: https://issues.apache.org/jira/browse/ATLAS-1546 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > Fix For: 0.8-incubating > > Attachments: ATLAS-1546.1.patch, ATLAS-1546.2.patch, > ATLAS-1546.3.patch, ATLAS-1546.patch, hiveenviro, hiveserver2_log.txt, > hiveserver2-site.xml, hive-site.xml, hs2.log.gz > > > In a kerberized environment, Atlas hook uses JAAS configuration section named > "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment > this configuration section is set to use the keytab and principal of > HiveServer2 process. The hook running in HiveCLI might fail to authenticate > with Kafka if the user can't read the configured keytab. > Given that HiveCLI users would have performed kinit, the hook in HiveCLI > should use the ticket-cache generated by kinit. When ticket cache is not > available (for example in HiveServer2), the hook should use the configuration > provided in KafkaClient JAAS section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1556) Edit entity button not working from search table of tag detail page.
[ https://issues.apache.org/jira/browse/ATLAS-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867747#comment-15867747 ] Nixon Rodrigues commented on ATLAS-1556: The patch applies well & build is fine.The edit button for entities on search result page looks good. +1 for the patch. > Edit entity button not working from search table of tag detail page. > > > Key: ATLAS-1556 > URL: https://issues.apache.org/jira/browse/ATLAS-1556 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1556.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1559) Regression - If a new tag is created then the earlier tags doesn't render properly
[ https://issues.apache.org/jira/browse/ATLAS-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867709#comment-15867709 ] Nixon Rodrigues commented on ATLAS-1559: +1 for the patch > Regression - If a new tag is created then the earlier tags doesn't render > properly > --- > > Key: ATLAS-1559 > URL: https://issues.apache.org/jira/browse/ATLAS-1559 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1559.1.patch, ATLAS-1559.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[
https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863835#comment-15863835
]
Nixon Rodrigues commented on ATLAS-1546:
[~gss2002], [~madhan.neethiraj],
After deleting kerberos ticket from hive user, i started getting this exception
for hiveServer2, isLoginTicketBased flag is coming true for hiveServer2 case.I
m looking into this.
{noformat}
Caused by: org.apache.kafka.common.KafkaException:
javax.security.auth.login.LoginException: Could not login: the client is being
asked for a password, but the Kafka client code does not currently support
obtaining a password from the user. not available to garner authentication
information from the user
at
org.apache.kafka.common.network.SaslChannelBuilder.configure(SaslChannelBuilder.java:86)
at
org.apache.kafka.common.network.ChannelBuilders.create(ChannelBuilders.java:71)
at
org.apache.kafka.clients.ClientUtils.createChannelBuilder(ClientUtils.java:83)
at
org.apache.kafka.clients.producer.KafkaProducer.(KafkaProducer.java:277)
... 19 more
Caused by: javax.security.auth.login.LoginException: Could not login: the
client is being asked for a password, but the Kafka client code does not
currently support obtaining a password from the user. not available to garner
authentication information from the user
{noformat}
> Hive hook should choose appropriate JAAS config if host uses kerberos
> ticket-cache
> --
>
> Key: ATLAS-1546
> URL: https://issues.apache.org/jira/browse/ATLAS-1546
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-intg
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1546.1.patch, ATLAS-1546.patch, hiveenviro,
> hiveserver2_log.txt, hs2.log.gz
>
>
> In a kerberized environment, Atlas hook uses JAAS configuration section named
> "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment
> this configuration section is set to use the keytab and principal of
> HiveServer2 process. The hook running in HiveCLI might fail to authenticate
> with Kafka if the user can't read the configured keytab.
> Given that HiveCLI users would have performed kinit, the hook in HiveCLI
> should use the ticket-cache generated by kinit. When ticket cache is not
> available (for example in HiveServer2), the hook should use the configuration
> provided in KafkaClient JAAS section.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[ https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863318#comment-15863318 ] Nixon Rodrigues commented on ATLAS-1546: [~gss2002],[~madhan.neethiraj], I tried running HiveServer2 (Run as end user instead of Hive user) with doAs = true and tables are created in hive and entities are getting created Atlas end. Also tested HiveCli and it is also working fine and entities are getting created Atlas end. > Hive hook should choose appropriate JAAS config if host uses kerberos > ticket-cache > -- > > Key: ATLAS-1546 > URL: https://issues.apache.org/jira/browse/ATLAS-1546 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > Fix For: 0.8-incubating > > Attachments: ATLAS-1546.1.patch, ATLAS-1546.patch, hiveenviro, > hiveserver2_log.txt, hs2.log.gz > > > In a kerberized environment, Atlas hook uses JAAS configuration section named > "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment > this configuration section is set to use the keytab and principal of > HiveServer2 process. The hook running in HiveCLI might fail to authenticate > with Kafka if the user can't read the configured keytab. > Given that HiveCLI users would have performed kinit, the hook in HiveCLI > should use the ticket-cache generated by kinit. When ticket cache is not > available (for example in HiveServer2), the hook should use the configuration > provided in KafkaClient JAAS section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[
https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863318#comment-15863318
]
Nixon Rodrigues edited comment on ATLAS-1546 at 2/13/17 8:36 AM:
-
[~gss2002],[~madhan.neethiraj],
I tried running HiveServer2 (Run as end user instead of Hive user) with doAs =
true and tables are created in hive and entities are getting created Atlas end.
Also tested HiveCli and it is also working fine and entities are getting
created Atlas end.
Tested this with hive_test user, this user was created with below steps
{noformat}
useradd hive_test
hadoop fs -mkdir /user/hive_test
hadoop fs -chown hive_test /user/hive_test
{noformat}
and principal hive_test, created with below steps
{noformat}
kadmin.local
addprinc hive_test/hive_test/dom...@example.com
kinit hive_test/dom...@example.com
{noformat}
was (Author: nixonrodrigues):
[~gss2002],[~madhan.neethiraj],
I tried running HiveServer2 (Run as end user instead of Hive user) with doAs =
true and tables are created in hive and entities are getting created Atlas end.
Also tested HiveCli and it is also working fine and entities are getting
created Atlas end.
> Hive hook should choose appropriate JAAS config if host uses kerberos
> ticket-cache
> --
>
> Key: ATLAS-1546
> URL: https://issues.apache.org/jira/browse/ATLAS-1546
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-intg
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1546.1.patch, ATLAS-1546.patch, hiveenviro,
> hiveserver2_log.txt, hs2.log.gz
>
>
> In a kerberized environment, Atlas hook uses JAAS configuration section named
> "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment
> this configuration section is set to use the keytab and principal of
> HiveServer2 process. The hook running in HiveCLI might fail to authenticate
> with Kafka if the user can't read the configured keytab.
> Given that HiveCLI users would have performed kinit, the hook in HiveCLI
> should use the ticket-cache generated by kinit. When ticket cache is not
> available (for example in HiveServer2), the hook should use the configuration
> provided in KafkaClient JAAS section.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[
https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863318#comment-15863318
]
Nixon Rodrigues edited comment on ATLAS-1546 at 2/13/17 8:39 AM:
-
[~gss2002],[~madhan.neethiraj],
I tried running HiveServer2 (Run as end user instead of Hive user) with doAs =
true and tables are created in hive and entities are getting created Atlas end.
Also tested HiveCli and it is also working fine and entities are getting
created Atlas end.
Tested this with *hive_test* user, this user was created with below steps
{noformat}
useradd hive_test
hadoop fs -mkdir /user/hive_test
hadoop fs -chown hive_test /user/hive_test
{noformat}
and principal *hive_test*, created with below steps
{noformat}
kadmin.local
addprinc hive_test/dom...@example.com
exit and then kinit
kinit hive_test/dom...@example.com
{noformat}
was (Author: nixonrodrigues):
[~gss2002],[~madhan.neethiraj],
I tried running HiveServer2 (Run as end user instead of Hive user) with doAs =
true and tables are created in hive and entities are getting created Atlas end.
Also tested HiveCli and it is also working fine and entities are getting
created Atlas end.
Tested this with hive_test user, this user was created with below steps
{noformat}
useradd hive_test
hadoop fs -mkdir /user/hive_test
hadoop fs -chown hive_test /user/hive_test
{noformat}
and principal hive_test, created with below steps
{noformat}
kadmin.local
addprinc hive_test/hive_test/dom...@example.com
kinit hive_test/dom...@example.com
{noformat}
> Hive hook should choose appropriate JAAS config if host uses kerberos
> ticket-cache
> --
>
> Key: ATLAS-1546
> URL: https://issues.apache.org/jira/browse/ATLAS-1546
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-intg
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1546.1.patch, ATLAS-1546.patch, hiveenviro,
> hiveserver2_log.txt, hs2.log.gz
>
>
> In a kerberized environment, Atlas hook uses JAAS configuration section named
> "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment
> this configuration section is set to use the keytab and principal of
> HiveServer2 process. The hook running in HiveCLI might fail to authenticate
> with Kafka if the user can't read the configured keytab.
> Given that HiveCLI users would have performed kinit, the hook in HiveCLI
> should use the ticket-cache generated by kinit. When ticket cache is not
> available (for example in HiveServer2), the hook should use the configuration
> provided in KafkaClient JAAS section.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[
https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863318#comment-15863318
]
Nixon Rodrigues edited comment on ATLAS-1546 at 2/13/17 9:02 AM:
-
[~gss2002],[~madhan.neethiraj],
I tried running HiveServer2 (Run as end user instead of Hive user) with doAs =
true and tables are created in hive and entities are getting created at Atlas
end.
Also tested HiveCli with doAs = true and it is also working fine and entities
are getting created at Atlas end.
Tested this with *hive_test* user, this user was created with below steps
{noformat}
useradd hive_test
hadoop fs -mkdir /user/hive_test
hadoop fs -chown hive_test /user/hive_test
{noformat}
and principal *hive_test*, created with below steps
{noformat}
kadmin.local
addprinc hive_test/dom...@example.com
exit and then kinit
kinit hive_test/dom...@example.com
{noformat}
was (Author: nixonrodrigues):
[~gss2002],[~madhan.neethiraj],
I tried running HiveServer2 (Run as end user instead of Hive user) with doAs =
true and tables are created in hive and entities are getting created Atlas end.
Also tested HiveCli and it is also working fine and entities are getting
created Atlas end.
Tested this with *hive_test* user, this user was created with below steps
{noformat}
useradd hive_test
hadoop fs -mkdir /user/hive_test
hadoop fs -chown hive_test /user/hive_test
{noformat}
and principal *hive_test*, created with below steps
{noformat}
kadmin.local
addprinc hive_test/dom...@example.com
exit and then kinit
kinit hive_test/dom...@example.com
{noformat}
> Hive hook should choose appropriate JAAS config if host uses kerberos
> ticket-cache
> --
>
> Key: ATLAS-1546
> URL: https://issues.apache.org/jira/browse/ATLAS-1546
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-intg
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1546.1.patch, ATLAS-1546.patch, hiveenviro,
> hiveserver2_log.txt, hs2.log.gz
>
>
> In a kerberized environment, Atlas hook uses JAAS configuration section named
> "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment
> this configuration section is set to use the keytab and principal of
> HiveServer2 process. The hook running in HiveCLI might fail to authenticate
> with Kafka if the user can't read the configured keytab.
> Given that HiveCLI users would have performed kinit, the hook in HiveCLI
> should use the ticket-cache generated by kinit. When ticket cache is not
> available (for example in HiveServer2), the hook should use the configuration
> provided in KafkaClient JAAS section.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[ https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1546: --- Attachment: ATLAS-1546.patch > Hive hook should choose appropriate JAAS config if host uses kerberos > ticket-cache > -- > > Key: ATLAS-1546 > URL: https://issues.apache.org/jira/browse/ATLAS-1546 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > Attachments: ATLAS-1546.patch > > > In a kerberized environment, Atlas hook uses JAAS configuration section named > "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment > this configuration section is set to use the keytab and principal of > HiveServer2 process. The hook running in HiveCLI might fail to authenticate > with Kafka if the user can't read the configured keytab. > Given that HiveCLI users would have performed kinit, the hook in HiveCLI > should use the ticket-cache generated by kinit. When ticket cache is not > available (for example in HiveServer2), the hook should use the configuration > provided in KafkaClient JAAS section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
[ https://issues.apache.org/jira/browse/ATLAS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-1546: -- Assignee: Nixon Rodrigues > Hive hook should choose appropriate JAAS config if host uses kerberos > ticket-cache > -- > > Key: ATLAS-1546 > URL: https://issues.apache.org/jira/browse/ATLAS-1546 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > > In a kerberized environment, Atlas hook uses JAAS configuration section named > "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment > this configuration section is set to use the keytab and principal of > HiveServer2 process. The hook running in HiveCLI might fail to authenticate > with Kafka if the user can't read the configured keytab. > Given that HiveCLI users would have performed kinit, the hook in HiveCLI > should use the ticket-cache generated by kinit. When ticket cache is not > available (for example in HiveServer2), the hook should use the configuration > provided in KafkaClient JAAS section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1538) Make AtlasLdapAuthenticationProvider like Ranger for OpenLdap type
[ https://issues.apache.org/jira/browse/ATLAS-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1538: --- Attachment: ATLAS-1538.patch > Make AtlasLdapAuthenticationProvider like Ranger for OpenLdap type > -- > > Key: ATLAS-1538 > URL: https://issues.apache.org/jira/browse/ATLAS-1538 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.7-incubating, 0.7.1-incubating >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-1538.patch > > > Currently in Altas , AtlasLdapAuthenticationProvider has > getLdapBindAuthentication method which used for openldap authentication. > Adding new method getLdapAuthentication as a fallback to take care of > failures in login. > I propose AtlasLdapAuthenticationProvider to be like Ranger -- This message was sent by Atlassian JIRA (v6.3.15#6346)
