[jira] [Commented] (ATLAS-1997) Search indexer NPE
[ https://issues.apache.org/jira/browse/ATLAS-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112027#comment-16112027 ] Madhan Neethiraj commented on ATLAS-1997: - +1 for the patch. > Search indexer NPE > -- > > Key: ATLAS-1997 > URL: https://issues.apache.org/jira/browse/ATLAS-1997 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating > > Attachments: > 0001-ATLAS-1997-Search-Indexer-NPE-on-the-vertex_index.patch > > > Getting the vertex index from the graph management system sometimes runs into > an NPE if the graph hasn't been completely initialized. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1944) NotificationHookConsumer throws exception while shutting down the consumer thread
[
https://issues.apache.org/jira/browse/ATLAS-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-1944.
-
Resolution: Fixed
Committed [~nixonrodrigues]'s patch to the following branches:
- master: http://git-wip-us.apache.org/repos/asf/atlas/commit/0267eecd
- 0.8-incubating: http://git-wip-us.apache.org/repos/asf/atlas/commit/49c62b85
> NotificationHookConsumer throws exception while shutting down the consumer
> thread
> -
>
> Key: ATLAS-1944
> URL: https://issues.apache.org/jira/browse/ATLAS-1944
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Ashutosh Mestry
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1944.1.patch, ATLAS-1944.patch
>
>
> NotificationHookConsumer throws below exception while shutting down the
> consumer thread, this issue is possibly after this commit.
> https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62
> CC [~nixonrodrigues]
> {noformat}
> 2017-07-12 01:26:09,743 WARN - [pool-1-thread-1:] ~ Error stopping service
> org.apache.atlas.notification.NotificationHookConsumer (Services:69)
> java.util.ConcurrentModificationException: KafkaConsumer is not safe for
> multi-threaded access
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquire(KafkaConsumer.java:1557)
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.close(KafkaConsumer.java:1467)
> at
> org.apache.atlas.kafka.AtlasKafkaConsumer.close(AtlasKafkaConsumer.java:88)
> at
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.stop(NotificationHookConsumer.java:384)
> at
> org.apache.atlas.notification.NotificationHookConsumer.stopConsumerThreads(NotificationHookConsumer.java:172)
> at
> org.apache.atlas.notification.NotificationHookConsumer.stop(NotificationHookConsumer.java:155)
> at org.apache.atlas.service.Services.stop(Services.java:67)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:366)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeDestroyMethods(InitDestroyAnnotationBeanPostProcessor.java:325)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeDestruction(InitDestroyAnnotationBeanPostProcessor.java:154)
> at
> org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:253)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:961)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:968)
> at
> org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1033)
> at
> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1009)
> at
> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:961)
> at
> org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:583)
> at
> org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:116)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:808)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:457)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:842)
> at
>
[jira] [Commented] (ATLAS-1981) Cache escaped type-query string to avoid repeated computation
[ https://issues.apache.org/jira/browse/ATLAS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112870#comment-16112870 ] Madhan Neethiraj commented on ATLAS-1981: - [~yussufshaikh] - this issue was addressed in following commits. Can you verify if you have the latest sources? - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/7fb09b0f - 0.8-incubating: http://git-wip-us.apache.org/repos/asf/atlas/commit/8264b2a6 > Cache escaped type-query string to avoid repeated computation > - > > Key: ATLAS-1981 > URL: https://issues.apache.org/jira/browse/ATLAS-1981 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1981.patch > > > Before sending the type-names to index-query, current search implementation > escape the type-names to handle presence of special characters. Avoiding this > repeated computation can help improve search performance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1981) Cache escaped type-query string to avoid repeated computation
[ https://issues.apache.org/jira/browse/ATLAS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113951#comment-16113951 ] Madhan Neethiraj commented on ATLAS-1981: - [~yussufshaikh] - now that Atlas has graduated to a top-level project, the git repo to use is: https://github.com/apache/atlas (note the missing 'incubator-' prefix). The fix is present in https://github.com/apache/atlas/blob/master/intg/src/main/java/org/apache/atlas/type/AtlasStructType.java. > Cache escaped type-query string to avoid repeated computation > - > > Key: ATLAS-1981 > URL: https://issues.apache.org/jira/browse/ATLAS-1981 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1981.patch > > > Before sending the type-names to index-query, current search implementation > escape the type-names to handle presence of special characters. Avoiding this > repeated computation can help improve search performance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2052) remove junit library from atlas.war
[ https://issues.apache.org/jira/browse/ATLAS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2052: Attachment: ATLAS-2052.patch > remove junit library from atlas.war > --- > > Key: ATLAS-2052 > URL: https://issues.apache.org/jira/browse/ATLAS-2052 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Attachments: ATLAS-2052.patch > > > atlas.war generated by the build includes junit.jar file under WEB-INF/lib > directory. Packaging should be updated to exclude libraries such as junit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1902) UI: Allow user to add more columns in search table
[ https://issues.apache.org/jira/browse/ATLAS-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083777#comment-16083777 ] Madhan Neethiraj commented on ATLAS-1902: - +1 for the patch. Thanks [~kevalbhatt]. > UI: Allow user to add more columns in search table > -- > > Key: ATLAS-1902 > URL: https://issues.apache.org/jira/browse/ATLAS-1902 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1902.1.patch > > > In basic search after searching for a type, user can add more columns based > on type selected -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1944) NotificationHookConsumer throws exception while shutting down the consumer thread
[
https://issues.apache.org/jira/browse/ATLAS-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-1944.
-
Resolution: Fixed
Fix Version/s: 0.8.1-incubating
Committed to the following branches:
- master:
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/18745cf4
- 0.8-incubating:
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/9b63509d
> NotificationHookConsumer throws exception while shutting down the consumer
> thread
> -
>
> Key: ATLAS-1944
> URL: https://issues.apache.org/jira/browse/ATLAS-1944
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Ashutosh Mestry
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1944.patch
>
>
> NotificationHookConsumer throws below exception while shutting down the
> consumer thread, this issue is possibly after this commit.
> https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62
> CC [~nixonrodrigues]
> {noformat}
> 2017-07-12 01:26:09,743 WARN - [pool-1-thread-1:] ~ Error stopping service
> org.apache.atlas.notification.NotificationHookConsumer (Services:69)
> java.util.ConcurrentModificationException: KafkaConsumer is not safe for
> multi-threaded access
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquire(KafkaConsumer.java:1557)
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.close(KafkaConsumer.java:1467)
> at
> org.apache.atlas.kafka.AtlasKafkaConsumer.close(AtlasKafkaConsumer.java:88)
> at
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.stop(NotificationHookConsumer.java:384)
> at
> org.apache.atlas.notification.NotificationHookConsumer.stopConsumerThreads(NotificationHookConsumer.java:172)
> at
> org.apache.atlas.notification.NotificationHookConsumer.stop(NotificationHookConsumer.java:155)
> at org.apache.atlas.service.Services.stop(Services.java:67)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:366)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeDestroyMethods(InitDestroyAnnotationBeanPostProcessor.java:325)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeDestruction(InitDestroyAnnotationBeanPostProcessor.java:154)
> at
> org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:253)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:961)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:968)
> at
> org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1033)
> at
> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1009)
> at
> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:961)
> at
> org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:583)
> at
> org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:116)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:808)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:457)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:842)
> at
>
[jira] [Resolved] (ATLAS-1733) No SIGKILL in python signal library on Windows
[ https://issues.apache.org/jira/browse/ATLAS-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-1733. - Resolution: Fixed Fix Version/s: 0.8.1-incubating 0.9-incubating Thanks [~grahamwallis] for the fix; [~davidrad] for reviewing the patch. Committed to the following branches: - master: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/ad398393 - 0.8-incubating: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/13d5bfbf > No SIGKILL in python signal library on Windows > -- > > Key: ATLAS-1733 > URL: https://issues.apache.org/jira/browse/ATLAS-1733 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating > Environment: Windows 7 >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1733.patch, ATLAS-1733.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > [I am new to Atlas and this is my first JIRA issue so apologies if I have > omitted any necessary information or steps.] > There is no SIGKILL signal in the python signal library on Windows, so the > import in atlas_stop.py fails. > There are two ways I can suggest that we fix it: > 1) introduce platform-specific code into atlas_stop.py > 2) wrap the python os.kill function > My preference is for the former as it is a small and localized change. > In either case the use of SIGTERM should be sufficient on Windows, as the > existing python os.kill() function will open the process and terminate it, > which is supposed to be equivalent to a SIGKILL (-9) on Linux. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1961) Basic search improvement in use of Solr index for attribute filtering
[ https://issues.apache.org/jira/browse/ATLAS-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1961: Attachment: ATLAS-1961.patch Review board URL: https://reviews.apache.org/r/60940/ > Basic search improvement in use of Solr index for attribute filtering > - > > Key: ATLAS-1961 > URL: https://issues.apache.org/jira/browse/ATLAS-1961 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1961.patch > > > Current basic search implementation uses Solr only when both type and > attribute filters can be done via Solr. When the type specified has too many > subtypes, Solr is not used - even though Solr could be used for attribute > filtering. Use of Solr for attribute filtering can be help quicker response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1965) UI update to allow browsing of tables in the db
Madhan Neethiraj created ATLAS-1965: --- Summary: UI update to allow browsing of tables in the db Key: ATLAS-1965 URL: https://issues.apache.org/jira/browse/ATLAS-1965 Project: Atlas Issue Type: Improvement Components: atlas-core, atlas-webui Reporter: Madhan Neethiraj One of the often asked improvement in Atlas UI is the ability to browse through tables in a Hive DB. Currently it is possible to list the tables in a DB using a DSL query. However, the feedback from many users is that DSL syntax is difficult to use for business users and it will make it a lot easier if tables list can be browsed in hive_db details page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1969) Cannot create a second child relationship
[ https://issues.apache.org/jira/browse/ATLAS-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094809#comment-16094809 ] Madhan Neethiraj commented on ATLAS-1969: - [~davidrad] - can you please add JSONs for the entities and relationship creation? > Cannot create a second child relationship > - > > Key: ATLAS-1969 > URL: https://issues.apache.org/jira/browse/ATLAS-1969 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > Attachments: 0005LinkedMediaTypes.json, 0210Glossary.json, > 0220CategoryHierarchy.json > > > On the latest code I create 3 GlossaryCategories CatA CatB and CatC. I can > successfully create a relationship with type CategoryHierarchyLink with CatA > as the parent and CatB as the child.. I then try to try to create a > relationship with type CategoryHierarchyLink with catA as the parent and CatC > as the child; and it fails with > 2017-07-20 12:14:51,188 ERROR - [pool-1-thread-7 - > 7d5fbe39-0e26-4af0-9137-651b51f9a69c:] ~ graph rollback due to exception > (GraphTransactionInterceptor:71) > org.apache.atlas.exception.AtlasBaseException: invalid parameters: found null > entity > at > org.apache.atlas.repository.store.graph.v1.AtlasEntityGraphDiscoveryV1.discover(AtlasEntityGraphDiscoveryV1.java:139) > at > org.apache.atlas.repository.store.graph.v1.AtlasEntityGraphDiscoveryV1.discoverEntities(AtlasEntityGraphDiscoveryV1.java:69) > at > org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.preCreateOrUpdate(AtlasEntityStoreV1.java:612) > at org -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1982) Update referenced to "incubator" in website
Madhan Neethiraj created ATLAS-1982: --- Summary: Update referenced to "incubator" in website Key: ATLAS-1982 URL: https://issues.apache.org/jira/browse/ATLAS-1982 Project: Atlas Issue Type: Task Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Now that Atlas has graduated to a top-level project, update website to remove incubator related references (git repo, emails, URLs). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2000) Deprecate REST API - search/gremlin
Madhan Neethiraj created ATLAS-2000: --- Summary: Deprecate REST API - search/gremlin Key: ATLAS-2000 URL: https://issues.apache.org/jira/browse/ATLAS-2000 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Madhan Neethiraj REST API at api/atlas/discovery/search/gremlin allows execution of Gremlin queries, which requires the users to know a lot of implementation level details (like how entity instances/relationships are mapped to vertices & edges..). While this could be useful, such usage is bound to break when the implementation details change over versions. Applications instead should only use higher-level public APIs (available at api/atlas/v2/entity, api/atlas/v2/search, api/atlas/v2/lineage, api/atlas/v2/types). This JIRA is track deprecation of the API at api/atlas/discovery/search/gremlin. Given that execution of Grelim queries could leave the store in inconsistent state, I would suggest to disable this API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1988) Implement REST API to search for related entities
[ https://issues.apache.org/jira/browse/ATLAS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1988: Attachment: ATLAS-1988.2.patch > Implement REST API to search for related entities > -- > > Key: ATLAS-1988 > URL: https://issues.apache.org/jira/browse/ATLAS-1988 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core, atlas-intg >Affects Versions: 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Fix For: 0.8.1-incubating > > Attachments: ATLAS-1988.1.patch, ATLAS-1988.2.patch > > > Add a new endpoint (v2/search/relationship) in DiscoveryREST to search for > related entities. > Parameters: > * guid > * relation > * sortBy > * sortOrder > * limit > * offset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1988) Implement REST API to search for related entities
[ https://issues.apache.org/jira/browse/ATLAS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1988: Description: Add a new endpoint (v2/search/relationship) in DiscoveryREST to search for related entities. Parameters: * guid * relation * sortBy * sortOrder * limit * offset was: Add a new endpoint (v2/search/relationship) in DiscoveryREST to search for related entities. Parameters: * guid * attributeLabel * sortBy * 'limit * offset > Implement REST API to search for related entities > -- > > Key: ATLAS-1988 > URL: https://issues.apache.org/jira/browse/ATLAS-1988 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core, atlas-intg >Affects Versions: 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Fix For: 0.8.1-incubating > > Attachments: ATLAS-1988.1.patch, ATLAS-1988.2.patch > > > Add a new endpoint (v2/search/relationship) in DiscoveryREST to search for > related entities. > Parameters: > * guid > * relation > * sortBy > * sortOrder > * limit > * offset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1988) Implement REST API to search for related entities
[ https://issues.apache.org/jira/browse/ATLAS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101284#comment-16101284 ] Madhan Neethiraj commented on ATLAS-1988: - Sample URLs: - Get list of hive_table entities in the given hive_db guid: api/atlas/v2/search/relationship?guid=d00fcba2-9228-4e6e-886f-cf9d22698377=__hive_table.db - Get list of hive_column entities in the given hive_table guid: api/atlas/v2/search/relationship?guid=892c3e01-476f-4f5a-9733-e3a99a13cf2d=__hive_table.columns - Get the hive_table entity given guid of hive_column: api/atlas/v2/search/relationship?guid=3d7f82a6-9638-409d-838d-9bb122e9dd73=table > Implement REST API to search for related entities > -- > > Key: ATLAS-1988 > URL: https://issues.apache.org/jira/browse/ATLAS-1988 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core, atlas-intg >Affects Versions: 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Fix For: 0.8.1-incubating > > Attachments: ATLAS-1988.1.patch, ATLAS-1988.2.patch > > > Add a new endpoint (v2/search/relationship) in DiscoveryREST to search for > related entities. > Parameters: > * guid > * relation > * sortBy > * sortOrder > * limit > * offset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1981) Cache escaped type-query string to avoid repeated computation
Madhan Neethiraj created ATLAS-1981: --- Summary: Cache escaped type-query string to avoid repeated computation Key: ATLAS-1981 URL: https://issues.apache.org/jira/browse/ATLAS-1981 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Before sending the type-names to index-query, current search implementation escape the type-names to handle presence of special characters. Avoiding this repeated computation can help improve search performance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2008) basic-search: numeric tag-attribute filtering fails with java.lang.ClassCastException
Madhan Neethiraj created ATLAS-2008:
---
Summary: basic-search: numeric tag-attribute filtering fails with
java.lang.ClassCastException
Key: ATLAS-2008
URL: https://issues.apache.org/jira/browse/ATLAS-2008
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
When tag-attribute filter includes attributes of numeric types (int, double,
float), Gremlin queries fail due to ClassCastException:
{noformat}
2017-07-29 07:58:15,868 DEBUG - [pool-1-thread-9 -
e81686ab-44b5-403a-94e2-cf2a342806c6:] ~
gremlinTagFilterQuery=g.V().has('__guid', T.in, guids).has('__traitNames',
T.in, traitNames).as('e').out().has('__typeName', T.in,
typeNames).has('tag4.attr4-double', T.gte, 6).back('e').toList()
(ClassificationSearchProcessor:119)
...
2017-07-29 07:58:16,189 WARN - [pool-1-thread-9 -
e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ javax.script.ScriptException:
java.lang.ClassCastException: java.lang.Integer cannot be cast to
java.lang.Double (ClassificationSearchProcessor:260)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2008) basic-search: numeric tag-attribute filtering fails with java.lang.ClassCastException
[
https://issues.apache.org/jira/browse/ATLAS-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106599#comment-16106599
]
Madhan Neethiraj commented on ATLAS-2008:
-
Gremlin seems to parse integer numbers to java.lang.Integer; and float/double
to java.math.BigDecimal. This results in failure in filter expressions for
attributes of type Double, Long, Short. Use of bind-variables can help address
this issue.
> basic-search: numeric tag-attribute filtering fails with
> java.lang.ClassCastException
> -
>
> Key: ATLAS-2008
> URL: https://issues.apache.org/jira/browse/ATLAS-2008
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>
> When tag-attribute filter includes attributes of numeric types (int, double,
> float), Gremlin queries fail due to ClassCastException:
> {noformat}
> 2017-07-29 07:58:15,868 DEBUG - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~
> gremlinTagFilterQuery=g.V().has('__guid', T.in, guids).has('__traitNames',
> T.in, traitNames).as('e').out().has('__typeName', T.in,
> typeNames).has('tag4.attr4-double', T.gte, 6).back('e').toList()
> (ClassificationSearchProcessor:119)
> ...
> 2017-07-29 07:58:16,189 WARN - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ javax.script.ScriptException:
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.Double (ClassificationSearchProcessor:260)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2008) basic-search: numeric tag-attribute filtering fails with java.lang.ClassCastException
[
https://issues.apache.org/jira/browse/ATLAS-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2008:
Attachment: ATLAS-2008.patch
Review board URL: https://reviews.apache.org/r/61246/
> basic-search: numeric tag-attribute filtering fails with
> java.lang.ClassCastException
> -
>
> Key: ATLAS-2008
> URL: https://issues.apache.org/jira/browse/ATLAS-2008
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Attachments: ATLAS-2008.patch
>
>
> When tag-attribute filter includes attributes of numeric types (int, double,
> float), Gremlin queries fail due to ClassCastException:
> {noformat}
> 2017-07-29 07:58:15,868 DEBUG - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~
> gremlinTagFilterQuery=g.V().has('__guid', T.in, guids).has('__traitNames',
> T.in, traitNames).as('e').out().has('__typeName', T.in,
> typeNames).has('tag4.attr4-double', T.gte, 6).back('e').toList()
> (ClassificationSearchProcessor:119)
> ...
> 2017-07-29 07:58:16,189 WARN - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ javax.script.ScriptException:
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.Double (ClassificationSearchProcessor:260)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2008) basic-search: numeric tag-attribute filtering fails with java.lang.ClassCastException
[
https://issues.apache.org/jira/browse/ATLAS-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2008:
Affects Version/s: 0.8.1-incubating
0.9-incubating
> basic-search: numeric tag-attribute filtering fails with
> java.lang.ClassCastException
> -
>
> Key: ATLAS-2008
> URL: https://issues.apache.org/jira/browse/ATLAS-2008
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2008.patch
>
>
> When tag-attribute filter includes attributes of numeric types (int, double,
> float), Gremlin queries fail due to ClassCastException:
> {noformat}
> 2017-07-29 07:58:15,868 DEBUG - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~
> gremlinTagFilterQuery=g.V().has('__guid', T.in, guids).has('__traitNames',
> T.in, traitNames).as('e').out().has('__typeName', T.in,
> typeNames).has('tag4.attr4-double', T.gte, 6).back('e').toList()
> (ClassificationSearchProcessor:119)
> ...
> 2017-07-29 07:58:16,189 WARN - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ javax.script.ScriptException:
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.Double (ClassificationSearchProcessor:260)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2033) AbstractNotification Message Serializer Uses Pretty JSON
[ https://issues.apache.org/jira/browse/ATLAS-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119481#comment-16119481 ] Madhan Neethiraj commented on ATLAS-2033: - Good find [~ashutoshm]! +1 for the patch. > AbstractNotification Message Serializer Uses Pretty JSON > > > Key: ATLAS-2033 > URL: https://issues.apache.org/jira/browse/ATLAS-2033 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk, 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Minor > Fix For: trunk > > Attachments: ATLAS-2033.patch > > > _InstanceSerialization.scala_ uses _writePretty_ instead of _write_. This > causes prettified JSON to be generated. > Pretty JSON is about 30% larger than ugly JSON. > This change will help in dealing Kafa's message threshold of 1MB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2007) Regression : Storm model not registered in Atlas due to recent changes
[
https://issues.apache.org/jira/browse/ATLAS-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107961#comment-16107961
]
Madhan Neethiraj commented on ATLAS-2007:
-
+1 for the patch. Thanks [~sarath.ku...@gmail.com].
> Regression : Storm model not registered in Atlas due to recent changes
> --
>
> Key: ATLAS-2007
> URL: https://issues.apache.org/jira/browse/ATLAS-2007
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Blocker
> Attachments: ATLAS-2007.1.patch,
> Storm_model_registration_exception.txt
>
>
> Atlas on startup throws following exception while registering Storm model.
> {code}
> org.apache.atlas.exception.AtlasBaseException: AGGREGATION relationshipDef
> storm_topology_nodes creation attempted without an end specifying isContainer
> {code}
> This issue is a regression possibly caused by
> [ATLAS-1979|https://issues.apache.org/jira/browse/ATLAS-1979]
> Attached the complete exception stack trace .
> CC : [~sarath.ku...@gmail.com]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ATLAS-1895) Inconsistent population of createdBy and updatedBy
[
https://issues.apache.org/jira/browse/ATLAS-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-1895.
-
Resolution: Duplicate
This issue is addressed in the fix for ATLAS-1879.
> Inconsistent population of createdBy and updatedBy
> --
>
> Key: ATLAS-1895
> URL: https://issues.apache.org/jira/browse/ATLAS-1895
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
>Assignee: Péter Gergő Barna
>
> When I create types via v2 POSTs, createdBy and updatedBy are not
> automatically available or populated - they are only populated when I specify
> values for them. But when I create entities they are automatically populated
> with the user I logged into the REST API client I use. And even if I specify
> a different user they are still populated with the logged in user.
> Entity
> POST http://127.0.0.1:21000/api/atlas/v2/entity
> {code}
> {
> "entity": {
> "typeName": "test_entity_7",
> "createdBy": "admin",
> "updatedBy": "admin",
> "attributes": {
> "description": "test decription",
> "name": "test_entity_7_hw_admin",
> "owner": "admin",
> "qualifiedName": "test_entity_7_hw_admin@Sandbox",
> "test_7_1": "attr1",
> "test_7_2": "attr2"
> },
> "guid": -1
> },
> "referredEntities": {}
> }
> {code}
> GET
> http://127.0.0.1:21000/api/atlas/v2/entity/guid/ed9cf696-cd76-4814-a407-9fdb8d18da3c
> {code}
> {
> "referredEntities": {
> }
> ,
> "entity": {
> "typeName": "test_entity_7",
> "attributes": {
> "owner": "admin",
> "test_7_2": "attr2",
> "test_7_1": "attr1",
> "qualifiedName": "test_entity_7_hw_admin@Sandbox",
> "name": "test_entity_7_hw_admin",
> "description": "test decription"
> }
> ,
> "guid": "ed9cf696-cd76-4814-a407-9fdb8d18da3c",
> "status": "ACTIVE",
> "createdBy": "holger_gov",
> "updatedBy": "holger_gov",
> "createTime": 1498268595794,
> "updateTime": 1498268595794,
> "version": 0,
> "classifications": [],
> }
> }
> {code}
> Type with createdBy and updatedBy specified
> POST
> http://127.0.0.1:21000/api/atlas/v2/types/typedefs
> {code}
> {
>"enumDefs":[],
>"structDefs":[],
>"classificationDefs":[],
>"entityDefs":[
> {
> "superTypes":[
>"DataSet"
> ],
> "name":"test_entity_12",
> "description":"test_entity_12",
> "createdBy": "Laura",
> "updatedBy": "Laura",
> "attributeDefs":[
> {
>"name":"test_12_1",
>"isOptional":true,
>"isUnique":true,
>"isIndexable":false,
>"typeName":"string",
>"valuesMaxCount":1,
>"cardinality":"SINGLE",
>"valuesMinCount":0
> },
>{
>"name":"test_12_2",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"string",
>"valuesMaxCount":1,
>"cardinality":"SINGLE",
>"valuesMinCount":0
> }
> ]
>
> }
>]
> }
> {code}
> GET http://127.0.0.1:21000/api/atlas/v2/types/typedef/name/test_entity_12
> {code}
> {
> "category": "ENTITY",
> "guid": "12d8633f-e00f-426b-b445-cc1ecd800764",
> "createdBy": "Laura",
> "updatedBy": "Laura",
> "createTime": 1498283827058,
> "updateTime": 1498283827058,
> "version": 1,
> "name": "test_entity_12",
> "description": "test_entity_12",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "test_12_1",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": true,
> "isIndexable": false
> },
> {
> "name": "test_12_2",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ],
> "superTypes": [
> "DataSet"
> ],
> }
> {code}
> Type without createdBy and updatedBy specified:
> POST http://127.0.0.1:21000/api/atlas/v2/types/typedefs
> {code}
> {
>"enumDefs":[],
>"structDefs":[],
>"classificationDefs":[],
>"entityDefs":[
> {
> "superTypes":[
>"DataSet"
> ],
> "name":"test_entity_13",
> "description":"test_entity_13",
> "attributeDefs":[
> {
>"name":"test_13_1",
>"isOptional":true,
>"isUnique":true,
>"isIndexable":false,
>"typeName":"string",
>"valuesMaxCount":1,
>"cardinality":"SINGLE",
>"valuesMinCount":0
> },
>{
>
[jira] [Updated] (ATLAS-2003) Add Javadoc format to class summaries
[ https://issues.apache.org/jira/browse/ATLAS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2003: Fix Version/s: 0.8.1-incubating Fix committed in 0.8-incubating branch as well: http://git-wip-us.apache.org/repos/asf/atlas/commit/bd5f74b5 > Add Javadoc format to class summaries > - > > Key: ATLAS-2003 > URL: https://issues.apache.org/jira/browse/ATLAS-2003 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8-incubating >Reporter: Richard Ding >Assignee: Richard Ding >Priority: Minor > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: after javadoc formating.png, ATLAS-2003.patch, before > javadoc formating.png > > > Java class summary needs to be formatted with HTML tags so that the generated > Javadoc can be properly displayed in browsers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1867) org.apache.atlas.AtlasClientV2.deleteAtlasTypeDefs gives an exception
[ https://issues.apache.org/jira/browse/ATLAS-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1867: Fix Version/s: 0.8.1-incubating Fix committed in 0.8-incubating branch as well: http://git-wip-us.apache.org/repos/asf/atlas/commit/374cc342 > org.apache.atlas.AtlasClientV2.deleteAtlasTypeDefs gives an exception > - > > Key: ATLAS-1867 > URL: https://issues.apache.org/jira/browse/ATLAS-1867 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: David Radley >Assignee: Richard Ding > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1867.patch > > > The org.apache.atlas.AtlasClientV2 is the Java API for Atlas. As such the > helper methods in it are the API. calling deleteAtlasTypeDefs gives the > exception > Exception in thread "main" com.sun.jersey.api.client.ClientHandlerException: > java.net.ProtocolException: HTTP method DELETE doesn't support output > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:155) > at > com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) > at com.sun.jersey.api.client.Client.handle(Client.java:652) > at com.sun.jersey.api.client.WebResource.handle(WebResource.java:682) > at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) > at > com.sun.jersey.api.client.WebResource$Builder.method(WebResource.java:634) > at > org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:298) > at > org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:285) > at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:427) > at > org.apache.atlas.AtlasClientV2.deleteAtlasTypeDefs(AtlasClientV2.java:258) > at > org.apache.atlas.examples.DeleteTypesFromJsonFileUtil.runTypeDelete(DeleteTypesFromJsonFileUtil.java:73) > at > org.apache.atlas.examples.DeleteTypesFromJsonFileUtil.main(DeleteTypesFromJsonFileUtil.java:58) > Caused by: java.net.ProtocolException: HTTP method DELETE doesn't support > output > at > sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1083) > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler$1$1.getOutputStream(URLConnectionClientHandler.java:238) > at > com.sun.jersey.api.client.CommittingOutputStream.commitStream(CommittingOutputStream.java:117) > at > com.sun.jersey.api.client.CommittingOutputStream.write(CommittingOutputStream.java:89) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.BufferedWriter.flush(BufferedWriter.java:254) > at > com.sun.jersey.core.util.ReaderWriter.writeToAsString(ReaderWriter.java:191) > at > com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:128) > at > com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:88) > at > com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:58) > at > com.sun.jersey.api.client.RequestWriter.writeRequestEntity(RequestWriter.java:300) > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:217) > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:153) > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.
[ https://issues.apache.org/jira/browse/ATLAS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2061. - Resolution: Fixed Fix Version/s: 0.8.1-incubating 0.9-incubating Committed to the following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/ce8f65c9 - 0.8-incubating: http://git-wip-us.apache.org/repos/asf/atlas/commit/acdcb7df > Regression : Entity,Tag filter fetches empty results when applied on an enum > attribute. > --- > > Key: ATLAS-2061 > URL: https://issues.apache.org/jira/browse/ATLAS-2061 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik >Priority: Blocker > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch > > > 1.Created a tag with an attribute fileAction of type file_action. > 2.Associated the tag to an entity with fileAction value "EXECUTE" > 3.Fired a basic query with classification = and tag filter : > fileAction = EXECUTE. The entity was not fetched. > No results are fetched with "!=" operator too on values other than EXECUTE > like WRITE , READ etc., > Hence , enum filtering is not fetching results. > This is a regression , as few commits back, enum filtering was working as > expected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2018) UI: Attribute filter will not preserving state
[ https://issues.apache.org/jira/browse/ATLAS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133683#comment-16133683 ] Madhan Neethiraj commented on ATLAS-2018: - +1 for the patch. Thanks [~kevalbhatt]. > UI: Attribute filter will not preserving state > -- > > Key: ATLAS-2018 > URL: https://issues.apache.org/jira/browse/ATLAS-2018 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-2018.patch > > > Steps to reproduce. > # Click on the filter button to open filter pop-up. > # Select an attribute and apply the condition. > # Click on the apply button. > # Now Click on Filter button again it won't show previously applied filter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2056) remove unused library references
[ https://issues.apache.org/jira/browse/ATLAS-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2056: Attachment: ATLAS-2056.patch > remove unused library references > > > Key: ATLAS-2056 > URL: https://issues.apache.org/jira/browse/ATLAS-2056 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Attachments: ATLAS-2056.patch > > > JTS library referenced in pom.xml files is unused and should be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2066) Change version from 0.8.1-SNAPSHOT to 0.8.1
[ https://issues.apache.org/jira/browse/ATLAS-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134273#comment-16134273 ] Madhan Neethiraj commented on ATLAS-2066: - +1 for the patch. > Change version from 0.8.1-SNAPSHOT to 0.8.1 > --- > > Key: ATLAS-2066 > URL: https://issues.apache.org/jira/browse/ATLAS-2066 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Fix For: 0.8.1-incubating > > Attachments: ATLAS-2066.1.patch > > > Update 0.8.1-SNAPSHOT version in pom.xml to 0.8.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2107) Atlas UI Improvements: Create Entity Modal Dialog
[ https://issues.apache.org/jira/browse/ATLAS-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2107. - Resolution: Fixed Fix Version/s: 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/f1c46466 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/3a47ea6b > Atlas UI Improvements: Create Entity Modal Dialog > -- > > Key: ATLAS-2107 > URL: https://issues.apache.org/jira/browse/ATLAS-2107 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating >Reporter: Srikanth Venkat >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.9-incubating, 0.8.2 > > Attachments: Create_Entity modal.png > > > The current design of the create entity modal dialog can be improved with > small changes such as removing dividing lines, justifying the labels and > making the dialog box to be have a more consistent look and feel. > See attached mockup for the suggested improvements (Create_Entity modal.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2108) Atlas UI Improvements: Advanced Search info popup has placeholder content
[ https://issues.apache.org/jira/browse/ATLAS-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2108. - Resolution: Fixed Fix Version/s: 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/f1c46466 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/3a47ea6b > Atlas UI Improvements: Advanced Search info popup has placeholder content > - > > Key: ATLAS-2108 > URL: https://issues.apache.org/jira/browse/ATLAS-2108 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating >Reporter: Srikanth Venkat >Assignee: Keval Bhatt > Fix For: 0.9-incubating, 0.8.2 > > > Currently there is placeholder content in the help popup dialog for Advanced > search. Placeholder need to be removed to make the help more useful and the > placeholders need to be replaced with relevant content such as from Apache > Atlas wiki for DSL search http://atlas.apache.org/Search.html > *DSL Examples* > For the model, > Asset - attributes name, owner, description > DB - supertype Asset - attributes clusterName, parameters, comment > Column - extends Asset - attributes type, comment > Table - supertype Asset - db, columns, parameters, comment > Classifications - PII, Log Data > DSL queries: * from DB > * DB where name="Reporting" select name, owner > * DB where name="Reporting" select name, owner orderby name > * DB where name="Reporting" select name limit 10 > * DB where name="Reporting" select name, owner limit 10 offset 0 > * DB where name="Reporting" select name, owner orderby name limit 10 offset 5 > * DB where name="Reporting" select name, owner orderby name desc limit 10 > offset 5 > * DB has name > * DB is JdbcAccess > * Column where Column isa PII > * Table where name="sales_fact", columns > * Table where name="sales_fact", columns as column select column.name, > column.dataType, column.comment > * DB groupby(owner) select owner, count() > * DB groupby(owner) select owner, max(name) > * DB groupby(owner) select owner, min(name) from Person select count() as > 'count', max(Person.age) as 'max', min(Person.age) as 'Log Data' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2137) Rename of entityDef with children types does not perform correctly
[ https://issues.apache.org/jira/browse/ATLAS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168064#comment-16168064 ] Madhan Neethiraj commented on ATLAS-2137: - [~davidrad] - type renaming shouldn't be supported. The recommended approach should be to delete the type and create a new one. > Rename of entityDef with children types does not perform correctly > -- > > Key: ATLAS-2137 > URL: https://issues.apache.org/jira/browse/ATLAS-2137 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > > As far as I can see, if we attempt to rename an AtlasEntityDef, there is no > checking around ensuring that any subtypes are processed. > The code will resolveReferences and see the from the types edges to the > subtypes - but the supertype names in the children will now mismatch the > parent. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI
[ https://issues.apache.org/jira/browse/ATLAS-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2104. - Resolution: Fixed Fix Version/s: 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/f1c46466 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/3a47ea6b > Atlas UI Improvements: Tag CRUD operations UI > - > > Key: ATLAS-2104 > URL: https://issues.apache.org/jira/browse/ATLAS-2104 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating >Reporter: Srikanth Venkat >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.9-incubating, 0.8.2 > > Attachments: TagDetailsAddedAttr.png > > > 1. Missing labels in Edit tag popup: A Tag could have the same Name and > Description attribute values. In this case, when editing a tag, the Edit > Description modal does not communicate that only "Description" attribute > value is editable and "Name" is not editable. Also since the field does not > have any label it is confusing as to what attribute is allowed to be modified > on edit. It would be nice to prefix the attribute name to the edit dialogs > for updating the value (i.e. show "Name :" and "Description :" as prefixes to > the field values being edited so it is very clear which field is being edited. > 2. Background color of Tag Delete popup confirmation can be improved to be a > more neutral and lighter color. > 3. In create tag pop up move "Add Attribute" button to the left side. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2105) Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel
[ https://issues.apache.org/jira/browse/ATLAS-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2105. - Resolution: Fixed Fix Version/s: 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/f1c46466 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/3a47ea6b > Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel > --- > > Key: ATLAS-2105 > URL: https://issues.apache.org/jira/browse/ATLAS-2105 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating >Reporter: Srikanth Venkat >Assignee: Keval Bhatt > Fix For: 0.9-incubating, 0.8.2 > > Attachments: AttributeFilterModalDialogMockup.png > > > The attribute filter modal dialog's design is not very clean and can be > improved by: > 1) Renaming search and apply button to search. > 2) Change background color to white. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2103) Atlas UI Improvements: Confirmation modal dialog for entity/tag CRUD operations needs to be improved
[ https://issues.apache.org/jira/browse/ATLAS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2103. - Resolution: Fixed Fix Version/s: 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/f1c46466 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/3a47ea6b > Atlas UI Improvements: Confirmation modal dialog for entity/tag CRUD > operations needs to be improved > > > Key: ATLAS-2103 > URL: https://issues.apache.org/jira/browse/ATLAS-2103 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating >Reporter: Srikanth Venkat >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ConfDialogBoxIssues.png > > > The confirmation dialog when CRUD operations are performed on entities or > tags has text that is wrapped with incorrect line breaks and the background > color needs to be made lighter to offer a better user experience - see > attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2129) Atlas shutdown during progress of bulk import throws ConcurrentModificationException
[
https://issues.apache.org/jira/browse/ATLAS-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168307#comment-16168307
]
Madhan Neethiraj commented on ATLAS-2129:
-
+1 for the unit test fix.
Committed to following branches:
- master: http://git-wip-us.apache.org/repos/asf/atlas/commit/45b84fa2
- branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/4d5e69a8
> Atlas shutdown during progress of bulk import throws
> ConcurrentModificationException
>
>
> Key: ATLAS-2129
> URL: https://issues.apache.org/jira/browse/ATLAS-2129
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Blocker
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2129-bulkImport-Refactor.patch,
> ATLAS-2129-bulkImport-UnitTest-Fix.patch
>
>
> 1. Exported an hive_db containing 300 hive_table entities from cluster1 into
> a zip file .
> 2. Tried to import into cluster2.
> 3. When the import was in progress ( at 34%) , stopped Atlas.
> 4. Following exception was seen in application logs of cluster2 :
> {code}
> 2017-09-11 10:17:09,192 INFO - [pool-2-thread-9 -
> 83fe24a2-ff2b-4add-a94e-a54b09090912:] ~ bulkImport(): progress: 34% (of 301)
> -
> entity:last-imported:hive_table:[102]:(2d629a8e-5c94-40e8-b83f-8a9c91c6de8d)
> (AtlasEntityStoreV1:238)
> 2017-09-11 10:17:09,340 ERROR - [SIGTERM handler:] ~ Could not commit
> transaction [1] due to exception (StandardTitanGraph:731)
> java.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
> at java.util.ArrayList$Itr.next(ArrayList.java:851)
> at
> atlas.shaded.titan.guava.common.collect.Iterators$7.computeNext(Iterators.java:701)
> at
> atlas.shaded.titan.guava.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
> at
> atlas.shaded.titan.guava.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.prepareCommit(StandardTitanGraph.java:473)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:654)
> at
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.shutdown(TitanBlueprintsGraph.java:120)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:171)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.access$700(StandardTitanGraph.java:75)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph$ShutdownThread.start(StandardTitanGraph.java:756)
> at
> java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
> at
> java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
> at java.lang.Shutdown.runHooks(Shutdown.java:123)
> at java.lang.Shutdown.sequence(Shutdown.java:167)
> at java.lang.Shutdown.exit(Shutdown.java:212)
> at java.lang.Terminator$1.handle(Terminator.java:52)
> at sun.misc.Signal$1.run(Signal.java:212)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Other operations that are called during Atlas shut down such as Shutdown hook
> , Stopping KafkaNotification service , NotificationHookConsumer ,
> HBaseBasedAuditRepository are not called.
> 5.After that , restarted Atlas. Atlas functioned properly.
> 6.Resumed import with import option , startGuid= %. Atlas was stopped when Import was going on at 34% >
> 7. Import completed successfully.
> 8.Post import, only entities from 33% to 100% were imported . Initial 32% of
> the entities were not imported.
> 9.Fired an import command again without any interruption and without
> specifying the startGUID. All 300 hive_table entities and 1 hive_db were
> imported successfully.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2145) Errors during build
[
https://issues.apache.org/jira/browse/ATLAS-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170381#comment-16170381
]
Madhan Neethiraj commented on ATLAS-2145:
-
+1 for ATLAS-2145-2.patch.
[~bpgergo] - lets keep this fix restricted to resolving the build failure. If
any other dependencies need to be added, please track via a separate JIRA.
> Errors during build
> ---
>
> Key: ATLAS-2145
> URL: https://issues.apache.org/jira/browse/ATLAS-2145
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
> Attachments: ATLAS-2145-2.patch, ATLAS-2145.patch
>
>
> Compilation error while building atlas-intg
> atlas-intg error:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.358 s
> [INFO] Finished at: 2017-09-18T14:38:00+02:00
> [INFO] Final Memory: 70M/888M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project atlas-intg: Compilation failure: Compilation failure:
> [ERROR]
> /Users/pbarna/Desktop/apache-source/atlas/intg/src/main/java/org/apache/atlas/model/SearchFilter.java:[20,32]
> package com.sun.jersey.core.util does not exist
> {noformat}
> dashboardv2 npm error:
> {noformat}
> [ERROR] npm ERR! path
> /Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js
> [ERROR] npm ERR! code ENOENT
> [ERROR] npm ERR! errno -2
> [ERROR] npm ERR! syscall chmod
> [ERROR]
> [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod
> '/Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js'
> [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod
> '/Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js'
> [ERROR] npm ERR! enoent This is most likely not a problem with npm itself
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2137) Rename of entityDef with children types does not perform correctly
[ https://issues.apache.org/jira/browse/ATLAS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170448#comment-16170448 ] Madhan Neethiraj commented on ATLAS-2137: - A type can be removed (or renamed) only when there are no instances of the type. Note that deleting of entity instances don't remove instance vertices - as the default is to perform soft-delete. Given that property-key names of attributes and relationship edges are named 'typeName.attributeName', deleting/renaming an entity-type is not trivial. > Rename of entityDef with children types does not perform correctly > -- > > Key: ATLAS-2137 > URL: https://issues.apache.org/jira/browse/ATLAS-2137 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > > As far as I can see, if we attempt to rename an AtlasEntityDef, there is no > checking around ensuring that any subtypes are processed. > The code will resolveReferences and see the from the types edges to the > subtypes - but the supertype names in the children will now mismatch the > parent. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2132) Error code during invalid file path/unreadable file provided during import
[
https://issues.apache.org/jira/browse/ATLAS-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-2132.
-
Resolution: Fixed
Fix Version/s: 0.8.2
0.9-incubating
Committed to following branches:
- master: http://git-wip-us.apache.org/repos/asf/atlas/commit/67c04c63
- branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/1b56bec7
> Error code during invalid file path/unreadable file provided during import
> --
>
> Key: ATLAS-2132
> URL: https://issues.apache.org/jira/browse/ATLAS-2132
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Péter Gergő Barna
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2132-2.patch, ATLAS-2132.patch
>
>
> When firing import command using
> {code}
> /api/atlas/admin/importfile
> {code}
> when file provided in the import_options.json doesn't have read permission or
> file is not present , Atlas throws 500 Internal server error but with proper
> error message.
> Example :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> invalid parameters: /exportimport/db5.zip: file not found"}
> {code}
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> java.io.IOException: File '/exportimport/db6.zip' cannot be read"}
> {code}
> Expected that Atlas would throw 400 Bad Request instead of 500 Internal
> Server error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2132) Error code during invalid file path/unreadable file provided during import
[
https://issues.apache.org/jira/browse/ATLAS-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171186#comment-16171186
]
Madhan Neethiraj commented on ATLAS-2132:
-
+1 for ATLAS-2132-2.patch.
> Error code during invalid file path/unreadable file provided during import
> --
>
> Key: ATLAS-2132
> URL: https://issues.apache.org/jira/browse/ATLAS-2132
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Péter Gergő Barna
>Priority: Minor
> Attachments: ATLAS-2132-2.patch, ATLAS-2132.patch
>
>
> When firing import command using
> {code}
> /api/atlas/admin/importfile
> {code}
> when file provided in the import_options.json doesn't have read permission or
> file is not present , Atlas throws 500 Internal server error but with proper
> error message.
> Example :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> invalid parameters: /exportimport/db5.zip: file not found"}
> {code}
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> java.io.IOException: File '/exportimport/db6.zip' cannot be read"}
> {code}
> Expected that Atlas would throw 400 Bad Request instead of 500 Internal
> Server error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2100) Support for Saving Searches
[ https://issues.apache.org/jira/browse/ATLAS-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2100: Issue Type: Sub-task (was: Improvement) Parent: ATLAS-1822 > Support for Saving Searches > --- > > Key: ATLAS-2100 > URL: https://issues.apache.org/jira/browse/ATLAS-2100 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry > Fix For: trunk > > Attachments: ATLAS-2100-SavedSearch-EntityBased.patch > > > *Background* > The current set of features around search allows user to construct complex > queries. These queries once constructed, cannot be persisted and re-used > later. The user will have to reconstruct these if they were to run them again. > *Solution* > The ability to save constructed queries and retrieve them later will benefit > the user. > *Implementation* > A logged in user should be able to: > * Save the constructed query. > * View all the queries constructed. > * Edit already constructed query. > * Execute already constructed query. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2028) Basic query with entity and tag filters : Invalid filter keys for type and tags attributes are ignored and fetches all entities of the type / associated to the tag
[
https://issues.apache.org/jira/browse/ATLAS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2028:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> Basic query with entity and tag filters : Invalid filter keys for type and
> tags attributes are ignored and fetches all entities of the type / associated
> to the tag
> ---
>
> Key: ATLAS-2028
> URL: https://issues.apache.org/jira/browse/ATLAS-2028
> Project: Atlas
> Issue Type: Sub-task
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Attachments:
> 0001-ATLAS-2028-Invalid-attributes-in-Basic-search-reques.patch
>
>
> Basic search request with POST body fired using curl:
> {code}
> {
>
> "entityFilters":{"condition":"AND","criterion":[{"attributeName":"invalid_attr","operator":"=","attributeValue":"userdir"}]},
> "tagFilters":null,
> "attributes":null,
> "query":null,
> "excludeDeletedEntities":true,
> "limit":25,
> "typeName":"hdfs_path",
> "classification":null
> }
> {code}
> All the hdfs_path entities are fetched because invalid filter keys are
> ignored :
> {code}
> Converted query string with 2 replacements: [v."__typeName":(hdfs_path) AND
> v."__state":ACTIVE] => [iyt_t:(hdfs_path) AND b2d_t:ACTIVE]
> (IndexSerializer:648)
> {code}
> Same happens with invalid tag attribute filters also.
> This gives a delusion that all returned hdfs_path entities are satisfied by
> the filter condition.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2101) Remove use of Guava Stopwatch from Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2101: Fix Version/s: (was: trunk) 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/7eff37a6 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/7780b520 > Remove use of Guava Stopwatch from Atlas > > > Key: ATLAS-2101 > URL: https://issues.apache.org/jira/browse/ATLAS-2101 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Minor > Fix For: 0.9-incubating, 0.8.2 > > Attachments: StandardIDPool.java > > > *Background* > Using _IntelliJ_ attempt to start Atlas server. Chances are the startup will > fail due to error in resolving _com.google.common.base.StopWatch_. > Similar problem is observed on some build environments. > *Solution* > * Add _StandardIDPool.java_ to shaded _Titan0_ JAR. > * Replace use of _Stopwatch_ with some alternative implementation. > See also: [HBASE-14963|https://issues.apache.org/jira/browse/HBASE-14963] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-1822) Search Query Builder and Faceted Search in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reassigned ATLAS-1822: --- Assignee: Madhan Neethiraj > Search Query Builder and Faceted Search in Atlas > > > Key: ATLAS-1822 > URL: https://issues.apache.org/jira/browse/ATLAS-1822 > Project: Atlas > Issue Type: Improvement > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Madhan Neethiraj > > Current search experience in Atlas UI is pretty basic and any advanced > searches require knowledge of DSL that might be difficult for business users. > As a data steward or data consumer, I need an easy and intuitive way to > perform faceted searches on entities, classifications, relationships, and > business glossaries and filter the results based on a combination of > parameters so I can navigate and locate assets for curation and in order to > take any governance actions. I also need to be able to save my searches and > filters and rerun them dynamically against the latest state of the enterprise > metadata catalog in Atlas. > Implementation considerations: > # For business users, there should be default filters provided based on > commonly used criteria in the search experience > # Any search results should only show metadata of data assets that user has > permission to view, based upon authorization policies (via Ranger) > # Search facets need to be based on search conditions and should allow for > sequence of AND, OR and NOT operations with multiple search conditions > # Search facets details (should allow for combinations of any or all of the > following): > * Asset type (entity types) > * Attribute value checker (should allow for combinations of range checks, > ordinality, exact match, numeric, string and date comparisons, single or > muliple values, category checks, nulls) > * Created time > * Updated time > * Size (where relevant for e.g. HDFS files) > * Deleted/Active status > * Owner > * Custom property values > * File format > * Asset name > * Physical storage context: Datalake/cluster or datacenter holding the asset > * Classification > * Glossary/taxonomy association > Note: > # Searches should be able to be saved and scoped to a particular business > catalog or asset type or namespace (when multi-tenancy is supported by Atlas > in the future) > # Once search results are available, user should be able to filter by any of > the facets. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1994) Search API: Work with Tag attributes when query and entity filters are specified
[ https://issues.apache.org/jira/browse/ATLAS-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1994: Issue Type: Sub-task (was: Improvement) Parent: ATLAS-1822 > Search API: Work with Tag attributes when query and entity filters are > specified > > > Key: ATLAS-1994 > URL: https://issues.apache.org/jira/browse/ATLAS-1994 > Project: Atlas > Issue Type: Sub-task >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > Currently when the entity text query is specified with the entity and it's > filters none of the tag attributes are considered during filtering (search). > This change honors the tag attributes during search even under the above > scenario -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1961) Basic search improvement in use of Solr index for attribute filtering
[ https://issues.apache.org/jira/browse/ATLAS-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1961: Issue Type: Sub-task (was: Improvement) Parent: ATLAS-1822 > Basic search improvement in use of Solr index for attribute filtering > - > > Key: ATLAS-1961 > URL: https://issues.apache.org/jira/browse/ATLAS-1961 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-1961.patch > > > Current basic search implementation uses Solr only when both type and > attribute filters can be done via Solr. When the type specified has too many > subtypes, Solr is not used - even though Solr could be used for attribute > filtering. Use of Solr for attribute filtering can be help quicker response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2091) Search using entity and trait attributes - "#" in string attribute filter doesn't fetch results
[ https://issues.apache.org/jira/browse/ATLAS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2091: Issue Type: Sub-task (was: Bug) Parent: ATLAS-1822 > Search using entity and trait attributes - "#" in string attribute filter > doesn't fetch results > --- > > Key: ATLAS-2091 > URL: https://issues.apache.org/jira/browse/ATLAS-2091 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-2091-Attribute-values-containing-Tokenizer-cha.patch > > > 1. Created an hdfs_path entity with owner name = "user#3" > 2. Fired basic search with type name = hdfs_path and filter - owner = user#3. > hdfs_path entity was returned. > 3. Fired basic search with type name = hdfs_path and filter - owner contains > user#3. No entity is returned. > Other than "=" , operators like != , contains , ends_with , begins_with are > not fetching expected results due to # in search filter key. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2118) Basic search - Contains clause issues
[
https://issues.apache.org/jira/browse/ATLAS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2118:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Sub-task
>Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
>
> Attachments:
> 0001-ATLAS-2118-Issues-with-contains-in-Basic-search.patch
>
>
> If the contains clause attribute value contains any of the special regex
> chars like
> "+", "|", "(", "{", "[", "*", "?", "$", "/", "^"
> then the graph query fails with Invalid pattern exception
> Solution: Escape all occurrences of the special characters
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2148) Saved Search: Introduce BASIC and ADVANCE Search Types During Save
[ https://issues.apache.org/jira/browse/ATLAS-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2148: Issue Type: Sub-task (was: Improvement) Parent: ATLAS-1822 > Saved Search: Introduce BASIC and ADVANCE Search Types During Save > -- > > Key: ATLAS-2148 > URL: https://issues.apache.org/jira/browse/ATLAS-2148 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core, atlas-webui >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Minor > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2148-QueryType.patch > > > *Background* > Existing implementation of _SavedSearch_ does not have a way to differentiate > saving of basic and advanced searches. > Basic searches are the ones where user constructs the query using the new > search UI. > Advanced queries are where the user types a DSL query into the search box. > Having this notion should allow for better differentiation of the 2 types of > queries. If the type is used in specifying unique attribute, user could > create query with same name. > *Implementation* > Additional attribute added to ___AtlasSavedSearch_. REST API updated to > include the query type parameter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2022) Regression : Empty results fetched from GET Basic search query
[
https://issues.apache.org/jira/browse/ATLAS-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2022:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> Regression : Empty results fetched from GET Basic search query
> --
>
> Key: ATLAS-2022
> URL: https://issues.apache.org/jira/browse/ATLAS-2022
> Project: Atlas
> Issue Type: Sub-task
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sharmadha Sainath
>Priority: Blocker
> Fix For: trunk, 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2022.patch
>
>
> Basic search query fired as a POST request with attribute , tag filters
> fetches correct results.
> But Basic query fired as a GET request with query params encoded in the URL ,
> returns empty results.
> For example : Basic query : typeName = "hive_table" query = hive_table in Atlas"
> http://localhost:21000/api/atlas/v2/search/basic?typeName=hive_table=employee
> returns
> {code}
> {
> queryType: "BASIC",
> searchParameters: {
> query: "employee",
> typeName: "hive_table",
> excludeDeletedEntities: false,
> limit: 0,
> offset: 0
> },
> queryText: "employee"
> }
> {code}
> Few commits back , following was the response :
> {code}
> {
> queryType: "BASIC",
> type: "hive_table",
> entities: [
> {
> typeName: "hive_table",
> attributes: {
> owner: "admin",
> qualifiedName: "default.employee@cl1",
> name: "employee",
> description: null
> },
> guid: "253aa208-0415-4e86-8611-3858fad78ede",
> status: "ACTIVE",
> displayText: "employee",
> classificationNames: [ ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2025) Basic query with entity and tag filters : Providing invalid tag name for classification returns all entities matching typename/query
[
https://issues.apache.org/jira/browse/ATLAS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2025:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> Basic query with entity and tag filters : Providing invalid tag name for
> classification returns all entities matching typename/query
>
>
> Key: ATLAS-2025
> URL: https://issues.apache.org/jira/browse/ATLAS-2025
> Project: Atlas
> Issue Type: Sub-task
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments:
> 0002-ATLAS-2025-Validation-of-classification-type-in-basi.patch
>
>
> Fired a basic query with following POST request body with Non Existing tag
> using curl (because UI only lets user select from existing tags):
> {code}
> {
> "entityFilters":null,
> "tagFilters":null,
> "attributes":null,
> "query":null,
> "excludeDeletedEntities":true,
> "limit":25,
> "typeName":"kafka_topic",
> "classification":"non_existing_tag"
> }
> {code}
> GET Basic search request with classification parameter also lists all the
> kakfa_topic entities:
> {code}
> http://localhost:21000/api/atlas/v2/search/basic?typeName=kafka_topic=non_existing_tag=50
> {code}
> Expected 40X Response code saying that tag doesn't exist. But the response
> listed all the kafka_topic entities. This gives an delusion that all returned
> kafka_topic entities are tagged with 'non_existing_tag'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2082) Regression: Search fails when filter contains a boolean attribute and a string attribute with special characters
[
https://issues.apache.org/jira/browse/ATLAS-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2082:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> Regression: Search fails when filter contains a boolean attribute and a
> string attribute with special characters
>
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
> Issue Type: Sub-task
> Components: atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {
>"entityFilters":{
> "condition":"AND",
> "criterion":[
> {
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
> },
> {
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
> }
> ]
>},
>"tagFilters":null,
>"attributes":[
> "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.
[ https://issues.apache.org/jira/browse/ATLAS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2061: Issue Type: Sub-task (was: Bug) Parent: ATLAS-1822 > Regression : Entity,Tag filter fetches empty results when applied on an enum > attribute. > --- > > Key: ATLAS-2061 > URL: https://issues.apache.org/jira/browse/ATLAS-2061 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik >Priority: Blocker > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch > > > 1.Created a tag with an attribute fileAction of type file_action. > 2.Associated the tag to an entity with fileAction value "EXECUTE" > 3.Fired a basic query with classification = and tag filter : > fileAction = EXECUTE. The entity was not fetched. > No results are fetched with "!=" operator too on values other than EXECUTE > like WRITE , READ etc., > Hence , enum filtering is not fetching results. > This is a regression , as few commits back, enum filtering was working as > expected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2115) Regression: Basic search performance
[ https://issues.apache.org/jira/browse/ATLAS-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2115: Issue Type: Sub-task (was: Bug) Parent: ATLAS-1822 > Regression: Basic search performance > > > Key: ATLAS-2115 > URL: https://issues.apache.org/jira/browse/ATLAS-2115 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8-incubating, 0.8.1-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.9-incubating, 0.8.2 > > > When searching using a tag without any attributes the call timings were > doubled (worst case tripled) regardless of the offset and limit. This patch > introduces a new code path which allows faster retrieval of vertices for the > mentioned scenario. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2117) Basic search issues due to Titan Solr schema
[ https://issues.apache.org/jira/browse/ATLAS-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2117: Issue Type: Sub-task (was: Bug) Parent: ATLAS-1822 > Basic search issues due to Titan Solr schema > > > Key: ATLAS-2117 > URL: https://issues.apache.org/jira/browse/ATLAS-2117 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating, 0.9-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-2117-Work-around-for-basic-search-due-to-Titan.patch > > > When using Solr as indexing backend, the tokenization of the string is > performed using the StandardTokenizerFactory which treats punctuations and > special characters as delimiters which results in the more indexed terms > being associated with the associated vertex (document) > Also there's a LowercaseFilterFactory which makes lookup case insensitive. > This schema design doesn't work well for the current basic search enhancement > (ATLAS-1880) causing a lot of false positives/negatives when querying the > index. > The workaround/hack for this is to do an in-memory filtering when such schema > violations are found or push the entire attribute query down to the graph > which might be in-efficient and memory intensive. (Current JIRA will track > this) > Correct solution would be to re-index the existing data with a schema change > and not use the mentioned code workarounds for better performance of the > search. (Should be taken up in separate JIRA) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2159) Incorrect createTime retrieved for entity attributes in related entities search
[ https://issues.apache.org/jira/browse/ATLAS-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175594#comment-16175594 ] Madhan Neethiraj commented on ATLAS-2159: - +1 for the patch. > Incorrect createTime retrieved for entity attributes in related entities > search > --- > > Key: ATLAS-2159 > URL: https://issues.apache.org/jira/browse/ATLAS-2159 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-2159.1.patch > > > While fetching the tables of a database , > entities[“attributes”][“createTime”] of a table has value of > response[“entity”][“createTime”] instead of > response[“entity”][“attributes”][“createTime”] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2150) UI to support search-history and favorites
Madhan Neethiraj created ATLAS-2150: --- Summary: UI to support search-history and favorites Key: ATLAS-2150 URL: https://issues.apache.org/jira/browse/ATLAS-2150 Project: Atlas Issue Type: Sub-task Components: atlas-webui Reporter: Madhan Neethiraj Assignee: Keval Bhatt -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2150) UI to support search-history and favorites
[ https://issues.apache.org/jira/browse/ATLAS-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2150: Attachment: ATLAS-2150.patch > UI to support search-history and favorites > -- > > Key: ATLAS-2150 > URL: https://issues.apache.org/jira/browse/ATLAS-2150 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Madhan Neethiraj >Assignee: Keval Bhatt > Fix For: 0.8.2 > > Attachments: ATLAS-2150.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2150) UI to support search-history and favorites
[ https://issues.apache.org/jira/browse/ATLAS-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173750#comment-16173750 ] Madhan Neethiraj commented on ATLAS-2150: - +1 for the patch. UI for saved-searches (Favorite Search) looks good! Thanks [~kevalbhatt]. > UI to support search-history and favorites > -- > > Key: ATLAS-2150 > URL: https://issues.apache.org/jira/browse/ATLAS-2150 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Madhan Neethiraj >Assignee: Keval Bhatt > Fix For: 0.8.2 > > Attachments: ATLAS-2150.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2115) Regression: Basic search performance
[ https://issues.apache.org/jira/browse/ATLAS-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2115. - Resolution: Fixed Fix Version/s: (was: 0.8.1-incubating) (was: 0.8-incubating) (was: trunk) 0.8.2 0.9-incubating Committed to the following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/1dc7f549 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/221e829f > Regression: Basic search performance > > > Key: ATLAS-2115 > URL: https://issues.apache.org/jira/browse/ATLAS-2115 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating, 0.8.1-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.9-incubating, 0.8.2 > > > When searching using a tag without any attributes the call timings were > doubled (worst case tripled) regardless of the offset and limit. This patch > introduces a new code path which allows faster retrieval of vertices for the > mentioned scenario. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2141) Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE
[ https://issues.apache.org/jira/browse/ATLAS-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2141: Attachment: ATLAS-2141.patch > Regression : Disassociating tag from Entity and Editing tag attributes > associated to an entity throw NPE > > > Key: ATLAS-2141 > URL: https://issues.apache.org/jira/browse/ATLAS-2141 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Madhan Neethiraj > Attachments: ATLAS-2141.patch, NPE_during_tag_delete.txt, > NPE_during_tag_edit.txt > > > Editing tag attribute value associated to an entity throws 500 Internal > server error with NPE and with Error Notification "Tag could not be > added". > Disassociating a tag from an entity also throws 500 Internal server error > with NPE , and with Error Notification "Tag could not be deleted". > Tag addition works fine. > This is a regression caused after > [ATLAS-2100|https://issues.apache.org/jira/browse/ATLAS-2100]. > Attached the exception stack trace seen for both cases. > CC :[~ashutoshm] [~madhan.neethiraj] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2141) Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE
[ https://issues.apache.org/jira/browse/ATLAS-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reassigned ATLAS-2141: --- Assignee: Madhan Neethiraj > Regression : Disassociating tag from Entity and Editing tag attributes > associated to an entity throw NPE > > > Key: ATLAS-2141 > URL: https://issues.apache.org/jira/browse/ATLAS-2141 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Madhan Neethiraj > Attachments: NPE_during_tag_delete.txt, NPE_during_tag_edit.txt > > > Editing tag attribute value associated to an entity throws 500 Internal > server error with NPE and with Error Notification "Tag could not be > added". > Disassociating a tag from an entity also throws 500 Internal server error > with NPE , and with Error Notification "Tag could not be deleted". > Tag addition works fine. > This is a regression caused after > [ATLAS-2100|https://issues.apache.org/jira/browse/ATLAS-2100]. > Attached the exception stack trace seen for both cases. > CC :[~ashutoshm] [~madhan.neethiraj] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2140) throwing overly generic exception type
[ https://issues.apache.org/jira/browse/ATLAS-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reassigned ATLAS-2140: --- Assignee: Zsombor Gegesy > throwing overly generic exception type > -- > > Key: ATLAS-2140 > URL: https://issues.apache.org/jira/browse/ATLAS-2140 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy >Priority: Minor > Labels: code-cleanup > Fix For: 0.9-incubating, 0.8.2 > > Attachments: > 0001-ATLAS-2140-Throwing-overly-generic-exceptions-or-unn.patch > > > In various places in the codebase exceptions are declared unnecessarily > broadly or without actually throwing it. Which could cause confusion in the > caller, making it harder to handling it, and recovering from this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2156) UI save-search : allow user to edit name
[ https://issues.apache.org/jira/browse/ATLAS-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176488#comment-16176488 ] Madhan Neethiraj commented on ATLAS-2156: - +1 for the patch. Thanks [~kevalbhatt]. > UI save-search : allow user to edit name > > > Key: ATLAS-2156 > URL: https://issues.apache.org/jira/browse/ATLAS-2156 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-2156.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2156) UI save-search : allow user to edit name
[ https://issues.apache.org/jira/browse/ATLAS-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2156. - Resolution: Fixed Fix Version/s: 0.8.2 0.9-incubating Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/20f2fba7 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/c6abf76e > UI save-search : allow user to edit name > > > Key: ATLAS-2156 > URL: https://issues.apache.org/jira/browse/ATLAS-2156 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2156.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2157) Atlas Hive hook runs into unhandled exceptions from beeline if there are temp tables involved
[ https://issues.apache.org/jira/browse/ATLAS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reassigned ATLAS-2157: --- Assignee: Madhan Neethiraj > Atlas Hive hook runs into unhandled exceptions from beeline if there are temp > tables involved > - > > Key: ATLAS-2157 > URL: https://issues.apache.org/jira/browse/ATLAS-2157 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 0.8-incubating, 0.7.1-incubating > Environment: HDP 2.6.2 >Reporter: Sailaja Navvluru >Assignee: Madhan Neethiraj > > Opening JIRA as requested by [~madhan.neethiraj] in the mailing list > *Repro steps:* > Insert into a Hive table from beeline, insert goes through fine but Atlas > Hive hook throws errors. > *Detailed description pasted from mailing list*: > created a table from both Hive CLI and beeline and inserted a row with > Atlas Hive hook enabled. From Hive CLI the insert goes through fine without > any errors but > from beeline I see errors for a temp table not found although insert itself > succeeds and temp > table shows up in table listing. Do I need to do anything extra for > beeline/HS2 connections > when Atlas is enabled ? > > hive> create table test1(c1 int, c2 string); > OK > Time taken: 2.108 seconds > hive> insert into test1 values(1,'v'); > Query ID = hive_20170920092542_d8ec0a4b-b88d-4d87-b59d-790f2eae6792 > Total jobs = 1 > Launching Job 1 out of 1 > Status: Running (Executing on YARN cluster with App id > application_1505852425742_0004) > > > VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED > KILLED > > Map 1 .. SUCCEEDED 1 100 0 > 0 > > VERTICES: 01/01 [==>>] 100% ELAPSED TIME: 4.68 s > > Loading data to table default.test1 > Table default.test1 stats: [numFiles=1, numRows=1, totalSize=4, rawDataSize=3] > OK > Time taken: 6.7 seconds > hive> select * from test1; > OK > 1 v > Time taken: 0.112 seconds, Fetched: 1 row(s) > hive> > > Beeline version 1.2.1000.2.6.2.0-133 by Apache Hive > 0: jdbc:hive2://> create table s1(c1 int,c2 string); > OK > No rows affected (2.345 seconds) > > 0: jdbc:hive2://> insert into s1 values(1,'v'); > 17/09/20 09:28:24 [main]: ERROR hdfs.KeyProviderCache: Could not find uri > with key [dfs.encryption.key.provider.uri] > to create a keyProvider !! > Query ID = hive_20170920092824_14bfdec4-dfe8-4b97-b5be-0af74de055ce > Total jobs = 1 > Launching Job 1 out of 1 > Status: Running (Executing on YARN cluster with App id > application_1505852425742_0005) > > Loading data to table default.s1 > Table default.s1 stats: [numFiles=1, numRows=1, totalSize=4, rawDataSize=3] > OK > No rows affected (498.295 seconds) > 0: jdbc:hive2://> > 0: jdbc:hive2://> 17/09/20 09:36:42 [Atlas Logger 1]: ERROR metadata.Hive: > Table values__tmp__table__1 > not found: default.values__tmp__table__1 table not found > 17/09/20 09:36:43 [Atlas Logger 1]: ERROR hook.HiveHook: Atlas hook failed > due to error > java.lang.reflect.UndeclaredThrowableException > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1884) > at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.apache.atlas.hook.AtlasHookException: > HiveHook.registerProcess() failed. > at > org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:701) > at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:268) > at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83) > at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866) > ... 6 more > Caused by: org.apache.atlas.hook.AtlasHookException: > HiveHook.processHiveEntity() failed.
[jira] [Updated] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names
[
https://issues.apache.org/jira/browse/ATLAS-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2121:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> Inconsistency in basic search results due to case sensitivity of type names
> ---
>
> Key: ATLAS-2121
> URL: https://issues.apache.org/jira/browse/ATLAS-2121
> Project: Atlas
> Issue Type: Sub-task
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.2
>
>
> Type names are case sensitive hence 2 types can be created with different
> cases.
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created,
> and when a BASIC search is fired with
> typeName= type1 , e1 is returned and
> typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search ,
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and
> returns entity tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct
> behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names
[
https://issues.apache.org/jira/browse/ATLAS-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-2121.
-
Resolution: Fixed
Fix Version/s: 0.8.2
0.9-incubating
Committed to the following branches:
- master: http://git-wip-us.apache.org/repos/asf/atlas/commit/c0f0abc1
- branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/5645c9e7
> Inconsistency in basic search results due to case sensitivity of type names
> ---
>
> Key: ATLAS-2121
> URL: https://issues.apache.org/jira/browse/ATLAS-2121
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.2
>
>
> Type names are case sensitive hence 2 types can be created with different
> cases.
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created,
> and when a BASIC search is fired with
> typeName= type1 , e1 is returned and
> typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search ,
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and
> returns entity tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct
> behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2008) basic-search: numeric tag-attribute filtering fails with java.lang.ClassCastException
[
https://issues.apache.org/jira/browse/ATLAS-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2008:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-1822
> basic-search: numeric tag-attribute filtering fails with
> java.lang.ClassCastException
> -
>
> Key: ATLAS-2008
> URL: https://issues.apache.org/jira/browse/ATLAS-2008
> Project: Atlas
> Issue Type: Sub-task
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2008.patch
>
>
> When tag-attribute filter includes attributes of numeric types (int, double,
> float), Gremlin queries fail due to ClassCastException:
> {noformat}
> 2017-07-29 07:58:15,868 DEBUG - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~
> gremlinTagFilterQuery=g.V().has('__guid', T.in, guids).has('__traitNames',
> T.in, traitNames).as('e').out().has('__typeName', T.in,
> typeNames).has('tag4.attr4-double', T.gte, 6).back('e').toList()
> (ClassificationSearchProcessor:119)
> ...
> 2017-07-29 07:58:16,189 WARN - [pool-1-thread-9 -
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ javax.script.ScriptException:
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.Double (ClassificationSearchProcessor:260)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-2186) Atlas not responding for long time after startup
[ https://issues.apache.org/jira/browse/ATLAS-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190064#comment-16190064 ] Madhan Neethiraj edited comment on ATLAS-2186 at 10/3/17 6:00 PM: -- Changes in ATLAS-2086 have been reverted in branch-0.8. [~ashutoshm] is investigating this issue and will commit a new patch to address the issue found with newer version of Jetty. was (Author: madhan.neethiraj): Changes in ATLAS-2086( have been reverted in branch-0.8. [~ashutoshm] is investigating this issue and will commit a new patch to address the issue found with newer version of Jetty. > Atlas not responding for long time after startup > > > Key: ATLAS-2186 > URL: https://issues.apache.org/jira/browse/ATLAS-2186 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.2 >Reporter: Ayub Pathan >Priority: Blocker > Fix For: 0.8.2 > > Attachments: atlas.20171003-122531.out > > > Atlas with latest bits is not responding for any query, the request times > out. This behavior can be seen for more than ~15 minutes after atlas startup > and everything will be back to normal after this period. > I suspect one of the threads is looping or hanging which is resulting in this > state. Atlas logs does not show any suspicious information (checked with > debug logs as well). I took a thread dump of Atlas, attaching the dump file > and report below. I strongly suspect, this might be an issue with newer jetty > version introduced recently. > Thread dump report: > http://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTcvMTAvMy8tLWF0bGFzLjIwMTcxMDAzLTEyMjUzMS5vdXQtLTEyLTE2LTQ2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2186) Atlas not responding for long time after startup
[ https://issues.apache.org/jira/browse/ATLAS-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2186. - Resolution: Fixed Fix Version/s: (was: 0.8.1) 0.8.2 Changes in ATLAS-2086( have been reverted in branch-0.8. [~ashutoshm] is investigating this issue and will commit a new patch to address the issue found with newer version of Jetty. > Atlas not responding for long time after startup > > > Key: ATLAS-2186 > URL: https://issues.apache.org/jira/browse/ATLAS-2186 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.2 >Reporter: Ayub Pathan >Priority: Blocker > Fix For: 0.8.2 > > Attachments: atlas.20171003-122531.out > > > Atlas with latest bits is not responding for any query, the request times > out. This behavior can be seen for more than ~15 minutes after atlas startup > and everything will be back to normal after this period. > I suspect one of the threads is looping or hanging which is resulting in this > state. Atlas logs does not show any suspicious information (checked with > debug logs as well). I took a thread dump of Atlas, attaching the dump file > and report below. I strongly suspect, this might be an issue with newer jetty > version introduced recently. > Thread dump report: > http://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTcvMTAvMy8tLWF0bGFzLjIwMTcxMDAzLTEyMjUzMS5vdXQtLTEyLTE2LTQ2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception
[ https://issues.apache.org/jira/browse/ATLAS-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197328#comment-16197328 ] Madhan Neethiraj commented on ATLAS-2194: - +1 for the patch. Thanks [~kevalbhatt]. > In Basic Search for Tag if any columns are removed then UI throws exception > --- > > Key: ATLAS-2194 > URL: https://issues.apache.org/jira/browse/ATLAS-2194 > Project: Atlas > Issue Type: Bug >Reporter: Tejas Rawool >Assignee: Keval Bhatt > Attachments: ATLAS-2194.patch > > > Steps to Reproduce:- > 1.Create a new Tag and click on its Search Tag > 2.Now remove few columns (e.g:- Tags and Type) > 3.In Console Error appears on "SearchResultLayoutView" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2213) HiveHook update to remove unused attributes
Madhan Neethiraj created ATLAS-2213: --- Summary: HiveHook update to remove unused attributes Key: ATLAS-2213 URL: https://issues.apache.org/jira/browse/ATLAS-2213 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: 0.8.1 Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Atas Hive hook calls Hive APIs to get values to populate Hive entity attributes. Some of these values obtained from Hive are unused in Hive entities - like queryType. Hive hook should be updated to remove such unused attributes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2213) HiveHook update to remove unused attributes
[ https://issues.apache.org/jira/browse/ATLAS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2213: Attachment: ATLAS-2213.patch > HiveHook update to remove unused attributes > --- > > Key: ATLAS-2213 > URL: https://issues.apache.org/jira/browse/ATLAS-2213 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 0.8.1 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Attachments: ATLAS-2213.patch > > > Atas Hive hook calls Hive APIs to get values to populate Hive entity > attributes. Some of these values obtained from Hive are unused in Hive > entities - like queryType. Hive hook should be updated to remove such unused > attributes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2120) Inconsistency in Importing already existing types on backup cluster with new definition.
[
https://issues.apache.org/jira/browse/ATLAS-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159548#comment-16159548
]
Madhan Neethiraj commented on ATLAS-2120:
-
bq. Entity is not imported into the cluster2 , but the type definition of tag1
in cluster2 had 3 attributes now (attrib1 : date , attrib2:Integer ,
attrib3:Integer)
[~ashutoshm] - import should have failed with no updates to tag1 definition,
right? i.e attrib2 shouldn't have been added to tag1 in cluster2.
> Inconsistency in Importing already existing types on backup cluster with new
> definition.
>
>
> Key: ATLAS-2120
> URL: https://issues.apache.org/jira/browse/ATLAS-2120
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Critical
> Attachments: ATLAS-2120-Import-Failure-Test.patch, hdfs_path1.zip
>
>
> 1.Created a tag tag1 on cluster1 with attributes :
> * attrib1 : string
> * attrib2 : integer
> 2.Created a tag with same name on cluster2 with attributes:
> *attrib1: date
> *attrib3: integer
> (Note the tag names are same , and attrib1 is same but datatypes of attrib1
> are different in both the clusters)
> 3. On cluster1 , created an entity and associated the tag1 to the entity with
> attribute values
> *attrib1: "randstr"
> *attrib2: 5
> and exported the entity into zip file .
> 4.Tried to import the entity into cluster2.
> Import failed with 500 Internal server error and with following exception :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
> com.thinkaurelius.titan.core.SchemaViolationException: Value [rand_str] is
> not an instance of the expected data type for property key [tag1.attrib1] and
> cannot be converted. Expected: class java.lang.Long, found: class
> java.lang.String"}
> {code}
> Following is the inconsistency observed :
> Entity is not imported into the cluster2 , but the type definition of tag1 in
> cluster2 had 3 attributes now (attrib1 : date , attrib2:Integer ,
> attrib3:Integer) and 500 Internal server error is thrown.
> Normally, when a datatype of an attribute is attempted to be updated , Atlas
> throws the following exception and the type is not updated.
> {code}
> {"errorCode":"ATLAS-400-00-029","errorMessage":"Data type update for
> attribute is not supported"}
> {code}
> Expected the same to happen while importing (i.e) Import failing with Bad
> request with the proper error message.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information
[ https://issues.apache.org/jira/browse/ATLAS-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146242#comment-16146242 ] Madhan Neethiraj commented on ATLAS-2097: - [~sarath.ku...@gmail.com] - the changes look good. +1 for the patch. > Update atlas docs site.xml about 0.8.1 documentation and release information > > > Key: ATLAS-2097 > URL: https://issues.apache.org/jira/browse/ATLAS-2097 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-2097.1.patch > > > * Update atlas docs site.xml about 0.8.1 documentation and release information > * Change pom.xml version to 0.8.2-SNAPSHOT for branch-0.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages
[ https://issues.apache.org/jira/browse/ATLAS-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2128: Fix Version/s: (was: 0.9.1) 0.9-incubating > UI Regression : DSL Results pagination doesn't spawn more than 2 pages > -- > > Key: ATLAS-2128 > URL: https://issues.apache.org/jira/browse/ATLAS-2128 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2128.patch > > > 1. Created 300 hive_tables. > 2. On Basic Search in UI , fired search typename= hive_table > 3. hive_table results were fetched across 12 pages - 25 entities in each page > - which is the correct behavior. > 4.On Advanced Search in UI , fired search typename = hive_table > * In the 1st page , 1- 25 results were shown. > * On clicking next , in the 2nd page , 26 - 50 results were shown > * On clicking next , Expected to land in 3rd page with 51 - 75 > results , but , 26-50 results were loaded again and the Next Button was > disabled. > Calls made to the Atlas backend seem to be correct. On clicking "Next" each > time , correct set of results were fetched. For example , call was made to > fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 > results and disabled "Next" button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages
[ https://issues.apache.org/jira/browse/ATLAS-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2128: Fix Version/s: 0.8.2 0.9.1 Committed in branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/0225cad5 > UI Regression : DSL Results pagination doesn't spawn more than 2 pages > -- > > Key: ATLAS-2128 > URL: https://issues.apache.org/jira/browse/ATLAS-2128 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2128.patch > > > 1. Created 300 hive_tables. > 2. On Basic Search in UI , fired search typename= hive_table > 3. hive_table results were fetched across 12 pages - 25 entities in each page > - which is the correct behavior. > 4.On Advanced Search in UI , fired search typename = hive_table > * In the 1st page , 1- 25 results were shown. > * On clicking next , in the 2nd page , 26 - 50 results were shown > * On clicking next , Expected to land in 3rd page with 51 - 75 > results , but , 26-50 results were loaded again and the Next Button was > disabled. > Calls made to the Atlas backend seem to be correct. On clicking "Next" each > time , correct set of results were fetched. For example , call was made to > fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 > results and disabled "Next" button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2071) UI : Minification of atlas code (js,css)
[ https://issues.apache.org/jira/browse/ATLAS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2071: Fix Version/s: 0.8.2 Committed to branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/565213d4 > UI : Minification of atlas code (js,css) > > > Key: ATLAS-2071 > URL: https://issues.apache.org/jira/browse/ATLAS-2071 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2071.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1218) Atlas says it is started but does not accept REST requests
[ https://issues.apache.org/jira/browse/ATLAS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1218: Fix Version/s: 0.8.2 Committed to branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/97ce63ec > Atlas says it is started but does not accept REST requests > -- > > Key: ATLAS-1218 > URL: https://issues.apache.org/jira/browse/ATLAS-1218 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: David Radley >Assignee: Richard Ding > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-1218_1.patch, ATLAS-1218_2.patch, ATLAS-1218.patch > > > I start Atlas on the command line and it tells me is started - but REST > requests are not accepted immediately. There appears to be asynchronous > background processes that have not yet initialized. I feel that when Atlas > says it is started it should be open for business and accept REST requests. > a few seconds later REST requests are accepted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2060) Fix logger class name typos
[ https://issues.apache.org/jira/browse/ATLAS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2060: Fix Version/s: 0.8.2 Committed to branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/16a02fc7 > Fix logger class name typos > --- > > Key: ATLAS-2060 > URL: https://issues.apache.org/jira/browse/ATLAS-2060 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 0.8-incubating >Reporter: Richard Ding >Assignee: Richard Ding >Priority: Trivial > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2060.patch > > > There are two classes in intg module that have incorrect logger class names. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2083) Refactor AtlasDefStore classes to reduce code duplication
[ https://issues.apache.org/jira/browse/ATLAS-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2083: Fix Version/s: 0.8.2 Committed to branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/5ca7955a > Refactor AtlasDefStore classes to reduce code duplication > --- > > Key: ATLAS-2083 > URL: https://issues.apache.org/jira/browse/ATLAS-2083 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Richard Ding >Assignee: Richard Ding > Fix For: 0.9-incubating, 0.8.2 > > Attachments: ATLAS-2083_1.patch, ATLAS-2083.patch > > > Currently each top-level TypeDef defines its own DefStore interface. These > interfaces have the same methods. I suggest that we use generic interface to > reduce the code duplication. > We can also tighten the type restriction on these interfaces. Replacing > Object reference with AtlasVertex reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2152) Saved Search: UI: Atlas UI not able to load the saved search
[
https://issues.apache.org/jira/browse/ATLAS-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2152:
Affects Version/s: (was: 0.9.1)
0.9-incubating
Fix Version/s: (was: 0.9.1)
[~ayubkhan] - there is no support for nested conditions and OR conditions in UI
(yet), hence this error.
> Saved Search: UI: Atlas UI not able to load the saved search
>
>
> Key: ATLAS-2152
> URL: https://issues.apache.org/jira/browse/ATLAS-2152
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: SavedSearchSample.json
>
>
> After saving the search query, Atlas UI unable to load the saved search.
> Below exception is observed on the browser console
> {noformat}
> CommonViewFunction.js:487 Uncaught TypeError: Cannot read property 'toJSON'
> of undefined
> at CommonViewFunction.js:487
> at Function.s.each.s.forEach (underscore-min.js:5)
> at Object.g.generateUrlFromSaveSearchObject (CommonViewFunction.js:476)
> at L.d.applyValue (SearchLayoutView.js:155)
> at L.d.stateChange (SaveSearchItemView.js:60)
> at HTMLLIElement.dispatch (jquery.min.js:3)
> at HTMLLIElement.q.handle (jquery.min.js:3)
> {noformat}
> Tested on master.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2161) UI : Save Search Query: Search button is not enabled when a saved search has only "Query" without typename / classification
[ https://issues.apache.org/jira/browse/ATLAS-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2161: Affects Version/s: (was: 0.9.1) 0.9-incubating > UI : Save Search Query: Search button is not enabled when a saved search has > only "Query" without typename / classification > --- > > Key: ATLAS-2161 > URL: https://issues.apache.org/jira/browse/ATLAS-2161 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.9-incubating, 0.8.2 > > > 1.Fired a basic search : > query = table1 (without typename and classification name). Now Search button > was enabled. > 2.Saved the search as hive_table_search. > 3.Cleared the search. > 4.Clicked on the saved search - hive_table_search. > 5.table1 was populated in the query text box. But Search button was not > enabled. > 6.But on clicking the "..." on the hive_table_search and selecting "Search" > option fired the search and fetched the entity. > This behavior is seen in both Basic and DSL search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2163) Save Search Query : Saved search query having deleted types
[ https://issues.apache.org/jira/browse/ATLAS-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2163: Affects Version/s: (was: 0.9.1) 0.9-incubating > Save Search Query : Saved search query having deleted types > --- > > Key: ATLAS-2163 > URL: https://issues.apache.org/jira/browse/ATLAS-2163 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Priority: Minor > > 1.Created a tag tag1. > 2.Fired basic search with classification name = tag1 and saved search as > "tag_basic_search" > 3.Fired DSL search with query = tag1 and saved search as "tag_DSL_search" > 4.Deleted the tag. > 5.Selected "tag_DSL_search" - this populated query text box with tag name . > Search threw invalid expression - which is expected. > 6.With Basic search ,on selecting "tag_basic_search" , no information is > populated in classification name. Classification name is null in the Basic > POST request body. > 7. Atlas displaying an error notification when selecting the saved search, > saying tag name invalid would be user friendly in case of deleted > tags/invalid tags . It is not very explicit to the user that the tag is > deleted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2151) Search using entity and trait attributes - OR condition considers only the first criterion in the list
[
https://issues.apache.org/jira/browse/ATLAS-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2151:
Affects Version/s: (was: 0.9.1)
> Search using entity and trait attributes - OR condition considers only the
> first criterion in the list
> ---
>
> Key: ATLAS-2151
> URL: https://issues.apache.org/jira/browse/ATLAS-2151
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments:
> 0002-ATLAS-2151-Surrounding-brace-fix-for-multiple-filter.patch
>
>
> 1.Created 2 hive_table entities by name : table1 and table2.
> 2. Fired basic search query with following POST body :
> {code}
> {
>"entityFilters":{
> "condition":"OR",
> "criterion":[
> {
> "attributeName":"name",
> "operator":"=",
> "attributeValue":"table1"
> },
> {
> "attributeName":"name",
> "operator":"=",
> "attributeValue":"table2"
> }
> ]
>},
>"tagFilters":null,
>"attributes":[
>],
>"query":null,
>"limit":25,
>"offset":0,
>"typeName":"hive_table",
>"classification":null,
>"excludeDeletedEntities": false
> }
> {code}
> 2. Expected the response would return both table1 and table2.
> 3. Only table1 (first filter) is returned. Any filter other than "!=" in the
> second condition doesn't fetch expected results.
> 4. Also when "excludeDeletedEntities" is set to true , though table1 and
> table2 are ACTIVE , no entity is returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2153) UI : Adding more columns to the search table masks the "Remove tag" button
[ https://issues.apache.org/jira/browse/ATLAS-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2153: Affects Version/s: (was: 0.9.1) > UI : Adding more columns to the search table masks the "Remove tag" button > --- > > Key: ATLAS-2153 > URL: https://issues.apache.org/jira/browse/ATLAS-2153 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Priority: Minor > > For basic search typename = hive_table , 20 attributes can be added in the > columns filter. When more attributes are added , "Remove Tag" (Cross button) > on the Tag under Tags column is masked. This happens when the screen size is > less and more columns are added. When columns are removed , Remove button > shows up again. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2147) querying supertype "Asset" with multiple filters fails with "unresolved datatype. Can not resolve due to unresolved children"
[
https://issues.apache.org/jira/browse/ATLAS-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-2147.
-
Resolution: Not A Problem
>From [~apoorvnaik]:
I think this is an invalid query since Asset doesn't have qualifedName as an
attribute so the data type of that can't be resolved. I ran this for a
hive_table/hive_db which seems to be working fine as it derives from Asset and
Referenceable.
> querying supertype "Asset" with multiple filters fails with "unresolved
> datatype. Can not resolve due to unresolved children"
> -
>
> Key: ATLAS-2147
> URL: https://issues.apache.org/jira/browse/ATLAS-2147
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>
> Example query with multiple filters: Asset where (name="") or
> (qualifiesName="")
> Stacktrace:
> {noformat}
> 2017-09-19 14:37:15,166 ERROR - [pool-1-thread-9 -
> 1ca16b19-634e-48bb-b872-20025c210b75:] ~ graph rollback due to exception
> (GraphTransactionInterceptor:71)
> org.apache.atlas.query.Expressions$UnresolvedException: Unresolved datatype.
> Can not resolve due to unresolved children, expression: Asset where (name =
> "h7") or (qualifiedName = "default.h7@primary")
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:708)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:706)
> at org.apache.atlas.query.Resolver.apply(Resolver.scala:48)
> at org.apache.atlas.query.Resolver.apply(Resolver.scala:25)
> at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
> at org.apache.atlas.query.Resolver.applyOrElse(Resolver.scala:25)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:201)
> at
> org.apache.atlas.query.Expressions$IdExpression.transformUp(Expressions.scala:404)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:211)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
> at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
> at scala.collection.AbstractIterator.to(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
> at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
> at scala.collection.AbstractIterator.toArray(Iterator.scala:1336)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformChildrenUp(Expressions.scala:240)
> at
> org.apache.atlas.query.Expressions$BinaryExpression.transformChildrenUp(Expressions.scala:367)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:199)
> at
> org.apache.atlas.query.Expressions$BinaryExpression.transformUp(Expressions.scala:367)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4$$anonfun$apply$3.apply(Expressions.scala:229)
> at
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
> at
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
> at scala.collection.immutable.List.map(List.scala:285)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:227)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
> at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
> at scala.collection.AbstractIterator.to(Iterator.scala:1336)
> at
>
[jira] [Updated] (ATLAS-2168) When a second search is fired in between the pages of the first search results , offset is not reset to 0
[ https://issues.apache.org/jira/browse/ATLAS-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2168: Affects Version/s: (was: 0.9.1) 0.9-incubating > When a second search is fired in between the pages of the first search > results , offset is not reset to 0 > - > > Key: ATLAS-2168 > URL: https://issues.apache.org/jira/browse/ATLAS-2168 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Critical > > 1.Created 8 hive_table entities. > 2.Created 3 hdfs_path entities. > 3. Searched for typename = hive_table , with page limit = 3. > 4. Navigated to page 3 which had 2 hive_table entities. Now offset is 6 and > limit is 3. > 5. Now fired basic search typename = hdfs_path. (without clicking Clear). > 6.Expected result table would list 3 hdfs_path entities. But no results were > fetched. Since offset is still set to 6. > 7. If Clear button was clicked before making the hdfs_path query , offset is > set to 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2164) Unable to execute the saved search query using its GUID
[
https://issues.apache.org/jira/browse/ATLAS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2164:
Affects Version/s: (was: 0.9.1)
0.9-incubating
> Unable to execute the saved search query using its GUID
> ---
>
> Key: ATLAS-2164
> URL: https://issues.apache.org/jira/browse/ATLAS-2164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created and saved 2 searches - one basic , one Advanced.
> Following is the response of /api/atlas/v2/search/saved :
> {code}
> [
>{
> "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
> "ownerName":"admin",
> "name":"basic_search1",
> "searchType":"BASIC",
> "searchParameters":{
> "query":"default",
> "typeName":"Asset",
> "classification":"tag3",
> "excludeDeletedEntities":true,
> "limit":0,
> "offset":0
> }
>},
>{
> "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
> "ownerName":"admin",
> "name":"dsl_search_1",
> "searchType":"ADVANCED",
> "searchParameters":{
> "query":"where name=\"h1\"",
> "typeName":"hdfs_path",
> "excludeDeletedEntities":true,
> "limit":0,
> "offset":0
> }
>}
> ]
> {code}
> 2.Fired the following to execute basic saved query using its GUID:
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
> {code}
> Response :
> {code}
> {
> errorCode: "ATLAS-404-00-009",
> errorMessage: "Instance __AtlasUserSavedSearch with unique attribute
> {uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
> }
> {code}
> Note : Logged in as admin while executing the "execute" query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2165) Limit set to 0 while executing saved query hence no results are fetched.
[
https://issues.apache.org/jira/browse/ATLAS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2165:
Affects Version/s: (was: 0.9.1)
0.9-incubating
> Limit set to 0 while executing saved query hence no results are fetched.
>
>
> Key: ATLAS-2165
> URL: https://issues.apache.org/jira/browse/ATLAS-2165
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Fired REST call to execute a saved query using its name :
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/basic_search1
> {code}
> Following was the response :
> {code}
> {
>guid:"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
>ownerName:"admin",
>name:"basic_search1",
>searchType:"BASIC",
>searchParameters:{
> query:"default",
> typeName:"Asset",
> classification:"tag3",
> excludeDeletedEntities:true,
> limit:0,
> offset:0
>}
> }
> {code}
> limit is set to 0 hence no entities are fetched though the query has many
> resulting entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2182) UI : Web elements are hidden when zoomed in
[ https://issues.apache.org/jira/browse/ATLAS-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185448#comment-16185448 ] Madhan Neethiraj commented on ATLAS-2182: - +1 for the patch. Thanks Keval. > UI : Web elements are hidden when zoomed in > > > Key: ATLAS-2182 > URL: https://issues.apache.org/jira/browse/ATLAS-2182 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > Attachments: ATLAS-2182.patch, Atlas_UI_zoomed_at_150%.png > > > Opened Atlas UI on Chrome . On zooming at 150% , most of the elements on > Search tab are not visible. > Attached the screenshot. At 200 % , complete left Search pane is not visible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2179) Split Atlas client library to avoid unnecessary dependencies
[ https://issues.apache.org/jira/browse/ATLAS-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2179: Affects Version/s: (was: 0.8.2) (was: 1.0.0) > Split Atlas client library to avoid unnecessary dependencies > > > Key: ATLAS-2179 > URL: https://issues.apache.org/jira/browse/ATLAS-2179 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 1.0.0, 0.8.2 > > > Currently there's one monlith client jar which bring in atlas-typesystem as > dependency for AtlasClientV1/AtlasClient which bloats up the jar size to > around 72 MB, splitting the client allows AtlasClientV2 library to be smaller > in size (27 MB) which can be reduced further by excluding more unnecessary > dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2172) Atlas AD search filter is not get honored when logging into Atlas UI
[ https://issues.apache.org/jira/browse/ATLAS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2172. - Resolution: Fixed Fix Version/s: 0.8.2 1.0.0 Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/aaeddd38 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/50980f7a > Atlas AD search filter is not get honored when logging into Atlas UI > > > Key: ATLAS-2172 > URL: https://issues.apache.org/jira/browse/ATLAS-2172 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Nixon Rodrigues >Assignee: Péter Gergő Barna > Fix For: 1.0.0, 0.8.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2147) querying supertype "Asset" with multiple filters fails with "unresolved datatype. Can not resolve due to unresolved children"
[
https://issues.apache.org/jira/browse/ATLAS-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2147:
Affects Version/s: (was: 0.9.1)
0.9-incubating
> querying supertype "Asset" with multiple filters fails with "unresolved
> datatype. Can not resolve due to unresolved children"
> -
>
> Key: ATLAS-2147
> URL: https://issues.apache.org/jira/browse/ATLAS-2147
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>
> Example query with multiple filters: Asset where (name="") or
> (qualifiesName="")
> Stacktrace:
> {noformat}
> 2017-09-19 14:37:15,166 ERROR - [pool-1-thread-9 -
> 1ca16b19-634e-48bb-b872-20025c210b75:] ~ graph rollback due to exception
> (GraphTransactionInterceptor:71)
> org.apache.atlas.query.Expressions$UnresolvedException: Unresolved datatype.
> Can not resolve due to unresolved children, expression: Asset where (name =
> "h7") or (qualifiedName = "default.h7@primary")
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:708)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:706)
> at org.apache.atlas.query.Resolver.apply(Resolver.scala:48)
> at org.apache.atlas.query.Resolver.apply(Resolver.scala:25)
> at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
> at org.apache.atlas.query.Resolver.applyOrElse(Resolver.scala:25)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:201)
> at
> org.apache.atlas.query.Expressions$IdExpression.transformUp(Expressions.scala:404)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:211)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
> at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
> at scala.collection.AbstractIterator.to(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
> at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
> at scala.collection.AbstractIterator.toArray(Iterator.scala:1336)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformChildrenUp(Expressions.scala:240)
> at
> org.apache.atlas.query.Expressions$BinaryExpression.transformChildrenUp(Expressions.scala:367)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:199)
> at
> org.apache.atlas.query.Expressions$BinaryExpression.transformUp(Expressions.scala:367)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4$$anonfun$apply$3.apply(Expressions.scala:229)
> at
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
> at
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
> at scala.collection.immutable.List.map(List.scala:285)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:227)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
> at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
> at scala.collection.AbstractIterator.to(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
> at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
> at
[jira] [Updated] (ATLAS-2147) querying supertype "Asset" with multiple filters fails with "unresolved datatype. Can not resolve due to unresolved children"
[
https://issues.apache.org/jira/browse/ATLAS-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2147:
Fix Version/s: (was: 0.9.1)
> querying supertype "Asset" with multiple filters fails with "unresolved
> datatype. Can not resolve due to unresolved children"
> -
>
> Key: ATLAS-2147
> URL: https://issues.apache.org/jira/browse/ATLAS-2147
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>
> Example query with multiple filters: Asset where (name="") or
> (qualifiesName="")
> Stacktrace:
> {noformat}
> 2017-09-19 14:37:15,166 ERROR - [pool-1-thread-9 -
> 1ca16b19-634e-48bb-b872-20025c210b75:] ~ graph rollback due to exception
> (GraphTransactionInterceptor:71)
> org.apache.atlas.query.Expressions$UnresolvedException: Unresolved datatype.
> Can not resolve due to unresolved children, expression: Asset where (name =
> "h7") or (qualifiedName = "default.h7@primary")
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:708)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:706)
> at org.apache.atlas.query.Resolver.apply(Resolver.scala:48)
> at org.apache.atlas.query.Resolver.apply(Resolver.scala:25)
> at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
> at org.apache.atlas.query.Resolver.applyOrElse(Resolver.scala:25)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:201)
> at
> org.apache.atlas.query.Expressions$IdExpression.transformUp(Expressions.scala:404)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:211)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
> at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
> at scala.collection.AbstractIterator.to(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
> at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
> at scala.collection.AbstractIterator.toArray(Iterator.scala:1336)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformChildrenUp(Expressions.scala:240)
> at
> org.apache.atlas.query.Expressions$BinaryExpression.transformChildrenUp(Expressions.scala:367)
> at
> org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:199)
> at
> org.apache.atlas.query.Expressions$BinaryExpression.transformUp(Expressions.scala:367)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4$$anonfun$apply$3.apply(Expressions.scala:229)
> at
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
> at
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
> at scala.collection.immutable.List.map(List.scala:285)
> at
> org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:227)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
> at
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
> at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
> at scala.collection.AbstractIterator.to(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
> at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
> at
> scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
> at scala.collection.AbstractIterator.toArray(Iterator.scala:1336)
>
[jira] [Updated] (ATLAS-2130) Call made to fetch tables of a database doesn't have exlcudeDeletedEntities parameter
[
https://issues.apache.org/jira/browse/ATLAS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2130:
Affects Version/s: (was: 0.9.1)
0.9-incubating
> Call made to fetch tables of a database doesn't have exlcudeDeletedEntities
> parameter
> -
>
> Key: ATLAS-2130
> URL: https://issues.apache.org/jira/browse/ATLAS-2130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>
> Following is the query fired to fetch the tables in a db :
> {code}
> http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
> {code}
> Since exlcudeDeletedEntities=true is not set in the param , deleted tables
> are also shown in the Tables tab of a hive_database's detailPage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (ATLAS-2082) Regression : Search using entity and trait attributes - Issue with capitalized string filter attributes and boolean filters
[
https://issues.apache.org/jira/browse/ATLAS-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reassigned ATLAS-2082:
---
Assignee: Madhan Neethiraj
> Regression : Search using entity and trait attributes - Issue with
> capitalized string filter attributes and boolean filters
> ---
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {
>"entityFilters":{
> "condition":"AND",
> "criterion":[
> {
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
> },
> {
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
> }
> ]
>},
>"tagFilters":null,
>"attributes":[
> "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2082) Regression : Search using entity and trait attributes - Issue with capitalized string filter attributes and boolean filters
[
https://issues.apache.org/jira/browse/ATLAS-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2082:
Attachment: ATLAS-2082.patch
Review board URL: https://reviews.apache.org/r/61854/
> Regression : Search using entity and trait attributes - Issue with
> capitalized string filter attributes and boolean filters
> ---
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {
>"entityFilters":{
> "condition":"AND",
> "criterion":[
> {
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
> },
> {
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
> }
> ]
>},
>"tagFilters":null,
>"attributes":[
> "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
