[jira] [Updated] (ATLAS-2010) Atlas Hook consumer runs into type not found
[ https://issues.apache.org/jira/browse/ATLAS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2010: --- Attachment: 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch > Atlas Hook consumer runs into type not found > > > Key: ATLAS-2010 > URL: https://issues.apache.org/jira/browse/ATLAS-2010 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 0.8-incubating, 0.8.1-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch > > > Sometimes the Hook consumer bean gets created before the type registry has > been fully initialized and when it's trying to create the entity, the type > name is missing from the registry. > Add depends on the HookConsumer class to make sure that the creation only > happens after type registry is completely bootstrapped. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2044) InMemory filtering after index query
[ https://issues.apache.org/jira/browse/ATLAS-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2044: --- Attachment: (was: 0001-ATLAS-2044-In-memory-filtering-for-correctness-after.patch) > InMemory filtering after index query > > > Key: ATLAS-2044 > URL: https://issues.apache.org/jira/browse/ATLAS-2044 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > Currently the indexing and querying is done using a StandardTokenParser which > tokenizes the string on punctuations, delimiters as a result the following > test string will pass the equality match for the actual stored string > test string: user > stored val: /foo/bar/user or /foo/bar:user > This patch adds another layer of filtering after the index query which > filters the vertices to ensure the correctness of results. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2044) InMemory filtering after index query
[ https://issues.apache.org/jira/browse/ATLAS-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2044: --- Attachment: 0001-ATLAS-2044-In-memory-filtering-for-correctness-after.patch > InMemory filtering after index query > > > Key: ATLAS-2044 > URL: https://issues.apache.org/jira/browse/ATLAS-2044 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-2044-In-memory-filtering-for-correctness-after.patch > > > Currently the indexing and querying is done using a StandardTokenParser which > tokenizes the string on punctuations, delimiters as a result the following > test string will pass the equality match for the actual stored string > test string: user > stored val: /foo/bar/user or /foo/bar:user > This patch adds another layer of filtering after the index query which > filters the vertices to ensure the correctness of results. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2044) InMemory filtering after index query
Apoorv Naik created ATLAS-2044: -- Summary: InMemory filtering after index query Key: ATLAS-2044 URL: https://issues.apache.org/jira/browse/ATLAS-2044 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Currently the indexing and querying is done using a StandardTokenParser which tokenizes the string on punctuations, delimiters as a result the following test string will pass the equality match for the actual stored string test string: user stored val: /foo/bar/user or /foo/bar:user This patch adds another layer of filtering after the index query which filters the vertices to ensure the correctness of results. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2019) Search using entity and trait attributes - Equals comparison using filter key when filter key is present between special characters
[ https://issues.apache.org/jira/browse/ATLAS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2019. Resolution: Fixed Fix Version/s: 0.8-incubating trunk > Search using entity and trait attributes - Equals comparison using filter key > when filter key is present between special characters > --- > > Key: ATLAS-2019 > URL: https://issues.apache.org/jira/browse/ATLAS-2019 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating > > > 1. Created hdfs_path entity with name = "user" , path = "/user" > 2. Created another hdfs_path with name="dir1" , path = "/user/dir1" > 3. Searched for hdfs_path , filter Path = /user > 4. The search listed down both the hdfs_path entities - user and dir1. > Expected that only "user" entity would be returned. > Here, the filter key is "/user" and if the filter key is present between > special characters in the attribute values ( "/" in this case) , all those > entities are returned. > Please note that , filter applied is "=" and not "contains" > Created few random hdfs_path entities for testing : > For the query type ="hdfs_path" and path = "/user" , entities with following > path attribute values are returned : > * user > * /user > * user/ > * /user/dir1 > * @user@dir1 > * /user@dir1 > Entities with following path values are *NOT* returned > * /userdir1 > * rootuser/dir2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1198) Move from Guice + Spring to only Spring
[ https://issues.apache.org/jira/browse/ATLAS-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1198. Resolution: Fixed Fix Version/s: 0.8.1-incubating trunk > Move from Guice + Spring to only Spring > --- > > Key: ATLAS-1198 > URL: https://issues.apache.org/jira/browse/ATLAS-1198 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk, 0.8.1-incubating > > Attachments: > 0001-ATLAS-1198-Spring-Framework-v4-with-Spring-security-.patch > > > Right now we're using both Guice and Spring and dependency injection which is > not a ideal combination. As Atlas evolves as a product we can leverage the > spring framework to avoid re-inventing the wheel like caching, transaction > management etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (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
]
Apoorv Naik reassigned ATLAS-1944:
--
Assignee: Nixon Rodrigues
Description:
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 [~]
{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
org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:215)
at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:529)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:162)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
at org.eclipse.jetty.server.Server.doStop(Server.java:456)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
{noformat}
was:
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 [~nrodrigues]
{noformat}
2017-07-12 01:26:09,743 WARN
[jira] [Updated] (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
]
Apoorv Naik updated ATLAS-1944:
---
Description:
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
org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:215)
at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:529)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:162)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
at org.eclipse.jetty.server.Server.doStop(Server.java:456)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
{noformat}
was:
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 [~]
{noformat}
2017-07-12 01:26:09,743 WARN - [pool-1-thread-1:] ~ Error
[jira] [Created] (ATLAS-1957) MultiVertex graph query
Apoorv Naik created ATLAS-1957:
--
Summary: MultiVertex graph query
Key: ATLAS-1957
URL: https://issues.apache.org/jira/browse/ATLAS-1957
Project: Atlas
Issue Type: Improvement
Affects Versions: trunk
Reporter: Apoorv Naik
Assignee: Apoorv Naik
Fix For: trunk
There are lot of use cases where the graph query needs to be executed against a
given set of vertices, right now the only way to do it to first determine a
unique indexed attribute for those and then use that as the very first has
condition filter.
e.g. graph.query().has("__guid", IN, Set guids)
This makes it difficult to perform hops in the graph traversal using the query
API alone.
Titan0 and Titan1 has the ability to perform queries on multiple vertices in
one go, which would benefit us in the future.
This enhancement will track the implementation of the MultiVertexQuery feature
across Titan0 and Titan1
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1956) AtlasSearchResult to include filter attributes by default
[ https://issues.apache.org/jira/browse/ATLAS-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1956: --- Issue Type: Improvement (was: Bug) > AtlasSearchResult to include filter attributes by default > - > > Key: ATLAS-1956 > URL: https://issues.apache.org/jira/browse/ATLAS-1956 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk > > > If no attributes are specified in the SearchParameters then by default > AtlasSearchResult should include the attributes present in the filter criteria -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1958) Better graph traversal APIs
Apoorv Naik created ATLAS-1958: -- Summary: Better graph traversal APIs Key: ATLAS-1958 URL: https://issues.apache.org/jira/browse/ATLAS-1958 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Right now the only way to perform deep/complex graph traversals is through the Gremlin API. Currently atlas has an ExpressionFactory abstraction which internally generates groovy expression as per the compatible TinkerPop version. It requires solid understanding of the TypeSystem, gremlin query structure, required optimizations etc. Instead, TinkerPop itself supports a Gremlin pipeline (TP2) and a GraphTraversal (TP3), which are good abstractions over the gremlin query language. We should have a Querying abstraction in Atlas which is agnostic to the underlying Graph implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1989) Atlas Hooks should package atlas-intg jar
Apoorv Naik created ATLAS-1989: -- Summary: Atlas Hooks should package atlas-intg jar Key: ATLAS-1989 URL: https://issues.apache.org/jira/browse/ATLAS-1989 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik The Hooks should include the atlas-intg jar so that the atlas client and the message producers can use the V2 atlas models -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1989) Atlas Hooks should package atlas-intg jar
[ https://issues.apache.org/jira/browse/ATLAS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1989: --- Attachment: 0001-ATLAS-1989-Hooks-to-include-atlas-model-classes-atla.patch > Atlas Hooks should package atlas-intg jar > - > > Key: ATLAS-1989 > URL: https://issues.apache.org/jira/browse/ATLAS-1989 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating, 0.9-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-1989-Hooks-to-include-atlas-model-classes-atla.patch > > > The Hooks should include the atlas-intg jar so that the atlas client and the > message producers can use the V2 atlas models -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1998) Missing error handling, default error page
Apoorv Naik created ATLAS-1998: -- Summary: Missing error handling, default error page Key: ATLAS-1998 URL: https://issues.apache.org/jira/browse/ATLAS-1998 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Right now there's no default error page for Atlas. Any 404 or 500 from the webpage side should direct to a default error page pointing to the index page for Atlas. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1998) Missing error handling, default error page
[ https://issues.apache.org/jira/browse/ATLAS-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1998: --- Attachment: 0001-ATLAS-1998-Default-error-page-for-404-500-and-Throwa.patch > Missing error handling, default error page > -- > > Key: ATLAS-1998 > URL: https://issues.apache.org/jira/browse/ATLAS-1998 > 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-1998-Default-error-page-for-404-500-and-Throwa.patch > > > Right now there's no default error page for Atlas. Any 404 or 500 from the > webpage side should direct to a default error page pointing to the index page > for Atlas. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2001) Invalid attribute during entity update should throw 400
Apoorv Naik created ATLAS-2001: -- Summary: Invalid attribute during entity update should throw 400 Key: ATLAS-2001 URL: https://issues.apache.org/jira/browse/ATLAS-2001 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating, trunk Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: trunk, 0.8-incubating Current implementation just ignores the invalid attributes and proceeds. Fix is to throw a bad request exception from the store. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1951) Regression: Any REST API request without user credentials results in 302 redirect to login.jsp. Actually, the correct response should be 401.
[
https://issues.apache.org/jira/browse/ATLAS-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102697#comment-16102697
]
Apoorv Naik commented on ATLAS-1951:
+1 Curl calls return 401 and browser functionality seems to be normal (no side
effect of this change). Thanks for the patch.
> Regression: Any REST API request without user credentials results in 302
> redirect to login.jsp. Actually, the correct response should be 401.
> -
>
> Key: ATLAS-1951
> URL: https://issues.apache.org/jira/browse/ATLAS-1951
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1951.patch
>
>
> Regression: Any REST API request to atlas without user credentials results in
> 302 redirect( login.jsp), but the actual response code should be 401
> unauthorized.
> This issue could have been introduced as part of new spring changes.
> For example:
> {noformat}
> curl -v -X GET "http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000;
> * Rebuilt URL to:
> http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000/
> * Trying 172.27.56.2...
> * Connected to ctr-e133-1493418528701-181199-01-02.hwx.site (172.27.56.2)
> port 21000 (#0)
> > GET / HTTP/1.1
> > Host: ctr-e133-1493418528701-181199-01-02.hwx.site:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 302 Found
> < Date: Fri, 14 Jul 2017 11:16:42 GMT
> < Set-Cookie: ATLASSESSIONID=1i0rxnm66dd3h17xyhvstk0vck;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < X-Frame-Options: DENY
> < Location:
> http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000/login.jsp
> < Content-Length: 0
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host ctr-e133-1493418528701-181199-01-02.hwx.site left
> intact
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-1994) Search API: Work with Tag attributes when query and entity filters are specified
Apoorv Naik created ATLAS-1994: -- Summary: 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: Improvement 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] [Created] (ATLAS-1966) attribute value containing @ gives inconsistent results
Apoorv Naik created ATLAS-1966: -- Summary: attribute value containing @ gives inconsistent results Key: ATLAS-1966 URL: https://issues.apache.org/jira/browse/ATLAS-1966 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1925) Bugfixes
Apoorv Naik created ATLAS-1925: -- Summary: Bugfixes Key: ATLAS-1925 URL: https://issues.apache.org/jira/browse/ATLAS-1925 Project: Atlas Issue Type: Sub-task Reporter: Apoorv Naik Assignee: Apoorv Naik This is a placeholder for all the bugs related to ATLAS-1880 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076687#comment-16076687 ] Apoorv Naik commented on ATLAS-1906: +1 Looks good to me > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076789#comment-16076789 ] Apoorv Naik commented on ATLAS-1906: Committed master : 1350067dda94e05674e1fa20018a2078ba6a63f8 0.8-incubating: edd4df08a088a03c37f88a4b53653061aeda8d5a Thanks Nixon > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1880) Search using entity and trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1880: --- Attachment: (was: 0001-ATLAS-1880-Search-using-entity-and-trait-attributes.patch) > Search using entity and trait attributes > > > Key: ATLAS-1880 > URL: https://issues.apache.org/jira/browse/ATLAS-1880 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1880-Search-using-entity-tag-attributes-multi-.patch > > > This improvement patch enhances the search experience provided by Atlas. > Currently the basic search only supports type, tag and lucene type query. > New search API will allow complex combinations of attribute search (ANDs / > ORs). The first step will be to use titan's index query on the vertex index > and then subsequently use gremlin to narrow the results if any non-indexed > attributes show up in the search request -- 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
]
Apoorv Naik updated ATLAS-2025:
---
Attachment: 0002-ATLAS-2025-Validation-of-classification-type-in-basi.patch
> 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: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
> 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] [Assigned] (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
]
Apoorv Naik reassigned ATLAS-2025:
--
Assignee: Apoorv Naik
> 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: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> 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] [Commented] (ATLAS-2026) Basic/DSL Query with invalid typeName/classification name throws 500 Internal server error
[
https://issues.apache.org/jira/browse/ATLAS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118585#comment-16118585
]
Apoorv Naik commented on ATLAS-2026:
I think it's better to do the validation in the search context itself, I've
added a patch under ATLAS-2025
> Basic/DSL Query with invalid typeName/classification name throws 500 Internal
> server error
> --
>
> Key: ATLAS-2026
> URL: https://issues.apache.org/jira/browse/ATLAS-2026
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ATLAS-2026.2.patch, ATLAS-2026.patch
>
>
> Following DSL/Basic queries with invalid classification name and type name
> throw 500 Internal server error
> {code}
> http://localhost:21000/api/atlas/v2/search/basic?typeName=unknown_type=unknown_tag
> http://localhost:21000/api/atlas/v2/search/dsl?typeName=unknown_type=unknown_tag
> {code}
> It would be appropriate to throw 40X Error code instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2001) Invalid attribute during entity update should throw 400
[ https://issues.apache.org/jira/browse/ATLAS-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2001: --- Attachment: 0001-ATLAS-2001-Invalid-attribute-during-entity-update-sh.patch > Invalid attribute during entity update should throw 400 > --- > > Key: ATLAS-2001 > URL: https://issues.apache.org/jira/browse/ATLAS-2001 > 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-2001-Invalid-attribute-during-entity-update-sh.patch > > > Current implementation just ignores the invalid attributes and proceeds. Fix > is to throw a bad request exception from the store. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (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:comment-tabpanel=16114435#comment-16114435
]
Apoorv Naik edited comment on ATLAS-2022 at 8/4/17 2:33 PM:
Committed
master: e0bd96b73d4330e221e65aae0ecb25c9fd9fdc26
0.8-incubating: 9524db197fc72a0f2f230f335027eaec88a30847
was (Author: apoorvnaik):
Committed to master: e0bd96b73d4330e221e65aae0ecb25c9fd9fdc26
> 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: Bug
> 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] [Created] (ATLAS-2024) Update Atlas Twiki
Apoorv Naik created ATLAS-2024: -- Summary: Update Atlas Twiki Key: ATLAS-2024 URL: https://issues.apache.org/jira/browse/ATLAS-2024 Project: Atlas Issue Type: Sub-task Reporter: Apoorv Naik Assignee: Apoorv Naik -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (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 ] Apoorv Naik reassigned ATLAS-2061: -- Assignee: Apoorv Naik > 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 > 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-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 ] Apoorv Naik updated ATLAS-2061: --- Attachment: 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch > 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 >Priority: Blocker > 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] [Resolved] (ATLAS-1883) Gremlin search implementation
[ https://issues.apache.org/jira/browse/ATLAS-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1883. Resolution: Done > Gremlin search implementation > - > > Key: ATLAS-1883 > URL: https://issues.apache.org/jira/browse/ATLAS-1883 > Project: Atlas > Issue Type: Sub-task >Reporter: Apoorv Naik >Assignee: Apoorv Naik > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1880) Search using entity and trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1880: --- Attachment: (was: 0001-ATLAS-1880-Search-using-entity-and-trait-attributes.patch) > Search using entity and trait attributes > > > Key: ATLAS-1880 > URL: https://issues.apache.org/jira/browse/ATLAS-1880 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1880-Search-using-entity-and-trait-attributes.patch > > > This improvement patch enhances the search experience provided by Atlas. > Currently the basic search only supports type, tag and lucene type query. > New search API will allow complex combinations of attribute search (ANDs / > ORs). The first step will be to use titan's index query on the vertex index > and then subsequently use gremlin to narrow the results if any non-indexed > attributes show up in the search request -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1880) Search using entity and trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058774#comment-16058774 ] Apoorv Naik commented on ATLAS-1880: [~grahamwallis] I think we still need to fix that (DSL inefficiency), this feature doesn't support vertex hops (yet) > Search using entity and trait attributes > > > Key: ATLAS-1880 > URL: https://issues.apache.org/jira/browse/ATLAS-1880 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1880-Search-using-entity-and-trait-attributes.patch > > > This improvement patch enhances the search experience provided by Atlas. > Currently the basic search only supports type, tag and lucene type query. > New search API will allow complex combinations of attribute search (ANDs / > ORs). The first step will be to use titan's index query on the vertex index > and then subsequently use gremlin to narrow the results if any non-indexed > attributes show up in the search request -- 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
]
Apoorv Naik updated ATLAS-2118:
---
Attachment: (was:
0001-ATLAS-2118-Issues-with-contains-in-Basic-search.patch)
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Bug
>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] [Created] (ATLAS-2138) Import capability in Atlas client
Apoorv Naik created ATLAS-2138: -- Summary: Import capability in Atlas client Key: ATLAS-2138 URL: https://issues.apache.org/jira/browse/ATLAS-2138 Project: Atlas Issue Type: Improvement Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 0.9-incubating, 0.8-incubating Enhancing the client to expose the import functionality. Will be useful for integration tests as well -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2138) Import capability in Atlas client
[ https://issues.apache.org/jira/browse/ATLAS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2138: --- Attachment: 0001-ATLAS-2138-Added-admin-import-call-to-Atlas-client.patch > Import capability in Atlas client > - > > Key: ATLAS-2138 > URL: https://issues.apache.org/jira/browse/ATLAS-2138 > Project: Atlas > Issue Type: Improvement >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 > > Attachments: > 0001-ATLAS-2138-Added-admin-import-call-to-Atlas-client.patch > > > Enhancing the client to expose the import functionality. Will be useful for > integration tests as well -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2149) Cleanup V1 typedef listener interfaces
[ https://issues.apache.org/jira/browse/ATLAS-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2149: --- Issue Type: Improvement (was: Bug) > Cleanup V1 typedef listener interfaces > -- > > Key: ATLAS-2149 > URL: https://issues.apache.org/jira/browse/ATLAS-2149 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating, 0.9-incubating, 0.8.1-incubating > > > Currently GraphBackedSearchIndexer implements typedef change listener for V1 > and V2 structures, this change removes the V1 dependency to avoid any > conflict/race during the index creation -- 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 ] Apoorv Naik updated ATLAS-2117: --- Attachment: 0001-ATLAS-2117-Work-around-for-basic-search-due-to-Titan.patch > Basic search issues due to Titan Solr schema > > > Key: ATLAS-2117 > URL: https://issues.apache.org/jira/browse/ATLAS-2117 > Project: Atlas > Issue Type: Bug >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] [Resolved] (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
]
Apoorv Naik resolved ATLAS-2028.
Resolution: Fixed
> 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: Bug
>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] [Commented] (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:comment-tabpanel=16166955#comment-16166955 ] Apoorv Naik commented on ATLAS-2091: Committed master : 6e56185209297e20169520f076f9eb3581abad89 0.8 : cb8c4a704115131a1c6a5f6e5919966969b6df57 > 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: Bug > 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-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 ] Apoorv Naik updated ATLAS-2091: --- Attachment: 0001-ATLAS-2091-Attribute-values-containing-Tokenizer-cha.patch > 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: Bug > 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] [Resolved] (ATLAS-2035) Search using entity and trait attributes - Issue with Case insensitive search in entity attributes and tag
[
https://issues.apache.org/jira/browse/ATLAS-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-2035.
Resolution: Fixed
Assignee: Apoorv Naik (was: Péter Gergő Barna)
> Search using entity and trait attributes - Issue with Case insensitive search
> in entity attributes and tag
> ---
>
> Key: ATLAS-2035
> URL: https://issues.apache.org/jira/browse/ATLAS-2035
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
>
> 1. Created an hdfs_path entity with description "hdfs_path"
> 2. Created a tag "tag1" and associated the tag to hdfs_path entity
> 3. In Basic Search
> a) Typename = hdfs_path , filter : description = hdfs_path returned the
> hdfs_path entity
> b) Typename = hdfs_path , filter : description = HDFS_PATH returned the
> hdfs_path entity (to verify case insensitivity)
>c) Typename = hdfs_path , filter : description = hdfs_path , tag = tag1
> returned the hdfs_path entity.
> d) But , Typename = hdfs_path , filter : description = HDFS_PATH , tag =
> tag1 did not fetch the entity.
> Therefore , any search with tag and case insensitive search in entityFilters
> does not fetch expected results.
> Logs from EntitySearchProcessor:
> {code}
> 2017-08-09 12:30:06,761 DEBUG - [pool-2-thread-10 -
> 56d0fb40-683d-48bb-8cf7-8d2dee690379:] ~ ==>
> EntitySearchProcessor.execute(searchParameters={query='null',
> typeName='hdfs_path', classification='tag1', excludeDeletedEntities=true,
> limit=25, offset=0, entityFilters={attributeName='null', operator=null,
> attributeValue='null', condition=AND,
> criterion=[{attributeName='description', operator=eq,
> attributeValue='HDFS_PATH', condition=null, criterion=null}]},
> tagFilters=null, attributes=null}) (EntitySearchProcessor:129)
> 2017-08-09 12:30:06,788 DEBUG - [pool-2-thread-10 -
> 56d0fb40-683d-48bb-8cf7-8d2dee690379:] ~ <==
> EntitySearchProcessor.execute(searchParameters={query='null',
> typeName='hdfs_path', classification='tag1', excludeDeletedEntities=true,
> limit=25, offset=0, entityFilters={attributeName='null', operator=null,
> attributeValue='null', condition=AND,
> criterion=[{attributeName='description', operator=eq,
> attributeValue='HDFS_PATH', condition=null, criterion=null}]},
> tagFilters=null, attributes=null}): ret.size()=0 (EntitySearchProcessor:213)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (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
]
Apoorv Naik reassigned ATLAS-2121:
--
Assignee: Apoorv Naik (was: Péter Gergő Barna)
> 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
>
> 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] [Commented] (ATLAS-2118) Basic search - Contains clause issues
[
https://issues.apache.org/jira/browse/ATLAS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166867#comment-16166867
]
Apoorv Naik commented on ATLAS-2118:
This should be extended for suffix regex matches too. And LIKE operator should
match the provided value as is (user will most likely enter a regex for LIKE)
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Bug
>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-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 ] Apoorv Naik updated ATLAS-2117: --- Attachment: (was: 0001-ATLAS-2117-Work-around-for-basic-search-due-to-Titan.patch) > Basic search issues due to Titan Solr schema > > > Key: ATLAS-2117 > URL: https://issues.apache.org/jira/browse/ATLAS-2117 > Project: Atlas > Issue Type: Bug >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] [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 ] Apoorv Naik updated ATLAS-2117: --- Attachment: 0001-ATLAS-2117-Work-around-for-basic-search-due-to-Titan.patch > Basic search issues due to Titan Solr schema > > > Key: ATLAS-2117 > URL: https://issues.apache.org/jira/browse/ATLAS-2117 > Project: Atlas > Issue Type: Bug >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] [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
]
Apoorv Naik updated ATLAS-2118:
---
Attachment: 0001-ATLAS-2118-Issues-with-contains-in-Basic-search.patch
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Bug
>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] [Assigned] (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
]
Apoorv Naik reassigned ATLAS-2151:
--
Assignee: Apoorv Naik
> 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, 0.9.1
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
>
> 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] [Assigned] (ATLAS-2198) HiveHook fails with OOM when hive view with 500 columns are created.
[
https://issues.apache.org/jira/browse/ATLAS-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik reassigned ATLAS-2198:
--
Assignee: Apoorv Naik
> HiveHook fails with OOM when hive view with 500 columns are created.
>
>
> Key: ATLAS-2198
> URL: https://issues.apache.org/jira/browse/ATLAS-2198
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8.2
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.8.2
>
>
> create below two commands with hivehook enabled, hiveHook fails with OOM.
> {noformat}
> create table t1_500(col0 string, col1 string, col2 string, col3 string, col4
> string, col5 string, col6 string, col7 string, col8 string, col9 string,
> col10 string, col11 string, col12 string, col13 string, col14 string, col15
> string, col16 string, col17 string, col18 string, col19 string, col20 string,
> col21 string, col22 string, col23 string, col24 string, col25 string, col26
> string, col27 string, col28 string, col29 string, col30 string, col31 string,
> col32 string, col33 string, col34 string, col35 string, col36 string, col37
> string, col38 string, col39 string, col40 string, col41 string, col42 string,
> col43 string, col44 string, col45 string, col46 string, col47 string, col48
> string, col49 string, col50 string, col51 string, col52 string, col53 string,
> col54 string, col55 string, col56 string, col57 string, col58 string, col59
> string, col60 string, col61 string, col62 string, col63 string, col64 string,
> col65 string, col66 string, col67 string, col68 string, col69 string, col70
> string, col71 string, col72 string, col73 string, col74 string, col75 string,
> col76 string, col77 string, col78 string, col79 string, col80 string, col81
> string, col82 string, col83 string, col84 string, col85 string, col86 string,
> col87 string, col88 string, col89 string, col90 string, col91 string, col92
> string, col93 string, col94 string, col95 string, col96 string, col97 string,
> col98 string, col99 string, col100 string, col101 string, col102 string,
> col103 string, col104 string, col105 string, col106 string, col107 string,
> col108 string, col109 string, col110 string, col111 string, col112 string,
> col113 string, col114 string, col115 string, col116 string, col117 string,
> col118 string, col119 string, col120 string, col121 string, col122 string,
> col123 string, col124 string, col125 string, col126 string, col127 string,
> col128 string, col129 string, col130 string, col131 string, col132 string,
> col133 string, col134 string, col135 string, col136 string, col137 string,
> col138 string, col139 string, col140 string, col141 string, col142 string,
> col143 string, col144 string, col145 string, col146 string, col147 string,
> col148 string, col149 string, col150 string, col151 string, col152 string,
> col153 string, col154 string, col155 string, col156 string, col157 string,
> col158 string, col159 string, col160 string, col161 string, col162 string,
> col163 string, col164 string, col165 string, col166 string, col167 string,
> col168 string, col169 string, col170 string, col171 string, col172 string,
> col173 string, col174 string, col175 string, col176 string, col177 string,
> col178 string, col179 string, col180 string, col181 string, col182 string,
> col183 string, col184 string, col185 string, col186 string, col187 string,
> col188 string, col189 string, col190 string, col191 string, col192 string,
> col193 string, col194 string, col195 string, col196 string, col197 string,
> col198 string, col199 string, col200 string, col201 string, col202 string,
> col203 string, col204 string, col205 string, col206 string, col207 string,
> col208 string, col209 string, col210 string, col211 string, col212 string,
> col213 string, col214 string, col215 string, col216 string, col217 string,
> col218 string, col219 string, col220 string, col221 string, col222 string,
> col223 string, col224 string, col225 string, col226 string, col227 string,
> col228 string, col229 string, col230 string, col231 string, col232 string,
> col233 string, col234 string, col235 string, col236 string, col237 string,
> col238 string, col239 string, col240 string, col241 string, col242 string,
> col243 string, col244 string, col245 string, col246 string, col247 string,
> col248 string, col249 string, col250 string, col251 string, col252 string,
> col253 string, col254 string, col255 string, col256 string, col257 string,
> col258 string, col259 string, col260 string, col261 string, col262 string,
> col263 string, col264 string, col265 string, col266 string, col267 string,
> col268 string, col269 string, col270 string, col271 string, col272 string,
> col273
[jira] [Updated] (ATLAS-2198) HiveHook fails with OOM when hive view with 500 columns are created.
[
https://issues.apache.org/jira/browse/ATLAS-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2198:
---
Attachment: 0001-ATLAS-2198-Hive-Hook-OOM-fix.patch
> HiveHook fails with OOM when hive view with 500 columns are created.
>
>
> Key: ATLAS-2198
> URL: https://issues.apache.org/jira/browse/ATLAS-2198
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8.2
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.8.2
>
> Attachments: 0001-ATLAS-2198-Hive-Hook-OOM-fix.patch
>
>
> create below two commands with hivehook enabled, hiveHook fails with OOM.
> {noformat}
> create table t1_500(col0 string, col1 string, col2 string, col3 string, col4
> string, col5 string, col6 string, col7 string, col8 string, col9 string,
> col10 string, col11 string, col12 string, col13 string, col14 string, col15
> string, col16 string, col17 string, col18 string, col19 string, col20 string,
> col21 string, col22 string, col23 string, col24 string, col25 string, col26
> string, col27 string, col28 string, col29 string, col30 string, col31 string,
> col32 string, col33 string, col34 string, col35 string, col36 string, col37
> string, col38 string, col39 string, col40 string, col41 string, col42 string,
> col43 string, col44 string, col45 string, col46 string, col47 string, col48
> string, col49 string, col50 string, col51 string, col52 string, col53 string,
> col54 string, col55 string, col56 string, col57 string, col58 string, col59
> string, col60 string, col61 string, col62 string, col63 string, col64 string,
> col65 string, col66 string, col67 string, col68 string, col69 string, col70
> string, col71 string, col72 string, col73 string, col74 string, col75 string,
> col76 string, col77 string, col78 string, col79 string, col80 string, col81
> string, col82 string, col83 string, col84 string, col85 string, col86 string,
> col87 string, col88 string, col89 string, col90 string, col91 string, col92
> string, col93 string, col94 string, col95 string, col96 string, col97 string,
> col98 string, col99 string, col100 string, col101 string, col102 string,
> col103 string, col104 string, col105 string, col106 string, col107 string,
> col108 string, col109 string, col110 string, col111 string, col112 string,
> col113 string, col114 string, col115 string, col116 string, col117 string,
> col118 string, col119 string, col120 string, col121 string, col122 string,
> col123 string, col124 string, col125 string, col126 string, col127 string,
> col128 string, col129 string, col130 string, col131 string, col132 string,
> col133 string, col134 string, col135 string, col136 string, col137 string,
> col138 string, col139 string, col140 string, col141 string, col142 string,
> col143 string, col144 string, col145 string, col146 string, col147 string,
> col148 string, col149 string, col150 string, col151 string, col152 string,
> col153 string, col154 string, col155 string, col156 string, col157 string,
> col158 string, col159 string, col160 string, col161 string, col162 string,
> col163 string, col164 string, col165 string, col166 string, col167 string,
> col168 string, col169 string, col170 string, col171 string, col172 string,
> col173 string, col174 string, col175 string, col176 string, col177 string,
> col178 string, col179 string, col180 string, col181 string, col182 string,
> col183 string, col184 string, col185 string, col186 string, col187 string,
> col188 string, col189 string, col190 string, col191 string, col192 string,
> col193 string, col194 string, col195 string, col196 string, col197 string,
> col198 string, col199 string, col200 string, col201 string, col202 string,
> col203 string, col204 string, col205 string, col206 string, col207 string,
> col208 string, col209 string, col210 string, col211 string, col212 string,
> col213 string, col214 string, col215 string, col216 string, col217 string,
> col218 string, col219 string, col220 string, col221 string, col222 string,
> col223 string, col224 string, col225 string, col226 string, col227 string,
> col228 string, col229 string, col230 string, col231 string, col232 string,
> col233 string, col234 string, col235 string, col236 string, col237 string,
> col238 string, col239 string, col240 string, col241 string, col242 string,
> col243 string, col244 string, col245 string, col246 string, col247 string,
> col248 string, col249 string, col250 string, col251 string, col252 string,
> col253 string, col254 string, col255 string, col256 string, col257 string,
> col258 string, col259 string, col260 string, col261 string, col262 string,
> col263 string, col264 string, col265 string, col266 string, col267 string,
>
[jira] [Commented] (ATLAS-2211) Dangling transaction in GraphBackedMetadataRepository
[ https://issues.apache.org/jira/browse/ATLAS-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204158#comment-16204158 ] Apoorv Naik commented on ATLAS-2211: Committed: master : https://github.com/apache/atlas/commit/a3bafb1e75a55e894cefc3f995e21ee2ffcb749b branch-0.8 : https://github.com/apache/atlas/commit/816c9c72dda4521a638b889ede7c3e04f0c598a4 > Dangling transaction in GraphBackedMetadataRepository > - > > Key: ATLAS-2211 > URL: https://issues.apache.org/jira/browse/ATLAS-2211 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating > > > Caused by change in ATLAS-1955 to > GraphBackedMetadataRepository.getEntityByID(guid) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2211) Dangling transaction in GraphBackedMetadataRepository
[ https://issues.apache.org/jira/browse/ATLAS-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2211. Resolution: Fixed Fix Version/s: 0.8-incubating trunk > Dangling transaction in GraphBackedMetadataRepository > - > > Key: ATLAS-2211 > URL: https://issues.apache.org/jira/browse/ATLAS-2211 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating > > > Caused by change in ATLAS-1955 to > GraphBackedMetadataRepository.getEntityByID(guid) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2211) Dangling transaction in GraphBackedMetadataRepository
[ https://issues.apache.org/jira/browse/ATLAS-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2211: --- Description: Caused by change in ATLAS-1995 to GraphBackedMetadataRepository.getEntityByID(guid) (was: Caused by change in ATLAS-1955 to GraphBackedMetadataRepository.getEntityByID(guid) ) > Dangling transaction in GraphBackedMetadataRepository > - > > Key: ATLAS-2211 > URL: https://issues.apache.org/jira/browse/ATLAS-2211 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating > > > Caused by change in ATLAS-1995 to > GraphBackedMetadataRepository.getEntityByID(guid) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2211) Dangling transaction in GraphBackedMetadataRepository
Apoorv Naik created ATLAS-2211: -- Summary: Dangling transaction in GraphBackedMetadataRepository Key: ATLAS-2211 URL: https://issues.apache.org/jira/browse/ATLAS-2211 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Caused by change in ATLAS-1955 to GraphBackedMetadataRepository.getEntityByID(guid) -- 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 ] Apoorv Naik updated ATLAS-2117: --- Summary: Basic search issues due to Titan Solr schema (was: Titan Indexer tokenization issues) > Basic search issues due to Titan Solr schema > > > Key: ATLAS-2117 > URL: https://issues.apache.org/jira/browse/ATLAS-2117 > Project: Atlas > Issue Type: Bug >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 > > > 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] [Updated] (ATLAS-2115) Regression: Basic search performance
[ https://issues.apache.org/jira/browse/ATLAS-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2115: --- Attachment: 0001-ATLAS-2115-Basic-search-regression-fix.patch > 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: trunk, 0.8-incubating, 0.8.1-incubating > > Attachments: 0001-ATLAS-2115-Basic-search-regression-fix.patch > > > 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] [Created] (ATLAS-2117) Titan Indexer tokenization issues
Apoorv Naik created ATLAS-2117: -- Summary: Titan Indexer tokenization issues Key: ATLAS-2117 URL: https://issues.apache.org/jira/browse/ATLAS-2117 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 0.9-incubating, 0.8.1-incubating, 0.8-incubating 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] [Assigned] (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 ] Apoorv Naik reassigned ATLAS-2091: -- Assignee: Apoorv Naik > 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: Bug > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik > > 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] [Assigned] (ATLAS-2057) Attributes filter does not show the attribute and value if the value of that attribute is null
[
https://issues.apache.org/jira/browse/ATLAS-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik reassigned ATLAS-2057:
--
Assignee: Apoorv Naik
> Attributes filter does not show the attribute and value if the value of that
> attribute is null
> --
>
> Key: ATLAS-2057
> URL: https://issues.apache.org/jira/browse/ATLAS-2057
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>
> 1.Created a hive_table.
> 2. Few attributes like aliases , partitionKeys , viewOriginalText ,
> viewExpandedText , description had null values.
> 3. Fired a basic query with following POST body :
> {code}
> {
> "entityFilters":null
> "tagFilters":null,
> "attributes":["viewExpandedText","comment","retention","aliases"],
> "query":null,
> "excludeDeletedEntities":true,
> "limit":25,
> "typeName":"hive_table",
> "classification":null
> }
> {code}
> Following is the response :
> {code}
> {
> "queryType": "BASIC",
> "searchParameters": {
> "typeName": "hive_table",
> "excludeDeletedEntities": true,
> "limit": 25,
> "offset": 0,
> "entityFilters":null,
> "attributes": [
> "viewExpandedText",
> "aliases",
> "comment",
> "retention"
> ]
> },
> "entities": [
> {
> "typeName": "hive_table",
> "attributes": {
> "owner": "hrt_qa",
> "qualifiedName": "db_h189c6z0eu.table_12_h189c6z0eu@cl1",
> "name": "table_12_h189c6z0eu",
> "description": null,
> "retention": 0
> },
> "guid": "c1a1362d-75f8-42a9-8ad8-3792ecc75018",
> "status": "ACTIVE",
> "displayText": "table_12_h189c6z0eu",
> "classificationNames": []
> }
> ]
> }
> {code}
> In the "attributes" key value , only retention is seen because it has
> non-null value. Other null valued attributes are ignored.
> If response has 2 entities and the second hive_table entity has non-null
> values for aliases , partitionKeys , viewOriginalText , viewExpandedText ,
> the attribute along with non-null value is fetched in the response. It can be
> confusing as why for one hive_table entity few attributes are not retrieved.
> It is fine from the UI since the attribute name is shown and the value is
> empty for null valued attributes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ATLAS-2001) Invalid attribute during entity update should throw 400
[ https://issues.apache.org/jira/browse/ATLAS-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2001. Resolution: Not A Bug > Invalid attribute during entity update should throw 400 > --- > > Key: ATLAS-2001 > URL: https://issues.apache.org/jira/browse/ATLAS-2001 > 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-2001-Invalid-attribute-during-entity-update-sh.patch > > > Current implementation just ignores the invalid attributes and proceeds. Fix > is to throw a bad request exception from the store. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-2113) [Regression] Basic search
[ https://issues.apache.org/jira/browse/ATLAS-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2113. Resolution: Duplicate > [Regression] Basic search > - > > Key: ATLAS-2113 > URL: https://issues.apache.org/jira/browse/ATLAS-2113 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.9-incubating > > > The REST call timings for the use-case when only classification is specified > have regressed after introduction of ATLAS-1880. This JIRA will track all > such use-cases and provide a code fix (if possible) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2118) Basic search - Contains clause issues
[
https://issues.apache.org/jira/browse/ATLAS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157230#comment-16157230
]
Apoorv Naik commented on ATLAS-2118:
Surprisingly the right hand counterparts were working fine with the index, I
think the regex sees the left hand versions and then starts expecting a right
hand one for the the same and errors out.
I'll run some more tests to make sure that it works as intended.
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Bug
>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] [Created] (ATLAS-2118) Basic search - Contains clause issues
Apoorv Naik created ATLAS-2118:
--
Summary: Basic search - Contains clause issues
Key: ATLAS-2118
URL: https://issues.apache.org/jira/browse/ATLAS-2118
Project: Atlas
Issue Type: Bug
Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
Reporter: Apoorv Naik
Assignee: Apoorv Naik
Fix For: 0.9-incubating, 0.8.1-incubating, 0.8-incubating
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-2115) Regression: Basic search performance
[ https://issues.apache.org/jira/browse/ATLAS-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2115: --- Attachment: (was: 0001-ATLAS-2115-Basic-search-regression-fix.patch) > 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: trunk, 0.8-incubating, 0.8.1-incubating > > > 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-2118) Basic search - Contains clause issues
[
https://issues.apache.org/jira/browse/ATLAS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2118:
---
Attachment: (was:
0001-ATLAS-2118-Issues-with-contains-in-Basic-search.patch)
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Bug
>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
>
>
> 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-2118) Basic search - Contains clause issues
[
https://issues.apache.org/jira/browse/ATLAS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2118:
---
Attachment: 0001-ATLAS-2118-Issues-with-contains-in-Basic-search.patch
> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
> Issue Type: Bug
>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] [Created] (ATLAS-2115) Regression: Basic search performance
Apoorv Naik created ATLAS-2115: -- Summary: 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: trunk, 0.8.1-incubating, 0.8-incubating 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] [Created] (ATLAS-2179) Split Atlas client library to avoid unnecessary dependencies
Apoorv Naik created ATLAS-2179: -- Summary: 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 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-2180) Regression : Hive hook is broken
[
https://issues.apache.org/jira/browse/ATLAS-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-2180.
Resolution: Fixed
Assignee: Apoorv Naik (was: Péter Gergő Barna)
Fix Version/s: 0.8-incubating
trunk
> Regression : Hive hook is broken
>
>
> Key: ATLAS-2180
> URL: https://issues.apache.org/jira/browse/ATLAS-2180
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
>
> Hive table creation succeeded but while invoking Atlas hook , following error
> message seen in hive logs :
> {code}
> 2017-09-27 06:29:26,084 INFO [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:collect(244)) - Entered Atlas hook for hook type
> POST_EXEC_HOOK, operation CREATETABLE , user null as hive
> 2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) - method=releaseLocks from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=releaseLocks start=1506493766084 end=1506493766084 duration=0
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,085 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=Driver.run start=1506493763780 end=1506493766085 duration=2305
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(205)) - Atlas hook failed due to error
> java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
> at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
> 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)
> 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: java.lang.ClassNotFoundException:
> org.apache.atlas.AtlasServiceException
> at java.lang.ClassLoader.findClass(ClassLoader.java:530)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (ATLAS-2155) Attributes with null values are not filtered using search parameters
[
https://issues.apache.org/jira/browse/ATLAS-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik reassigned ATLAS-2155:
--
Assignee: Apoorv Naik (was: Péter Gergő Barna)
> Attributes with null values are not filtered using search parameters
>
>
> Key: ATLAS-2155
> URL: https://issues.apache.org/jira/browse/ATLAS-2155
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>
> For example: Below example shows attrbutes like "Description" has nullvalues
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
> '{"excludeDeletedEntities":true,"entityFilters":{"condition":"AND","criterion":[{"attributeName":"owner","operator":"eq","attributeValue":"apathan"}]},"tagFilters":null,"attributes":["qualifiedName"],"query":null,"limit":25,"offset":0,"typeName":"hive_table","classification":null}'
> --compressed | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 11050 825 100 280 13953 4735 --:--:-- --:--:-- --:--:-- 14224
> {
> "entities": [
> {
> "attributes": {
> "createTime": 1505475604641,
> "description": null,
> "name": "h5",
> "owner": "apathan",
> "qualifiedName": "default.h5@primary"
> },
> "classificationNames": [],
> "displayText": "h5",
> "guid": "7a8955bf-7395-454f-9d67-ea3ba01529bf",
> "status": "ACTIVE",
> "typeName": "hive_table"
> },
> {
> "attributes": {
> "createTime": 1505475721717,
> "description": null,
> "name": "h7",
> "owner": "apathan",
> "qualifiedName": "default.h7@primary"
> },
> "classificationNames": [
> "abc",
> "dsfads",
> "sdf"
> ],
> "displayText": "h7",
> "guid": "82d6de4e-d808-4c88-8207-be5a58fbbb4e",
> "status": "ACTIVE",
> "typeName": "hive_table"
> }
> ],
> "queryType": "BASIC",
> "searchParameters": {
> "attributes": [
> "qualifiedName"
> ],
> "entityFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "owner",
> "attributeValue": "apathan",
> "operator": "eq"
> }
> ]
> },
> "excludeDeletedEntities": true,
> "limit": 25,
> "offset": 0,
> "typeName": "hive_table"
> }
> }
> {noformat}
> *Filtering those attributes using any operand will not take effect and it
> will always result empty response*
> example:
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
>
[jira] [Commented] (ATLAS-2155) Attributes with null values are not filtered using search parameters
[
https://issues.apache.org/jira/browse/ATLAS-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182923#comment-16182923
]
Apoorv Naik commented on ATLAS-2155:
[~bpgergo] - I'm already working on verifying the fix, reassigning to myself.
> Attributes with null values are not filtered using search parameters
>
>
> Key: ATLAS-2155
> URL: https://issues.apache.org/jira/browse/ATLAS-2155
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Ayub Pathan
>Assignee: Péter Gergő Barna
>
> For example: Below example shows attrbutes like "Description" has nullvalues
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
> '{"excludeDeletedEntities":true,"entityFilters":{"condition":"AND","criterion":[{"attributeName":"owner","operator":"eq","attributeValue":"apathan"}]},"tagFilters":null,"attributes":["qualifiedName"],"query":null,"limit":25,"offset":0,"typeName":"hive_table","classification":null}'
> --compressed | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 11050 825 100 280 13953 4735 --:--:-- --:--:-- --:--:-- 14224
> {
> "entities": [
> {
> "attributes": {
> "createTime": 1505475604641,
> "description": null,
> "name": "h5",
> "owner": "apathan",
> "qualifiedName": "default.h5@primary"
> },
> "classificationNames": [],
> "displayText": "h5",
> "guid": "7a8955bf-7395-454f-9d67-ea3ba01529bf",
> "status": "ACTIVE",
> "typeName": "hive_table"
> },
> {
> "attributes": {
> "createTime": 1505475721717,
> "description": null,
> "name": "h7",
> "owner": "apathan",
> "qualifiedName": "default.h7@primary"
> },
> "classificationNames": [
> "abc",
> "dsfads",
> "sdf"
> ],
> "displayText": "h7",
> "guid": "82d6de4e-d808-4c88-8207-be5a58fbbb4e",
> "status": "ACTIVE",
> "typeName": "hive_table"
> }
> ],
> "queryType": "BASIC",
> "searchParameters": {
> "attributes": [
> "qualifiedName"
> ],
> "entityFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "owner",
> "attributeValue": "apathan",
> "operator": "eq"
> }
> ]
> },
> "excludeDeletedEntities": true,
> "limit": 25,
> "offset": 0,
> "typeName": "hive_table"
> }
> }
> {noformat}
> *Filtering those attributes using any operand will not take effect and it
> will always result empty response*
> example:
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
>
[jira] [Updated] (ATLAS-2155) Attributes with null values are not filtered using search parameters
[
https://issues.apache.org/jira/browse/ATLAS-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2155:
---
Attachment: 0001-ATLAS-2155-Allow-null-NEQ-comparisons-for-String.patch
> Attributes with null values are not filtered using search parameters
>
>
> Key: ATLAS-2155
> URL: https://issues.apache.org/jira/browse/ATLAS-2155
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
> Attachments:
> 0001-ATLAS-2155-Allow-null-NEQ-comparisons-for-String.patch
>
>
> For example: Below example shows attrbutes like "Description" has nullvalues
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
> '{"excludeDeletedEntities":true,"entityFilters":{"condition":"AND","criterion":[{"attributeName":"owner","operator":"eq","attributeValue":"apathan"}]},"tagFilters":null,"attributes":["qualifiedName"],"query":null,"limit":25,"offset":0,"typeName":"hive_table","classification":null}'
> --compressed | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 11050 825 100 280 13953 4735 --:--:-- --:--:-- --:--:-- 14224
> {
> "entities": [
> {
> "attributes": {
> "createTime": 1505475604641,
> "description": null,
> "name": "h5",
> "owner": "apathan",
> "qualifiedName": "default.h5@primary"
> },
> "classificationNames": [],
> "displayText": "h5",
> "guid": "7a8955bf-7395-454f-9d67-ea3ba01529bf",
> "status": "ACTIVE",
> "typeName": "hive_table"
> },
> {
> "attributes": {
> "createTime": 1505475721717,
> "description": null,
> "name": "h7",
> "owner": "apathan",
> "qualifiedName": "default.h7@primary"
> },
> "classificationNames": [
> "abc",
> "dsfads",
> "sdf"
> ],
> "displayText": "h7",
> "guid": "82d6de4e-d808-4c88-8207-be5a58fbbb4e",
> "status": "ACTIVE",
> "typeName": "hive_table"
> }
> ],
> "queryType": "BASIC",
> "searchParameters": {
> "attributes": [
> "qualifiedName"
> ],
> "entityFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "owner",
> "attributeValue": "apathan",
> "operator": "eq"
> }
> ]
> },
> "excludeDeletedEntities": true,
> "limit": 25,
> "offset": 0,
> "typeName": "hive_table"
> }
> }
> {noformat}
> *Filtering those attributes using any operand will not take effect and it
> will always result empty response*
> example:
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
>
[jira] [Commented] (ATLAS-2155) Attributes with null values are not filtered using search parameters
[
https://issues.apache.org/jira/browse/ATLAS-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16186155#comment-16186155
]
Apoorv Naik commented on ATLAS-2155:
Closing this as "Works as designed", for doing isNull/notNull checks we've
introduced new operators in ATLAS-2184
> Attributes with null values are not filtered using search parameters
>
>
> Key: ATLAS-2155
> URL: https://issues.apache.org/jira/browse/ATLAS-2155
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
> Attachments:
> 0001-ATLAS-2155-Allow-null-NEQ-comparisons-for-String.patch
>
>
> For example: Below example shows attrbutes like "Description" has nullvalues
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
> '{"excludeDeletedEntities":true,"entityFilters":{"condition":"AND","criterion":[{"attributeName":"owner","operator":"eq","attributeValue":"apathan"}]},"tagFilters":null,"attributes":["qualifiedName"],"query":null,"limit":25,"offset":0,"typeName":"hive_table","classification":null}'
> --compressed | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 11050 825 100 280 13953 4735 --:--:-- --:--:-- --:--:-- 14224
> {
> "entities": [
> {
> "attributes": {
> "createTime": 1505475604641,
> "description": null,
> "name": "h5",
> "owner": "apathan",
> "qualifiedName": "default.h5@primary"
> },
> "classificationNames": [],
> "displayText": "h5",
> "guid": "7a8955bf-7395-454f-9d67-ea3ba01529bf",
> "status": "ACTIVE",
> "typeName": "hive_table"
> },
> {
> "attributes": {
> "createTime": 1505475721717,
> "description": null,
> "name": "h7",
> "owner": "apathan",
> "qualifiedName": "default.h7@primary"
> },
> "classificationNames": [
> "abc",
> "dsfads",
> "sdf"
> ],
> "displayText": "h7",
> "guid": "82d6de4e-d808-4c88-8207-be5a58fbbb4e",
> "status": "ACTIVE",
> "typeName": "hive_table"
> }
> ],
> "queryType": "BASIC",
> "searchParameters": {
> "attributes": [
> "qualifiedName"
> ],
> "entityFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "owner",
> "attributeValue": "apathan",
> "operator": "eq"
> }
> ]
> },
> "excludeDeletedEntities": true,
> "limit": 25,
> "offset": 0,
> "typeName": "hive_table"
> }
> }
> {noformat}
> *Filtering those attributes using any operand will not take effect and it
> will always result empty response*
> example:
> {noformat}
> apathan@Ayub-sys-101:~/Hortonworks > curl
> 'http://localhost:21000/api/atlas/v2/search/basic' -H 'Origin:
> http://localhost:21000' -H 'Accept-Encoding: gzip, deflate, br' -H
> 'X-XSRF-HEADER: ""' -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H
> 'Accept-Language: en-US,en;q=0.8' -H 'Cookie:
> ATLASSESSIONID=9hm04vl07k7f1vmcmeq9q6kg9' -H 'Connection: keep-alive' -H
> 'Pragma: no-cache' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent:
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/60.0.3112.113 Safari/537.36' -H 'Content-Type:
> application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01'
> -H 'Cache-Control: no-cache' -H 'Referer: http://localhost:21000/index.html'
> --data-binary
>
[jira] [Commented] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062
[ https://issues.apache.org/jira/browse/ATLAS-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138658#comment-16138658 ] Apoorv Naik commented on ATLAS-2079: +1 Changes look good. > Fix IT failures introduced by ATLAS-2062 > > > Key: ATLAS-2079 > URL: https://issues.apache.org/jira/browse/ATLAS-2079 > Project: Atlas > Issue Type: Bug > Components: atlas-core >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-2079.2.patch > > > Fix for coverity scan issues and following IT failures: > Failed tests: > > NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 > » AtlasService > > NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 > » > EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> > MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » > AtlasService Me... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2012) Docker - image & hub - for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140948#comment-16140948 ] Apoorv Naik commented on ATLAS-2012: [~jonesn] [~davidrad] I think this is a very good addition to Atlas. Maybe down the line we can start building docker images as soon as a commit goes in and publish. That way it will be easier for other folks to test out the changes as well. IT runs are non-consistent and Sarath has been trying to fix it for a while now, but now and then we do run into intermittent failures either in webapp or in Hive module. > Docker - image & hub - for Atlas > > > Key: ATLAS-2012 > URL: https://issues.apache.org/jira/browse/ATLAS-2012 > Project: Atlas > Issue Type: New Feature >Reporter: Nigel Jones >Assignee: Nigel Jones > Attachments: atlas_docker1.patch, atlas_docker_2.patch, > atlas_docker.patch > > > Docker is increasingly become a standard way of easily running components in > a flexible manner, whether for development, production, or test > I feel there are a few things we can do with docker that will aid Atlas's > appeal > 1. We could provide a simple example of how to create a docker image from the > Atlas build. This could be published on the wiki & it would make it easier > for developers to use Atlas within a docker environment - mostly by > addressing how to configure & start up > 2. We could automatically generate a docker image as part of the build > process. This builds on #1 by automating the creation of the image & making > it "just part of the build" > 3. We could publish the docker image from #2, for releases, to dockerhub, > making it near trivial for any developer to easily pull down and experiment > with Atlas. Full source of course would be provided/documented so that a user > could customize as needed for their environment plus of course improve what > is provided with the core project > 4. We could work with other teams especially ranger, to allow similar efforts > in other teams to easily work together & be orchestrated -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2113) [Regression] Basic search
Apoorv Naik created ATLAS-2113: -- Summary: [Regression] Basic search Key: ATLAS-2113 URL: https://issues.apache.org/jira/browse/ATLAS-2113 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 0.9-incubating The REST call timings for the use-case when only classification is specified have regressed after introduction of ATLAS-1880. This JIRA will track all such use-cases and provide a code fix (if possible) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2207) Test property fixes
Apoorv Naik created ATLAS-2207: -- Summary: Test property fixes Key: ATLAS-2207 URL: https://issues.apache.org/jira/browse/ATLAS-2207 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik In one of the recent commits, atlas-application.properties under typesystem/src/test/resources was accidentally modified this resulted in IT failures on branch-0.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2207) Test property fixes
[ https://issues.apache.org/jira/browse/ATLAS-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201494#comment-16201494 ] Apoorv Naik commented on ATLAS-2207: Committed: https://github.com/apache/atlas/commit/a05384870ce06548bd564ffc1962653b133e8b82 > Test property fixes > --- > > Key: ATLAS-2207 > URL: https://issues.apache.org/jira/browse/ATLAS-2207 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > In one of the recent commits, atlas-application.properties under > typesystem/src/test/resources was accidentally modified this resulted in IT > failures on branch-0.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2201) Test dependency and plugin fixes
[ https://issues.apache.org/jira/browse/ATLAS-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2201: --- Attachment: 0001-ATLAS-2201-Test-dependency-plugin-version-and-test-c.patch Patch for branch-0.8 > Test dependency and plugin fixes > > > Key: ATLAS-2201 > URL: https://issues.apache.org/jira/browse/ATLAS-2201 > 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-2201-Test-dependency-plugin-version-and-test-c.patch > > > Atlas is running a really old version of TestNG and any change to the > dependency version (inevitable in the future) causes the test ordering to > change and hence the assertions fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2201) Test dependency and plugin fixes
Apoorv Naik created ATLAS-2201: -- Summary: Test dependency and plugin fixes Key: ATLAS-2201 URL: https://issues.apache.org/jira/browse/ATLAS-2201 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Atlas is running a really old version of TestNG and any change to the dependency version (inevitable in the future) causes the test ordering to change and hence the assertions fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2198) HiveHook fails with OOM when hive view with 500 columns are created.
[
https://issues.apache.org/jira/browse/ATLAS-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2198:
---
Attachment: (was: 0001-ATLAS-2198-Hive-Hook-OOM-fix.patch)
> HiveHook fails with OOM when hive view with 500 columns are created.
>
>
> Key: ATLAS-2198
> URL: https://issues.apache.org/jira/browse/ATLAS-2198
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8.2
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.8.2
>
> Attachments: 0001-ATLAS-2198-Hive-Hook-OOM-fix.patch
>
>
> create below two commands with hivehook enabled, hiveHook fails with OOM.
> {noformat}
> create table t1_500(col0 string, col1 string, col2 string, col3 string, col4
> string, col5 string, col6 string, col7 string, col8 string, col9 string,
> col10 string, col11 string, col12 string, col13 string, col14 string, col15
> string, col16 string, col17 string, col18 string, col19 string, col20 string,
> col21 string, col22 string, col23 string, col24 string, col25 string, col26
> string, col27 string, col28 string, col29 string, col30 string, col31 string,
> col32 string, col33 string, col34 string, col35 string, col36 string, col37
> string, col38 string, col39 string, col40 string, col41 string, col42 string,
> col43 string, col44 string, col45 string, col46 string, col47 string, col48
> string, col49 string, col50 string, col51 string, col52 string, col53 string,
> col54 string, col55 string, col56 string, col57 string, col58 string, col59
> string, col60 string, col61 string, col62 string, col63 string, col64 string,
> col65 string, col66 string, col67 string, col68 string, col69 string, col70
> string, col71 string, col72 string, col73 string, col74 string, col75 string,
> col76 string, col77 string, col78 string, col79 string, col80 string, col81
> string, col82 string, col83 string, col84 string, col85 string, col86 string,
> col87 string, col88 string, col89 string, col90 string, col91 string, col92
> string, col93 string, col94 string, col95 string, col96 string, col97 string,
> col98 string, col99 string, col100 string, col101 string, col102 string,
> col103 string, col104 string, col105 string, col106 string, col107 string,
> col108 string, col109 string, col110 string, col111 string, col112 string,
> col113 string, col114 string, col115 string, col116 string, col117 string,
> col118 string, col119 string, col120 string, col121 string, col122 string,
> col123 string, col124 string, col125 string, col126 string, col127 string,
> col128 string, col129 string, col130 string, col131 string, col132 string,
> col133 string, col134 string, col135 string, col136 string, col137 string,
> col138 string, col139 string, col140 string, col141 string, col142 string,
> col143 string, col144 string, col145 string, col146 string, col147 string,
> col148 string, col149 string, col150 string, col151 string, col152 string,
> col153 string, col154 string, col155 string, col156 string, col157 string,
> col158 string, col159 string, col160 string, col161 string, col162 string,
> col163 string, col164 string, col165 string, col166 string, col167 string,
> col168 string, col169 string, col170 string, col171 string, col172 string,
> col173 string, col174 string, col175 string, col176 string, col177 string,
> col178 string, col179 string, col180 string, col181 string, col182 string,
> col183 string, col184 string, col185 string, col186 string, col187 string,
> col188 string, col189 string, col190 string, col191 string, col192 string,
> col193 string, col194 string, col195 string, col196 string, col197 string,
> col198 string, col199 string, col200 string, col201 string, col202 string,
> col203 string, col204 string, col205 string, col206 string, col207 string,
> col208 string, col209 string, col210 string, col211 string, col212 string,
> col213 string, col214 string, col215 string, col216 string, col217 string,
> col218 string, col219 string, col220 string, col221 string, col222 string,
> col223 string, col224 string, col225 string, col226 string, col227 string,
> col228 string, col229 string, col230 string, col231 string, col232 string,
> col233 string, col234 string, col235 string, col236 string, col237 string,
> col238 string, col239 string, col240 string, col241 string, col242 string,
> col243 string, col244 string, col245 string, col246 string, col247 string,
> col248 string, col249 string, col250 string, col251 string, col252 string,
> col253 string, col254 string, col255 string, col256 string, col257 string,
> col258 string, col259 string, col260 string, col261 string, col262 string,
> col263 string, col264 string, col265 string, col266 string, col267
[jira] [Updated] (ATLAS-2198) HiveHook fails with OOM when hive view with 500 columns are created.
[
https://issues.apache.org/jira/browse/ATLAS-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2198:
---
Attachment: 0001-ATLAS-2198-Hive-Hook-OOM-fix.patch
> HiveHook fails with OOM when hive view with 500 columns are created.
>
>
> Key: ATLAS-2198
> URL: https://issues.apache.org/jira/browse/ATLAS-2198
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8.2
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.8.2
>
> Attachments: 0001-ATLAS-2198-Hive-Hook-OOM-fix.patch
>
>
> create below two commands with hivehook enabled, hiveHook fails with OOM.
> {noformat}
> create table t1_500(col0 string, col1 string, col2 string, col3 string, col4
> string, col5 string, col6 string, col7 string, col8 string, col9 string,
> col10 string, col11 string, col12 string, col13 string, col14 string, col15
> string, col16 string, col17 string, col18 string, col19 string, col20 string,
> col21 string, col22 string, col23 string, col24 string, col25 string, col26
> string, col27 string, col28 string, col29 string, col30 string, col31 string,
> col32 string, col33 string, col34 string, col35 string, col36 string, col37
> string, col38 string, col39 string, col40 string, col41 string, col42 string,
> col43 string, col44 string, col45 string, col46 string, col47 string, col48
> string, col49 string, col50 string, col51 string, col52 string, col53 string,
> col54 string, col55 string, col56 string, col57 string, col58 string, col59
> string, col60 string, col61 string, col62 string, col63 string, col64 string,
> col65 string, col66 string, col67 string, col68 string, col69 string, col70
> string, col71 string, col72 string, col73 string, col74 string, col75 string,
> col76 string, col77 string, col78 string, col79 string, col80 string, col81
> string, col82 string, col83 string, col84 string, col85 string, col86 string,
> col87 string, col88 string, col89 string, col90 string, col91 string, col92
> string, col93 string, col94 string, col95 string, col96 string, col97 string,
> col98 string, col99 string, col100 string, col101 string, col102 string,
> col103 string, col104 string, col105 string, col106 string, col107 string,
> col108 string, col109 string, col110 string, col111 string, col112 string,
> col113 string, col114 string, col115 string, col116 string, col117 string,
> col118 string, col119 string, col120 string, col121 string, col122 string,
> col123 string, col124 string, col125 string, col126 string, col127 string,
> col128 string, col129 string, col130 string, col131 string, col132 string,
> col133 string, col134 string, col135 string, col136 string, col137 string,
> col138 string, col139 string, col140 string, col141 string, col142 string,
> col143 string, col144 string, col145 string, col146 string, col147 string,
> col148 string, col149 string, col150 string, col151 string, col152 string,
> col153 string, col154 string, col155 string, col156 string, col157 string,
> col158 string, col159 string, col160 string, col161 string, col162 string,
> col163 string, col164 string, col165 string, col166 string, col167 string,
> col168 string, col169 string, col170 string, col171 string, col172 string,
> col173 string, col174 string, col175 string, col176 string, col177 string,
> col178 string, col179 string, col180 string, col181 string, col182 string,
> col183 string, col184 string, col185 string, col186 string, col187 string,
> col188 string, col189 string, col190 string, col191 string, col192 string,
> col193 string, col194 string, col195 string, col196 string, col197 string,
> col198 string, col199 string, col200 string, col201 string, col202 string,
> col203 string, col204 string, col205 string, col206 string, col207 string,
> col208 string, col209 string, col210 string, col211 string, col212 string,
> col213 string, col214 string, col215 string, col216 string, col217 string,
> col218 string, col219 string, col220 string, col221 string, col222 string,
> col223 string, col224 string, col225 string, col226 string, col227 string,
> col228 string, col229 string, col230 string, col231 string, col232 string,
> col233 string, col234 string, col235 string, col236 string, col237 string,
> col238 string, col239 string, col240 string, col241 string, col242 string,
> col243 string, col244 string, col245 string, col246 string, col247 string,
> col248 string, col249 string, col250 string, col251 string, col252 string,
> col253 string, col254 string, col255 string, col256 string, col257 string,
> col258 string, col259 string, col260 string, col261 string, col262 string,
> col263 string, col264 string, col265 string, col266 string, col267 string,
>
[jira] [Resolved] (ATLAS-2207) Test property fixes
[ https://issues.apache.org/jira/browse/ATLAS-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2207. Resolution: Fixed > Test property fixes > --- > > Key: ATLAS-2207 > URL: https://issues.apache.org/jira/browse/ATLAS-2207 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > In one of the recent commits, atlas-application.properties under > typesystem/src/test/resources was accidentally modified this resulted in IT > failures on branch-0.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-2207) Test property fixes
[ https://issues.apache.org/jira/browse/ATLAS-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201494#comment-16201494 ] Apoorv Naik edited comment on ATLAS-2207 at 10/12/17 5:23 PM: -- Committed: branch-0.8: https://github.com/apache/atlas/commit/a05384870ce06548bd564ffc1962653b133e8b82 master: https://github.com/apache/atlas/commit/ea1b981e631e1d093f0df3294d9c4484873ca890 was (Author: apoorvnaik): Committed: https://github.com/apache/atlas/commit/a05384870ce06548bd564ffc1962653b133e8b82 > Test property fixes > --- > > Key: ATLAS-2207 > URL: https://issues.apache.org/jira/browse/ATLAS-2207 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > In one of the recent commits, atlas-application.properties under > typesystem/src/test/resources was accidentally modified this resulted in IT > failures on branch-0.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2218) Test stability across branches
Apoorv Naik created ATLAS-2218: -- Summary: Test stability across branches Key: ATLAS-2218 URL: https://issues.apache.org/jira/browse/ATLAS-2218 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik The tests are pretty inconsistent in runs across master and branch-0.8. This has been preventing a clean build in apache jenkins for a while now. This JIRA is aimed at ensuring build success across master and latest release branch. Goals: 1. Make IT runs consistent 2. Make UTs run successfully on both 3. Separate UTs and ITs in webapp module -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2210) Add relationship methods to AtlasClientV2
[ https://issues.apache.org/jira/browse/ATLAS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215738#comment-16215738 ] Apoorv Naik commented on ATLAS-2210: Committed on master: https://github.com/apache/atlas/commit/c08bac80a8aae344874e7393dd94fa7efece752b > Add relationship methods to AtlasClientV2 > - > > Key: ATLAS-2210 > URL: https://issues.apache.org/jira/browse/ATLAS-2210 > Project: Atlas > Issue Type: Improvement >Reporter: Andrew Hulbert > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2210) Add relationship methods to AtlasClientV2
[ https://issues.apache.org/jira/browse/ATLAS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik reassigned ATLAS-2210: -- Assignee: Apoorv Naik > Add relationship methods to AtlasClientV2 > - > > Key: ATLAS-2210 > URL: https://issues.apache.org/jira/browse/ATLAS-2210 > Project: Atlas > Issue Type: Improvement >Reporter: Andrew Hulbert >Assignee: Apoorv Naik > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2228) Remove dependency on V1 typesystem
Apoorv Naik created ATLAS-2228: -- Summary: Remove dependency on V1 typesystem Key: ATLAS-2228 URL: https://issues.apache.org/jira/browse/ATLAS-2228 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Currently the Notifications and DSL bit of Atlas still require the old typesystem to function. This JIRA will track the effort to migrate the old codepaths to use the new V2 type registry and V2 data structures -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2229) DSL changes to use V2 data structures
Apoorv Naik created ATLAS-2229: -- Summary: DSL changes to use V2 data structures Key: ATLAS-2229 URL: https://issues.apache.org/jira/browse/ATLAS-2229 Project: Atlas Issue Type: Sub-task Reporter: Apoorv Naik Assignee: Apoorv Naik -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2648) [Glossary] Remove "__" prefix from Glossary related types and relations
[ https://issues.apache.org/jira/browse/ATLAS-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465322#comment-16465322 ] Apoorv Naik commented on ATLAS-2648: [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/351/] was successful. Thanks Madhan > [Glossary] Remove "__" prefix from Glossary related types and relations > --- > > Key: ATLAS-2648 > URL: https://issues.apache.org/jira/browse/ATLAS-2648 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-remove-prefix-__-from-AtlasGlossary-type-names.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2648) [Glossary] Remove "__" prefix from Glossary related types and relations
[ https://issues.apache.org/jira/browse/ATLAS-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2648: --- Attachment: 0001-remove-prefix-__-from-AtlasGlossary-type-names.patch > [Glossary] Remove "__" prefix from Glossary related types and relations > --- > > Key: ATLAS-2648 > URL: https://issues.apache.org/jira/browse/ATLAS-2648 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-remove-prefix-__-from-AtlasGlossary-type-names.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2648) [Glossary] Remove "__" prefix from Glossary related types and relations
Apoorv Naik created ATLAS-2648: -- Summary: [Glossary] Remove "__" prefix from Glossary related types and relations Key: ATLAS-2648 URL: https://issues.apache.org/jira/browse/ATLAS-2648 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2660) [Glossary] Add feature toggle for cross glossary category children
Apoorv Naik created ATLAS-2660: -- Summary: [Glossary] Add feature toggle for cross glossary category children Key: ATLAS-2660 URL: https://issues.apache.org/jira/browse/ATLAS-2660 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 ATLAS-2655 added a restriction around the child category association within the same glossary. This JIRA adds the feature toggle capability so that this restriction can be controlled using an atlas property or some other mechanism -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2655) [Glossary] Restrict category child to be within same glossary
[ https://issues.apache.org/jira/browse/ATLAS-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468060#comment-16468060 ] Apoorv Naik commented on ATLAS-2655: [~davidrad] Thanks for the suggestion. I'll take this feature toggle in a subsequent patch. > [Glossary] Restrict category child to be within same glossary > - > > Key: ATLAS-2655 > URL: https://issues.apache.org/jira/browse/ATLAS-2655 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > Currently no such check exists. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2679) [Glossary] Derive category's qualifiedName using hierarchy
Apoorv Naik created ATLAS-2679: -- Summary: [Glossary] Derive category's qualifiedName using hierarchy Key: ATLAS-2679 URL: https://issues.apache.org/jira/browse/ATLAS-2679 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Currently the qualifiedName is derived using displayName and Glossary's qualifiedName. In this patch, the qualifiedName is derived from it's Hierarchy and any changes in the hierarchy itself will trigger a cascaded update of all children. E.g. Cat1 is parent category, Cat2 is child category Derived qualfiedName of Cat2 = Cat2.Cat1@ The following actions trigger a cascaded update of the children categories # Change of anchor # Change of Parent # Removal of children from a parent (similar to #2) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: (was: 0001-Jackson-and-Lucene-dependency-upgrade.patch) > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch, > 0002-Spring-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: 0001-Dependency-upgrades.patch > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch, > 0002-Spring-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: (was: 0002-Spring-upgrades.patch) > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2654) [Glossary] Issue when creating term relations with end2 attr name
Apoorv Naik created ATLAS-2654: -- Summary: [Glossary] Issue when creating term relations with end2 attr name Key: ATLAS-2654 URL: https://issues.apache.org/jira/browse/ATLAS-2654 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 When the end2 attr name were being set while creating the Term relations, the relationship was inversely created eg. setting preferredToTerms in Term1 with value Term2 would result in setting preferredToTerms in Term2 instead of Term1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
