[jira] [Updated] (ATLAS-971) UI not displaying results for this query - Eg: "hive_table as t where qualifiedName = 'default.input@cl1' select t"
[ https://issues.apache.org/jira/browse/ATLAS-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-971: -- Assignee: (was: Madhan Neethiraj) > UI not displaying results for this query - Eg: "hive_table as t where > qualifiedName = 'default.input@cl1' select t" > --- > > Key: ATLAS-971 > URL: https://issues.apache.org/jira/browse/ATLAS-971 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Ayub Khan >Priority: Critical > > Create table and fire this DSL query from UI (hive_table as t where > qualifiedName = 'default.tmp1@cl1' select t). > https://monosnap.com/file/gPZO4fYizZrQFk0rmKBfOrCJX7LJas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-971) UI not displaying results for this query - Eg: "hive_table as t where qualifiedName = 'default.input@cl1' select t"
[ https://issues.apache.org/jira/browse/ATLAS-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-971: -- Fix Version/s: (was: 0.7-incubating) > UI not displaying results for this query - Eg: "hive_table as t where > qualifiedName = 'default.input@cl1' select t" > --- > > Key: ATLAS-971 > URL: https://issues.apache.org/jira/browse/ATLAS-971 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Ayub Khan >Assignee: Madhan Neethiraj >Priority: Critical > > Create table and fire this DSL query from UI (hive_table as t where > qualifiedName = 'default.tmp1@cl1' select t). > https://monosnap.com/file/gPZO4fYizZrQFk0rmKBfOrCJX7LJas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-969) Removed unused images in ./docs/src/site/resources/images
Shwetha G S created ATLAS-969: - Summary: Removed unused images in ./docs/src/site/resources/images Key: ATLAS-969 URL: https://issues.apache.org/jira/browse/ATLAS-969 Project: Atlas Issue Type: Bug Reporter: Shwetha G S -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356902#comment-15356902 ] Shwetha G S commented on ATLAS-967: --- Can you also remove any images not used, don't see any reference to graph.png. > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > Attachments: ATLAS-967.patch > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356895#comment-15356895 ] Shwetha G S commented on ATLAS-967: --- Can you also remove 'Hortonworks' in dashboardv2/package.json? > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-964) Cleanup NOTICE and LICENSE
[
https://issues.apache.org/jira/browse/ATLAS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-964:
--
Attachment: ATLAS-964.patch
> Cleanup NOTICE and LICENSE
> --
>
> Key: ATLAS-964
> URL: https://issues.apache.org/jira/browse/ATLAS-964
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-964.patch
>
>
> {noformat}
> Hi,
> We have removed the glyphicons fonts, updated the license and notice to
> match the source contents. Will you be able to do a quick check to see if
> we are missing anything here:
> https://github.com/apache/incubator-atlas/tree/0.7-incubating?
> License looks good to me only two very minor things I can see you / may not
> want to change:
> - No need for the quotes around MIT license or the like. I've seen this done
> elsewhere but can't think of a reason for doing so. Rabbit ears / scare
> quotes [1] can imply that it's actually not the correct license or that it's
> a MIT like license.
> - Why not legally required I include the a pointer to the public domain text.
> Notice is a bit odd, why have the section "Titan also includes software from
> other open source projects including..."? Are these things bundled or just
> dependancies? If they are just dependancies there is no need to mention then
> in NOTICE, move them to a DEPENDENCIES files if you think it is useful
> information to tell the user of the software.
> (Feel free to post this to the list for discussion if you want)
> Thanks,
> Justin
> 1. https://en.wikipedia.org/wiki/Scare_quotes
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-964) Cleanup NOTICE and LICENSE
Shwetha G S created ATLAS-964:
-
Summary: Cleanup NOTICE and LICENSE
Key: ATLAS-964
URL: https://issues.apache.org/jira/browse/ATLAS-964
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Priority: Blocker
Fix For: 0.7-incubating
{noformat}
Hi,
We have removed the glyphicons fonts, updated the license and notice to
match the source contents. Will you be able to do a quick check to see if
we are missing anything here:
https://github.com/apache/incubator-atlas/tree/0.7-incubating?
License looks good to me only two very minor things I can see you / may not
want to change:
- No need for the quotes around MIT license or the like. I've seen this done
elsewhere but can't think of a reason for doing so. Rabbit ears / scare quotes
[1] can imply that it's actually not the correct license or that it's a MIT
like license.
- Why not legally required I include the a pointer to the public domain text.
Notice is a bit odd, why have the section "Titan also includes software from
other open source projects including..."? Are these things bundled or just
dependancies? If they are just dependancies there is no need to mention then in
NOTICE, move them to a DEPENDENCIES files if you think it is useful information
to tell the user of the software.
(Feel free to post this to the list for discussion if you want)
Thanks,
Justin
1. https://en.wikipedia.org/wiki/Scare_quotes
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-962: -- Comment: was deleted (was: +1) > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355261#comment-15355261 ] Shwetha G S commented on ATLAS-962: --- +1 > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355260#comment-15355260 ] Shwetha G S commented on ATLAS-962: --- +1 > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-961) DataSetLineageJerseyResourceIT.setUp fails
Shwetha G S created ATLAS-961:
-
Summary: DataSetLineageJerseyResourceIT.setUp fails
Key: ATLAS-961
URL: https://issues.apache.org/jira/browse/ATLAS-961
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
mvn clean install -rf :atlas-webapp -Dit.test=DataSetLineageJerseyResourceIT
-DskipUTs
{noformat}
Tests run: 9, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 3.716 sec <<<
FAILURE! - in org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT
setUp(org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT) Time
elapsed: 3.666 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY
failed with status 400(Bad Request) Response Body ({"error":"Unknown datatype:
Fact","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
Unknown datatype: Fact\n\tat
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:178)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:649)\n\tat
org.apache.atlas.typesystem.types.ClassType.createInstanceWithTraits(ClassType.java:182)\n\tat
org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:125)\n\tat
org.apache.atlas.services.DefaultMetadataService.getTypedReferenceableInstance(DefaultMetadataService.java:374)\n\tat
org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:350)\n\tat
org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:331)\n\tat
org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:606)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)\n\tat
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)\n\tat
com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
org.eclipse
[jira] [Updated] (ATLAS-948) import-hive should allow an option to continue after failure
[ https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-948: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > import-hive should allow an option to continue after failure > > > Key: ATLAS-948 > URL: https://issues.apache.org/jira/browse/ATLAS-948 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad >Priority: Critical > Fix For: 0.7-incubating > > Attachments: ATLAS-948.patch > > > Currently import-hive.sh aborts whenever a failure occurs during import of a > table. It should allow continuation after logging the failure which could be > checked and post processed later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-919) UI : Deleted references should be shown in red or filtered out
[ https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-919: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > UI : Deleted references should be shown in red or filtered out > -- > > Key: ATLAS-919 > URL: https://issues.apache.org/jira/browse/ATLAS-919 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.7-incubating > > Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, > ATLAS-919.1.patch, ATLAS-919.2.patch, ATLAS-919.3.patch, ATLAS-919.patch, > ATLAS-919.rebased.patch, Screen Shot 2016-06-20 at 3.56.33 PM.png, Screen > Shot 2016-06-23 at 11.26.17 AM.png > > > Foe eg: In a hive_table one of the columns could be dropped in which case the > columns array will have the deleted column as well. This could be completely > filtered out in the UI. The way to identify this is to check if the entity > state is DELETED when going through the references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-954) Get hadoop classpath if command hadoop is in PATH
[ https://issues.apache.org/jira/browse/ATLAS-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-954: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > Get hadoop classpath if command hadoop is in PATH > - > > Key: ATLAS-954 > URL: https://issues.apache.org/jira/browse/ATLAS-954 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.7-incubating > > Attachments: ATLAS-954.patch > > > The script import_hive.sh expects Hadoop classpath. > Environment variable HADOOP_HOME or HADOOP_CLASSPATH might not be set but > command hadoop may be in the PATH. > Get hadoop classpath from hadoop command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version
[
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-927:
--
Fix Version/s: (was: 0.8-incubating)
0.7-incubating
> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-927.1.patch, ATLAS-927.2.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded
> version:
> {code}
> Version :
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project
> version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.
[ https://issues.apache.org/jira/browse/ATLAS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-624: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > UI: Clicking a tag hyperlink should always result in DSL search. In some > cases, results in full-text search. > > > Key: ATLAS-624 > URL: https://issues.apache.org/jira/browse/ATLAS-624 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Ayub Khan >Assignee: Kalyani Kashikar > Fix For: 0.7-incubating > > Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch > > > UI: Clicking a tag hyperlink should always result in DSL search. > 1. Create a hive table with a column, Attach a tag to the column. > 2. Now navigate to the schema tab of hive_table search result. > 3. Click on the attached tag - This will result in full-text query search of > that tag, which will always return empty response. This should be ideally a > DSL search query which will show all the entities associated with that tag. > Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is > clicked on atlas UI, this should result in DSL search only. > UI snapshot for reference: > https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-950) Atlas should support Solr that requires Kerberos authentication
[ https://issues.apache.org/jira/browse/ATLAS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-950: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > Atlas should support Solr that requires Kerberos authentication > --- > > Key: ATLAS-950 > URL: https://issues.apache.org/jira/browse/ATLAS-950 > Project: Atlas > Issue Type: Bug >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.7-incubating > > Attachments: ATLAS-950.patch > > > Currently Atlas uses Solr version 5.1.0 libraries, which does not support > Kerberos authentication. To support Solr instances that require Kerberos > authentication, Atlas should use recent Solr version libraries - like 5.5.1. > Details Solr Security can be found at: > https://cwiki.apache.org/confluence/display/solr/Securing+Solr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-947) Return state information in inputs and outputs lineage API
[ https://issues.apache.org/jira/browse/ATLAS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-947: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > Return state information in inputs and outputs lineage API > -- > > Key: ATLAS-947 > URL: https://issues.apache.org/jira/browse/ATLAS-947 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-947.patch > > > Return state of entity along with name in lineage inputs and outputs API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-806) Create default taxonomy at server startup
[ https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-806: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > Create default taxonomy at server startup > - > > Key: ATLAS-806 > URL: https://issues.apache.org/jira/browse/ATLAS-806 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-806-1.patch, ATLAS-806-2.patch, ATLAS-806.patch > > > Currently, the UI is creating a default taxonomy object as the first call in > its flow. This would not work if used from an API. Hence, creating this > automatically at server startup time will help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-942) Jenkins build failure - GraphRepoMapperScaleTest
[
https://issues.apache.org/jira/browse/ATLAS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-942:
--
Fix Version/s: (was: 0.8-incubating)
0.7-incubating
> Jenkins build failure - GraphRepoMapperScaleTest
>
>
> Key: ATLAS-942
> URL: https://issues.apache.org/jira/browse/ATLAS-942
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-942.patch
>
>
> https://builds.apache.org/job/apache-atlas-nightly/342/console
> {noformat}
> Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 7.241 sec <<<
> FAILURE! - in org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
> setUp(org.apache.atlas.repository.graph.GraphRepoMapperScaleTest) Time
> elapsed: 7.205 sec <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:168)
> at
> org.apache.atlas.repository.graph.GraphRepoMapperScaleTest.setUp(GraphRepoMapperScaleTest.java:77)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table
[ https://issues.apache.org/jira/browse/ATLAS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-920: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > Lineage graph is broken when there are multiple paths from same source table > > > Key: ATLAS-920 > URL: https://issues.apache.org/jira/browse/ATLAS-920 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Suma Shivaprasad >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > Attachments: ATLAS-920.patch, Screen Shot 2016-06-20 at 4.09.02 > PM.png, Screen Shot 2016-06-20 at 4.31.58 PM.png, Screen Shot 2016-06-20 at > 4.49.24 PM.png > > > Steps to reproduce > 1. CREATE TABLE test_table(abc string) partitioned by (dt date) > 2. CREATE TABLE test_lineage as SELECT * from test_table > 3. CREATE VIEW test_view as SELECT * from test_table > 4. ALTER VIEW test_view as SELECT * from test_lineage > The lineage is broken as seen in screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-940) Type cache implementation property name in atlas-application.properties is incorrect
[ https://issues.apache.org/jira/browse/ATLAS-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-940: -- Fix Version/s: (was: 0.8-incubating) 0.7-incubating > Type cache implementation property name in atlas-application.properties is > incorrect > > > Key: ATLAS-940 > URL: https://issues.apache.org/jira/browse/ATLAS-940 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: David Kantor >Assignee: David Kantor > Fix For: 0.7-incubating > > Attachments: rb49091.patch > > > The name of the type cache implementation property was changed in ATLAS-856 > but this change was not propagated to the "production" > atlas-application.properties file that is bundled in the distribution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-431) Remove un-used licenses
[ https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-431: -- Attachment: ATLAS-431-v2.patch > Remove un-used licenses > --- > > Key: ATLAS-431 > URL: https://issues.apache.org/jira/browse/ATLAS-431 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-431-v2.patch, ATLAS-431.patch > > > From 0.6 voting thread: > On 26/12/15 5:14 am, "Justin Mclean" wrote: > Hi, > +1 binding > I checked: > - artefact contains “incubating” > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good, but license main contain too many things (see > below). > - no unexpected binaries in release > - all source files have Apache headers > - can compile from source > The license mentions Berkeley DB Java Edition and ASM but it doesn’t look > like these are bundled in the source release. If this is the case they should > be removed from the source LICENSE file. [1] > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-431) Remove un-used licenses
[ https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354559#comment-15354559 ] Shwetha G S commented on ATLAS-431: --- Updated patch adds the missing lines to NOTICE > Remove un-used licenses > --- > > Key: ATLAS-431 > URL: https://issues.apache.org/jira/browse/ATLAS-431 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-431-v2.patch, ATLAS-431.patch > > > From 0.6 voting thread: > On 26/12/15 5:14 am, "Justin Mclean" wrote: > Hi, > +1 binding > I checked: > - artefact contains “incubating” > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good, but license main contain too many things (see > below). > - no unexpected binaries in release > - all source files have Apache headers > - can compile from source > The license mentions Berkeley DB Java Edition and ASM but it doesn’t look > like these are bundled in the source release. If this is the case they should > be removed from the source LICENSE file. [1] > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-431) Remove un-used licenses
[ https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-431: - Assignee: Shwetha G S > Remove un-used licenses > --- > > Key: ATLAS-431 > URL: https://issues.apache.org/jira/browse/ATLAS-431 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-431.patch > > > From 0.6 voting thread: > On 26/12/15 5:14 am, "Justin Mclean" wrote: > Hi, > +1 binding > I checked: > - artefact contains “incubating” > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good, but license main contain too many things (see > below). > - no unexpected binaries in release > - all source files have Apache headers > - can compile from source > The license mentions Berkeley DB Java Edition and ASM but it doesn’t look > like these are bundled in the source release. If this is the case they should > be removed from the source LICENSE file. [1] > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-431) Remove un-used licenses
[ https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-431: -- Attachment: ATLAS-431.patch > Remove un-used licenses > --- > > Key: ATLAS-431 > URL: https://issues.apache.org/jira/browse/ATLAS-431 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-431.patch > > > From 0.6 voting thread: > On 26/12/15 5:14 am, "Justin Mclean" wrote: > Hi, > +1 binding > I checked: > - artefact contains “incubating” > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good, but license main contain too many things (see > below). > - no unexpected binaries in release > - all source files have Apache headers > - can compile from source > The license mentions Berkeley DB Java Edition and ASM but it doesn’t look > like these are bundled in the source release. If this is the case they should > be removed from the source LICENSE file. [1] > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-958) Add licenses for dashboard dependencies
Shwetha G S created ATLAS-958: - Summary: Add licenses for dashboard dependencies Key: ATLAS-958 URL: https://issues.apache.org/jira/browse/ATLAS-958 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Priority: Blocker Fix For: 0.7-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-431) Remove un-used licenses
[ https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-431: -- Fix Version/s: 0.7-incubating > Remove un-used licenses > --- > > Key: ATLAS-431 > URL: https://issues.apache.org/jira/browse/ATLAS-431 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Fix For: 0.7-incubating > > > From 0.6 voting thread: > On 26/12/15 5:14 am, "Justin Mclean" wrote: > Hi, > +1 binding > I checked: > - artefact contains “incubating” > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good, but license main contain too many things (see > below). > - no unexpected binaries in release > - all source files have Apache headers > - can compile from source > The license mentions Berkeley DB Java Edition and ASM but it doesn’t look > like these are bundled in the source release. If this is the case they should > be removed from the source LICENSE file. [1] > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-948) import-hive should allow an option to continue after failure
[ https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352313#comment-15352313 ] Shwetha G S commented on ATLAS-948: --- +1 > import-hive should allow an option to continue after failure > > > Key: ATLAS-948 > URL: https://issues.apache.org/jira/browse/ATLAS-948 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad >Priority: Critical > Fix For: 0.8-incubating > > Attachments: ATLAS-948.patch > > > Currently import-hive.sh aborts whenever a failure occurs during import of a > table. It should allow continuation after logging the failure which could be > checked and post processed later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL
[ https://issues.apache.org/jira/browse/ATLAS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351386#comment-15351386 ] Shwetha G S commented on ATLAS-435: --- [~guptaneeru]/[~dkantor], in gremlin translator, why was toLowercase() added to the property value? If the orderby property is not set, the condition fails > Add ORDER BY and Limit to search DSL > -- > > Key: ATLAS-435 > URL: https://issues.apache.org/jira/browse/ATLAS-435 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: David Kantor >Assignee: Neeru Gupta > Fix For: 0.7-incubating > > Attachments: rb45499(2).patch, rb45499(3).patch > > > Add support for Limit and ORDER BY to Atlas search DSL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-647) entityText property should be prefixed with __
[ https://issues.apache.org/jira/browse/ATLAS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-647: -- Assignee: (was: Shwetha G S) > entityText property should be prefixed with __ > -- > > Key: ATLAS-647 > URL: https://issues.apache.org/jira/browse/ATLAS-647 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > All internal properties for the vertex in the repository are prefixed with __ > to avoid conflicts with user defined attribute names. Looks like entityText > is missed out -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red or filtered out
[ https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350456#comment-15350456 ] Shwetha G S commented on ATLAS-919: --- When a deleted table is viewed, sd is displayed for me, but is not marked as deleted. Also, when sd is clicked, the sd entity shown is not marked as deleted. The API has the deleted state in all these cases > UI : Deleted references should be shown in red or filtered out > -- > > Key: ATLAS-919 > URL: https://issues.apache.org/jira/browse/ATLAS-919 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Suma Shivaprasad >Assignee: Keval Bhatt >Priority: Critical > Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, > ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot > 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png > > > Foe eg: In a hive_table one of the columns could be dropped in which case the > columns array will have the deleted column as well. This could be completely > filtered out in the UI. The way to identify this is to check if the entity > state is DELETED when going through the references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348483#comment-15348483 ] Shwetha G S commented on ATLAS-847: --- You don't need to show number of pages. Most recent entries are returned in the first page. So, instead of showing pages as 1, 2, 3 etc, just show the next link which fetches the next page. If we have user requirements, we can change this to page count later. > UI: Audit versioning does not paginate details from Atlas server > > > Key: ATLAS-847 > URL: https://issues.apache.org/jira/browse/ATLAS-847 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Kalyani Kashikar > > In ATLAS-664, the capability to view Audit events was added to the Atlas > admin UI. However, currently, the API call made only fetches the first 100 > events (which is the default if no count is sent). In order to fetch the next > set of events, further API calls need to be made to the Audit API, by > providing additional parameters in the API. This JIRA is to track the > required changes in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-943) ATlas Build failure: Storm Bridge
[
https://issues.apache.org/jira/browse/ATLAS-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S resolved ATLAS-943.
---
Resolution: Not A Problem
Resolving, please re-open if you see the issue again
> ATlas Build failure: Storm Bridge
> -
>
> Key: ATLAS-943
> URL: https://issues.apache.org/jira/browse/ATLAS-943
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
> Environment: CentOS 7.2.1511
> Maven 3.3.9
> OpenJDK 1.7.0_101
> *fresh atlas clone*
>Reporter: Nigel Jones
>
> [INFO] Apache Atlas Storm Bridge .. FAILURE [02:34
> min]
> [WARNING] FAILED
> o.e.j.m.p.JettyWebAppContext@17d43cec{/,file:/home/ibmcloud/src/atlas/webapp/target/atlas-webapp-0.8-incubating-SNAPSHOT/,STARTING}{/home/ibmcloud/src/atlas/webapp/target/atlas-webapp-0.8-incubating-SNAPSHOT.war}:
> java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.nio.HeapByteBuffer.(HeapByteBuffer.java:57)
> at java.nio.ByteBuffer.allocate(ByteBuffer.java:331)
> at kafka.log.SkimpyOffsetMap.(OffsetMap.scala:43)
> at kafka.log.LogCleaner$CleanerThread.(LogCleaner.scala:193)
> at kafka.log.LogCleaner$$anonfun$1.apply(LogCleaner.scala:83)
> at kafka.log.LogCleaner$$anonfun$1.apply(LogCleaner.scala:83)
> at
> etc.
> Heap Space likely needs increasing for clean build/test
> Log file to be attached...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server
[
https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348127#comment-15348127
]
Shwetha G S commented on ATLAS-847:
---
bq. For pagination it requires total number of records. How do I get that ?
The API doesn't return total number of records currently. Make an API call to
check if there are any remaining records
bq. Regarding usage of "startKey" the output remain same when I tried
startKey=any number
For the first page, don't set startKey. For the second page, startKey should be
equal to the startKey specified in the last record of the previous call(made
for first page)
bq. the api do not returns audit data in json
Here is the json response from audit API
{noformat}
{
"requestId":"qtp966396367-171 - a8c0fada-9c4b-4616-84b2-bccdf90ca54d",
"events":[
{
"entityId":"c402c96b-72d8-4d6b-ad15-101b38870140",
"timestamp":1466764733583,
"user":"admin",
"action":"TAG_ADD",
"details":"Added trait: {\n
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct\",\n
\"typeName\":\"tag1\",\n \"values\":{\n\n }\n}",
"eventKey":"c402c96b-72d8-4d6b-ad15-101b38870140:1466764733583",
"entityDefinition":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"c402c96b-72d8-4d6b-ad15-101b38870140",
"version":0,
"typeName":"hive_column",
"state":"ACTIVE"
},
"typeName":"hive_column",
"values":{
"name":"id",
"qualifiedName":"default.t1.id@primary",
"owner":"sshivalingamurthy",
"type":"string",
"table":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"cebdf4a6-838c-45d7-b166-302c0e4c6c48",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
}
},
"traitNames":[
"tag1"
],
"traits":{
"tag1":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName":"tag1",
"values":{
}
}
}
}
},
{
"entityId":"c402c96b-72d8-4d6b-ad15-101b38870140",
"timestamp":1466764387184,
"user":"sshivalingamurthy",
"action":"ENTITY_UPDATE",
"details":"Updated: {\n
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
\"id\":{\n
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
\"id\":\"c402c96b-72d8-4d6b-ad15-101b38870140\",\n\"version\":0,\n
\"typeName\":\"hive_column\",\n\"state\":\"ACTIVE\"\n },\n
\"typeName\":\"hive_column\",\n \"values\":{\n\"name\":\"id\",\n
\"description\":null,\n\"qualifiedName\":\"default.t1.id@primary\",\n
\"comment\":null,\n\"owner\":\"sshivalingamurthy\",\n
\"type\":\"string\",\n\"table\":{\n
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
\"id\":\"cebdf4a6-838c-45d7-b166-302c0e4c6c48\",\n \"version\":0,\n
\"typeName\":\"hive_table\",\n \"state\":\"ACTIVE\"\n}\n },\n
\"traitNames\":[\n\n ],\n \"traits\":{\n\n }\n}",
"eventKey":"c402c96b-72d8-4d6b-ad15-101b38870140:1466764387184",
"entityDefinition":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"c402c96b-72d8-4d6b-ad15-101b38870140",
"version":0,
"typeName":"hive_column",
"state":"ACTIVE"
},
"typeName":"hive_column",
"values":{
"name":"id",
"qualifiedName":"default.t1.id@primary",
"owner":"sshivalingamurthy",
"type":"string",
"table":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"cebdf4a6-838c-45d7-b166-302c0e4c6c48",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
}
},
"traitNames":[
],
"traits":{
}
}
},
{
"entityId":"c402c96b-72d8-4d6b-ad15-101b38870140",
"timestamp":1466764385464,
"user":"sshiva
[jira] [Commented] (ATLAS-947) Return state information in inputs and outputs lineage API
[
https://issues.apache.org/jira/browse/ATLAS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348118#comment-15348118
]
Shwetha G S commented on ATLAS-947:
---
Here is a sample json
{noformat}
{
requestId:"qtp966396367-171 - 685b8b53-c999-4f78-bcb6-4849a44ec3d6",
results:{
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName:"__tempQueryResultStruct17",
values:{
vertices:{
0a0f0924-bf6c-47d7-a93a-f06378896ad7:{
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName:"__tempQueryResultStruct16",
values:{
qualifiedName:"default.t2@primary",
vertexId:{
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName:"__IdType",
values:{
guid:"0a0f0924-bf6c-47d7-a93a-f06378896ad7",
state:"ACTIVE",
typeName:"hive_table"
}
},
name:"t2"
}
},
cebdf4a6-838c-45d7-b166-302c0e4c6c48:{
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName:"__tempQueryResultStruct16",
values:{
qualifiedName:"default.t1@primary",
vertexId:{
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName:"__IdType",
values:{
guid:"cebdf4a6-838c-45d7-b166-302c0e4c6c48",
state:"ACTIVE",
typeName:"hive_table"
}
},
name:"t1"
}
}
},
edges:{
4b5b2118-c899-40e5-b050-c47a4e3d82b6:[
"0a0f0924-bf6c-47d7-a93a-f06378896ad7"
],
cebdf4a6-838c-45d7-b166-302c0e4c6c48:[
"4b5b2118-c899-40e5-b050-c47a4e3d82b6"
]
}
}
}
}
{noformat}
> Return state information in inputs and outputs lineage API
> --
>
> Key: ATLAS-947
> URL: https://issues.apache.org/jira/browse/ATLAS-947
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-947.patch
>
>
> Return state of entity along with name in lineage inputs and outputs API
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-947) Return state information in inputs and outputs lineage API
[ https://issues.apache.org/jira/browse/ATLAS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-947: -- Attachment: ATLAS-947.patch > Return state information in inputs and outputs lineage API > -- > > Key: ATLAS-947 > URL: https://issues.apache.org/jira/browse/ATLAS-947 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-947.patch > > > Return state of entity along with name in lineage inputs and outputs API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-918) UI : Deleted entities show status as DELETED and Datasets should be differentiable in lineage
[ https://issues.apache.org/jira/browse/ATLAS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347827#comment-15347827 ] Shwetha G S commented on ATLAS-918: --- Working on ATLAS-947, will give a patch and sample json that you can work with. When are the cases where guid is not present in vertices object. If there is no guid, what API call is made to get the details. According to me, there shouldn't be any case where guid is not present in vertices object. > UI : Deleted entities show status as DELETED and Datasets should be > differentiable in lineage > - > > Key: ATLAS-918 > URL: https://issues.apache.org/jira/browse/ATLAS-918 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Suma Shivaprasad >Assignee: Keval Bhatt >Priority: Critical > Attachments: Screen Shot 2016-06-20 at 2.20.32 PM.png > > > Keval, > This jira is to track showing deleted entities with a diff color in lineage. > Is there anything missing in the lineage API to implement this? We need to > take care of this since no one looks at lineage via a process and will be > mostly looking at lineage from a table or a dataset. Also a table can be > dropped and recreated in hive, leading to linage showing as attached in > screen shot > Also can we show the property (status)__status for deleted entities as > "DELETED" . We could display that in "properties" section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-947) Return state information in inputs and outputs lineage API
[ https://issues.apache.org/jira/browse/ATLAS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-947: - Assignee: Shwetha G S > Return state information in inputs and outputs lineage API > -- > > Key: ATLAS-947 > URL: https://issues.apache.org/jira/browse/ATLAS-947 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Shwetha G S > Fix For: 0.8-incubating > > > Return state of entity along with name in lineage inputs and outputs API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-946) gmx 18446661660 GMX helpline number
[ https://issues.apache.org/jira/browse/ATLAS-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-946. --- Resolution: Invalid > gmx 18446661660 GMX helpline number > --- > > Key: ATLAS-946 > URL: https://issues.apache.org/jira/browse/ATLAS-946 > Project: Atlas > Issue Type: Bug >Reporter: peter smith > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-942) Jenkins build failure - GraphRepoMapperScaleTest
[
https://issues.apache.org/jira/browse/ATLAS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-942:
--
Attachment: ATLAS-942.patch
> Jenkins build failure - GraphRepoMapperScaleTest
>
>
> Key: ATLAS-942
> URL: https://issues.apache.org/jira/browse/ATLAS-942
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-942.patch
>
>
> https://builds.apache.org/job/apache-atlas-nightly/342/console
> {noformat}
> Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 7.241 sec <<<
> FAILURE! - in org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
> setUp(org.apache.atlas.repository.graph.GraphRepoMapperScaleTest) Time
> elapsed: 7.205 sec <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:168)
> at
> org.apache.atlas.repository.graph.GraphRepoMapperScaleTest.setUp(GraphRepoMapperScaleTest.java:77)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-942) Jenkins build failure - GraphRepoMapperScaleTest
[
https://issues.apache.org/jira/browse/ATLAS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-942:
--
Description:
https://builds.apache.org/job/apache-atlas-nightly/342/console
{noformat}
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 7.241 sec <<<
FAILURE! - in org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
setUp(org.apache.atlas.repository.graph.GraphRepoMapperScaleTest) Time
elapsed: 7.205 sec <<< FAILURE!
java.lang.NullPointerException: null
at
org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:168)
at
org.apache.atlas.repository.graph.GraphRepoMapperScaleTest.setUp(GraphRepoMapperScaleTest.java:77)
{noformat}
was:
{noformat}
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 7.241 sec <<<
FAILURE! - in org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
setUp(org.apache.atlas.repository.graph.GraphRepoMapperScaleTest) Time
elapsed: 7.205 sec <<< FAILURE!
java.lang.NullPointerException: null
at
org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:168)
at
org.apache.atlas.repository.graph.GraphRepoMapperScaleTest.setUp(GraphRepoMapperScaleTest.java:77)
{noformat}
> Jenkins build failure - GraphRepoMapperScaleTest
>
>
> Key: ATLAS-942
> URL: https://issues.apache.org/jira/browse/ATLAS-942
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
>
> https://builds.apache.org/job/apache-atlas-nightly/342/console
> {noformat}
> Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 7.241 sec <<<
> FAILURE! - in org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
> setUp(org.apache.atlas.repository.graph.GraphRepoMapperScaleTest) Time
> elapsed: 7.205 sec <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:168)
> at
> org.apache.atlas.repository.graph.GraphRepoMapperScaleTest.setUp(GraphRepoMapperScaleTest.java:77)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-942) Jenkins build failure - GraphRepoMapperScaleTest
Shwetha G S created ATLAS-942:
-
Summary: Jenkins build failure - GraphRepoMapperScaleTest
Key: ATLAS-942
URL: https://issues.apache.org/jira/browse/ATLAS-942
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Fix For: 0.8-incubating
{noformat}
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 7.241 sec <<<
FAILURE! - in org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
setUp(org.apache.atlas.repository.graph.GraphRepoMapperScaleTest) Time
elapsed: 7.205 sec <<< FAILURE!
java.lang.NullPointerException: null
at
org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:168)
at
org.apache.atlas.repository.graph.GraphRepoMapperScaleTest.setUp(GraphRepoMapperScaleTest.java:77)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-924) Release 0.7-incubating
[ https://issues.apache.org/jira/browse/ATLAS-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-924: - Assignee: Shwetha G S > Release 0.7-incubating > -- > > Key: ATLAS-924 > URL: https://issues.apache.org/jira/browse/ATLAS-924 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-643) Ability to specify multiple order by criteria
[ https://issues.apache.org/jira/browse/ATLAS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-643: -- Issue Type: Improvement (was: Sub-task) Parent: (was: ATLAS-435) > Ability to specify multiple order by criteria > - > > Key: ATLAS-643 > URL: https://issues.apache.org/jira/browse/ATLAS-643 > Project: Atlas > Issue Type: Improvement >Reporter: Neeru Gupta >Assignee: Neeru Gupta > > DSL should be able to accept and parse queries like > select X order by x.name, x.description desc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-435) Add ORDER BY and Limit to search DSL
[ https://issues.apache.org/jira/browse/ATLAS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-435. --- Resolution: Fixed Fix Version/s: 0.7-incubating > Add ORDER BY and Limit to search DSL > -- > > Key: ATLAS-435 > URL: https://issues.apache.org/jira/browse/ATLAS-435 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: David Kantor >Assignee: Neeru Gupta > Fix For: 0.7-incubating > > Attachments: rb45499(2).patch, rb45499(3).patch > > > Add support for Limit and ORDER BY to Atlas search DSL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-366) Release 0.6-incubating
[ https://issues.apache.org/jira/browse/ATLAS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-366. --- Resolution: Fixed > Release 0.6-incubating > -- > > Key: ATLAS-366 > URL: https://issues.apache.org/jira/browse/ATLAS-366 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-419) Document release steps in wiki
[ https://issues.apache.org/jira/browse/ATLAS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-419: -- Issue Type: Task (was: Sub-task) Parent: (was: ATLAS-366) > Document release steps in wiki > -- > > Key: ATLAS-419 > URL: https://issues.apache.org/jira/browse/ATLAS-419 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S >Assignee: Shwetha G S > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-366) Release 0.6-incubating
[ https://issues.apache.org/jira/browse/ATLAS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-366: -- Fix Version/s: 0.6-incubating > Release 0.6-incubating > -- > > Key: ATLAS-366 > URL: https://issues.apache.org/jira/browse/ATLAS-366 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-369) Publish 0.6-incubating artifacts
[ https://issues.apache.org/jira/browse/ATLAS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-369. --- Resolution: Fixed Fix Version/s: 0.6-incubating Artifacts now available at https://repository.apache.org/content/repositories/releases/org/apache/atlas/ > Publish 0.6-incubating artifacts > > > Key: ATLAS-369 > URL: https://issues.apache.org/jira/browse/ATLAS-369 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.6-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-936) Update atlas website
Shwetha G S created ATLAS-936: - Summary: Update atlas website Key: ATLAS-936 URL: https://issues.apache.org/jira/browse/ATLAS-936 Project: Atlas Issue Type: Sub-task Reporter: Shwetha G S -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-936) Update atlas website
[ https://issues.apache.org/jira/browse/ATLAS-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-936: - Assignee: Shwetha G S > Update atlas website > > > Key: ATLAS-936 > URL: https://issues.apache.org/jira/browse/ATLAS-936 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-935) Publish release artifacts
Shwetha G S created ATLAS-935: - Summary: Publish release artifacts Key: ATLAS-935 URL: https://issues.apache.org/jira/browse/ATLAS-935 Project: Atlas Issue Type: Sub-task Reporter: Shwetha G S Assignee: Shwetha G S -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-369) Publish 0.6-incubating artifacts
[ https://issues.apache.org/jira/browse/ATLAS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-369: - Assignee: Shwetha G S (was: Suma Shivaprasad) > Publish 0.6-incubating artifacts > > > Key: ATLAS-369 > URL: https://issues.apache.org/jira/browse/ATLAS-369 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-419) Document release steps in wiki
[ https://issues.apache.org/jira/browse/ATLAS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343952#comment-15343952 ] Shwetha G S commented on ATLAS-419: --- Updating: https://cwiki.apache.org/confluence/display/ATLAS/Developer+Resources > Document release steps in wiki > -- > > Key: ATLAS-419 > URL: https://issues.apache.org/jira/browse/ATLAS-419 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-419) Document release steps in wiki
[ https://issues.apache.org/jira/browse/ATLAS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-419: - Assignee: Shwetha G S (was: Suma Shivaprasad) > Document release steps in wiki > -- > > Key: ATLAS-419 > URL: https://issues.apache.org/jira/browse/ATLAS-419 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-82) Secure kafka calls
[ https://issues.apache.org/jira/browse/ATLAS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-82. -- Resolution: Fixed Secure calls from atlas to kafka is available on trunk > Secure kafka calls > -- > > Key: ATLAS-82 > URL: https://issues.apache.org/jira/browse/ATLAS-82 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > depends on KAFKA-1682 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-94) Re-use of trait instance
[ https://issues.apache.org/jira/browse/ATLAS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-94. -- Resolution: Duplicate > Re-use of trait instance > > > Key: ATLAS-94 > URL: https://issues.apache.org/jira/browse/ATLAS-94 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > Currently, we create new instance for trait everytime trait is added/entity > is created. This can explode the graph. Need a way to re-use the trait > instance across entities -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-934) Exclude temp files in source package
[
https://issues.apache.org/jira/browse/ATLAS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343817#comment-15343817
]
Shwetha G S edited comment on ATLAS-934 at 6/22/16 7:03 AM:
Fixed typo, updated patch that works
was (Author: shwethags):
Fixed type, ppdated patch that works
> Exclude temp files in source package
>
>
> Key: ATLAS-934
> URL: https://issues.apache.org/jira/browse/ATLAS-934
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-934-v2.patch, ATLAS-934.patch
>
>
> Following needs to be excluded in source package:
> {noformat}
> distro/hbase
> distro/solr
> **/${sys:atlas.data}
> **/atlas.data
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-934) Exclude temp files in source package
[
https://issues.apache.org/jira/browse/ATLAS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-934:
--
Attachment: ATLAS-934-v2.patch
Fixed type, ppdated patch that works
> Exclude temp files in source package
>
>
> Key: ATLAS-934
> URL: https://issues.apache.org/jira/browse/ATLAS-934
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-934-v2.patch, ATLAS-934.patch
>
>
> Following needs to be excluded in source package:
> {noformat}
> distro/hbase
> distro/solr
> **/${sys:atlas.data}
> **/atlas.data
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-934) Exclude temp files in source package
[
https://issues.apache.org/jira/browse/ATLAS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-934:
--
Attachment: ATLAS-934.patch
> Exclude temp files in source package
>
>
> Key: ATLAS-934
> URL: https://issues.apache.org/jira/browse/ATLAS-934
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-934.patch
>
>
> Following needs to be excluded in source package:
> {noformat}
> distro/hbase
> distro/solr
> **/${sys:atlas.data}
> **/atlas.data
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-934) Exclude temp files in source package
[
https://issues.apache.org/jira/browse/ATLAS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-934:
--
Description:
Following needs to be excluded in source package:
{noformat}
distro/hbase
distro/solr
**/${sys:atlas.data}
**/atlas.data
{noformat}
was:
Following needs to be excluded in source package:
distro/hbase
distro/solr
**/${sys:atlas.data}
**/atlas.data
> Exclude temp files in source package
>
>
> Key: ATLAS-934
> URL: https://issues.apache.org/jira/browse/ATLAS-934
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-934.patch
>
>
> Following needs to be excluded in source package:
> {noformat}
> distro/hbase
> distro/solr
> **/${sys:atlas.data}
> **/atlas.data
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-934) Exclude temp files in source package
Shwetha G S created ATLAS-934:
-
Summary: Exclude temp files in source package
Key: ATLAS-934
URL: https://issues.apache.org/jira/browse/ATLAS-934
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Fix For: 0.7-incubating
Following needs to be excluded in source package:
distro/hbase
distro/solr
**/${sys:atlas.data}
**/atlas.data
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-856) Lazy-load type cache provider
[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-856: -- Attachment: ATLAS-856-final.patch Committed patch after fixing the checkstyle issue > Lazy-load type cache provider > - > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature >Reporter: David Kantor >Assignee: David Kantor > Fix For: 0.7-incubating > > Attachments: ATLAS-856-final.patch, ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-933) Test failure: HiveHookIT.testInsertIntoTable
Shwetha G S created ATLAS-933:
-
Summary: Test failure: HiveHookIT.testInsertIntoTable
Key: ATLAS-933
URL: https://issues.apache.org/jira/browse/ATLAS-933
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Fix For: 0.7-incubating
Attachments: ATLAS-933.patch
{noformat}
Tests run: 45, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.454 sec <<<
FAILURE! - in org.apache.atlas.hive.hook.HiveHookIT
testInsertIntoTable(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: 2.097
sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API GET_ENTITY failed
with status 500(Internal Server Error) Response Body ({"error":"Could not
execute operation due to backend
exception","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could not
execute operation due to backend exception\n\tat
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)\n\tat
com.thinkaurelius.titan.diskstorage.BackendTransaction.executeRead(BackendTransaction.java:428)\n\tat
com.thinkaurelius.titan.diskstorage.BackendTransaction.edgeStoreQuery(BackendTransaction.java:253)\n\tat
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.edgeQuery(StandardTitanGraph.java:365)\n\tat
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:109)\n\tat
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:106)\n\tat
com.thinkaurelius.titan.graphdb.vertices.CacheVertex.loadRelations(CacheVertex.java:47)\n\tat
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.getBasicIterator(SimpleVertexQueryProcessor.java:106)\n\tat
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.iterator(SimpleVertexQueryProcessor.java:63)\n\tat
com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1$1.(RelationConstructor.java:36)\n\tat
com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1.iterator(RelationConstructor.java:34)\n\tat
org.apache.atlas.repository.graph.GraphHelper.getTraitNames(GraphHelper.java:325)\n\tat
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:70)\n\tat
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToClassReference(GraphToTypedInstanceMapper.java:176)\n\tat
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToAttribute(GraphToTypedInstanceMapper.java:146)\n\tat
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToInstance(GraphToTypedInstanceMapper.java:101)\n\tat
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:80)\n\tat
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:167)\n\tat
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)\n\tat
org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:398)\n\tat
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:403)\n\tat
org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:515)\n\tat
org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:497)\n\tat
sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:606)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.serv
[jira] [Updated] (ATLAS-933) Test failure: HiveHookIT.testInsertIntoTable
[
https://issues.apache.org/jira/browse/ATLAS-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-933:
--
Attachment: ATLAS-933.patch
> Test failure: HiveHookIT.testInsertIntoTable
>
>
> Key: ATLAS-933
> URL: https://issues.apache.org/jira/browse/ATLAS-933
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-933.patch
>
>
> {noformat}
> Tests run: 45, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.454 sec
> <<< FAILURE! - in org.apache.atlas.hive.hook.HiveHookIT
> testInsertIntoTable(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed:
> 2.097 sec <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API GET_ENTITY
> failed with status 500(Internal Server Error) Response Body ({"error":"Could
> not execute operation due to backend
> exception","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not execute operation due to backend exception\n\tat
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)\n\tat
>
> com.thinkaurelius.titan.diskstorage.BackendTransaction.executeRead(BackendTransaction.java:428)\n\tat
>
> com.thinkaurelius.titan.diskstorage.BackendTransaction.edgeStoreQuery(BackendTransaction.java:253)\n\tat
>
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.edgeQuery(StandardTitanGraph.java:365)\n\tat
>
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:109)\n\tat
>
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:106)\n\tat
>
> com.thinkaurelius.titan.graphdb.vertices.CacheVertex.loadRelations(CacheVertex.java:47)\n\tat
>
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.getBasicIterator(SimpleVertexQueryProcessor.java:106)\n\tat
>
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.iterator(SimpleVertexQueryProcessor.java:63)\n\tat
>
> com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1$1.(RelationConstructor.java:36)\n\tat
>
> com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1.iterator(RelationConstructor.java:34)\n\tat
>
> org.apache.atlas.repository.graph.GraphHelper.getTraitNames(GraphHelper.java:325)\n\tat
>
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:70)\n\tat
>
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToClassReference(GraphToTypedInstanceMapper.java:176)\n\tat
>
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToAttribute(GraphToTypedInstanceMapper.java:146)\n\tat
>
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToInstance(GraphToTypedInstanceMapper.java:101)\n\tat
>
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:80)\n\tat
>
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:167)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:398)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:403)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:515)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:497)\n\tat
> sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)\n\tat
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun
[jira] [Updated] (ATLAS-856) Lazy-load type cache provider
[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-856: -- Fix Version/s: 0.7-incubating > Lazy-load type cache provider > - > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature >Reporter: David Kantor >Assignee: David Kantor > Fix For: 0.7-incubating > > Attachments: ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter
[ https://issues.apache.org/jira/browse/ATLAS-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-584: -- Fix Version/s: (was: 0.7-incubating) > Integrate CSRF prevention filter > > > Key: ATLAS-584 > URL: https://issues.apache.org/jira/browse/ATLAS-584 > Project: Atlas > Issue Type: Task >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: Kalyani Kashikar >Priority: Blocker > > Atlas needs to provide protection for CSRF protection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter
[ https://issues.apache.org/jira/browse/ATLAS-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-584: -- Priority: Major (was: Blocker) > Integrate CSRF prevention filter > > > Key: ATLAS-584 > URL: https://issues.apache.org/jira/browse/ATLAS-584 > Project: Atlas > Issue Type: Task >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: Kalyani Kashikar > > Atlas needs to provide protection for CSRF protection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-856) Lazy-load type cache provider
[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342221#comment-15342221 ] Shwetha G S commented on ATLAS-856: --- [~dkantor], the attached patch has some changes to not create atlas-application.properties in respository/test. See if the changes make sense to you > Lazy-load type cache provider > - > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature >Reporter: David Kantor >Assignee: David Kantor > Attachments: ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-856) Lazy-load type cache provider
[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-856: -- Attachment: ATLAS-856.patch > Lazy-load type cache provider > - > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature >Reporter: David Kantor >Assignee: David Kantor > Attachments: ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342023#comment-15342023
]
Shwetha G S commented on ATLAS-930:
---
+1, committing
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-930.patch, application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:
[jira] [Updated] (ATLAS-822) Type updates - don't allow updating supertypes
[ https://issues.apache.org/jira/browse/ATLAS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-822: -- Attachment: ATLAS-822-v2.patch Fixed webapp IT > Type updates - don't allow updating supertypes > -- > > Key: ATLAS-822 > URL: https://issues.apache.org/jira/browse/ATLAS-822 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-822-v2.patch, ATLAS-822.patch > > > In type updates, we allow adding super types. But set of super types is > maintained in every entity, and this type update will require updating all > the entities of that type which is not handled currently. We should either > update all entities or not allow updating super type information -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-698) Remove Rexster Graph API
[ https://issues.apache.org/jira/browse/ATLAS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-698: -- Summary: Remove Rexster Graph API (was: Remove Rexster Graph and Gremlin REST API) > Remove Rexster Graph API > > > Key: ATLAS-698 > URL: https://issues.apache.org/jira/browse/ATLAS-698 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: Vimal Sharma > Fix For: 0.7-incubating > > Attachments: ATLAS-698-v2.patch, ATLAS-698-v3.patch, ATLAS-698.patch > > > Since these expose the internals of Atlas and are not intended for public > consumption, these should be removed: > api/atlas/graph > api/atlas/discovery/search/gremlin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-822) Type updates - don't allow updating supertypes
[ https://issues.apache.org/jira/browse/ATLAS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-822: -- Summary: Type updates - don't allow updating supertypes (was: Type updates - add supertypes) > Type updates - don't allow updating supertypes > -- > > Key: ATLAS-822 > URL: https://issues.apache.org/jira/browse/ATLAS-822 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-822.patch > > > In type updates, we allow adding super types. But set of super types is > maintained in every entity, and this type update will require updating all > the entities of that type which is not handled currently. We should either > update all entities or not allow updating super type information -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-822) Type updates - add supertypes
[ https://issues.apache.org/jira/browse/ATLAS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-822: -- Attachment: ATLAS-822.patch Type update will not allow updating super types > Type updates - add supertypes > - > > Key: ATLAS-822 > URL: https://issues.apache.org/jira/browse/ATLAS-822 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-822.patch > > > In type updates, we allow adding super types. But set of super types is > maintained in every entity, and this type update will require updating all > the entities of that type which is not handled currently. We should either > update all entities or not allow updating super type information -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-929) Add test for trait preservation on column rename for non-default database
[ https://issues.apache.org/jira/browse/ATLAS-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341505#comment-15341505 ] Shwetha G S commented on ATLAS-929: --- +1. Thanks [~suma.shivaprasad] for finding the issue and giving the code fix > Add test for trait preservation on column rename for non-default database > - > > Key: ATLAS-929 > URL: https://issues.apache.org/jira/browse/ATLAS-929 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-929.patch > > > The patch for ATLAS-752 had a bug where HiveHook assumes the table to reside > in the default database in Hive. > Add a testcase to verify the fix for non-default database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-925) Change master version to 0.8-incubating
[ https://issues.apache.org/jira/browse/ATLAS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-925: -- Fix Version/s: 0.8-incubating > Change master version to 0.8-incubating > --- > > Key: ATLAS-925 > URL: https://issues.apache.org/jira/browse/ATLAS-925 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-925-v2.patch, ATLAS-925.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-499) Automatically update inverse references to prevent repository corruption
[ https://issues.apache.org/jira/browse/ATLAS-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-499: -- Fix Version/s: (was: 0.7-incubating) > Automatically update inverse references to prevent repository corruption > > > Key: ATLAS-499 > URL: https://issues.apache.org/jira/browse/ATLAS-499 > Project: Atlas > Issue Type: Improvement >Reporter: David Kantor >Assignee: David Kantor > > For references that are defined in the type system as bi-directional, Atlas > does not enforce that clients update both sides of the reference, and relies > on well behaved client applications for repository consistency. This allows > the repository to be easily corrupted with unbalanced references. Atlas > should automatically update the inverse reference to avoid this corruption. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-926) Change version in 0.7 branch to 0.7-incubating
[ https://issues.apache.org/jira/browse/ATLAS-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-926: -- Attachment: ATLAS-926.patch > Change version in 0.7 branch to 0.7-incubating > -- > > Key: ATLAS-926 > URL: https://issues.apache.org/jira/browse/ATLAS-926 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-926.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-925) Change master version to 0.8-incubating
[ https://issues.apache.org/jira/browse/ATLAS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-925: -- Attachment: ATLAS-925-v2.patch 1. Added another section for trunk in release-log.txt 2. Fixed storm-bridge dependency in distro/pom.xml > Change master version to 0.8-incubating > --- > > Key: ATLAS-925 > URL: https://issues.apache.org/jira/browse/ATLAS-925 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-925-v2.patch, ATLAS-925.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version
Shwetha G S created ATLAS-927:
-
Summary: aboutAtlas_tmpl.html has hard-coded project version
Key: ATLAS-927
URL: https://issues.apache.org/jira/browse/ATLAS-927
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Keval Bhatt
dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded
version:
{code}
Version :
0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
{code}
Instead, it should use mvn resource filtering to set the version to project
version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-925) Change master version to 0.8-incubating
[ https://issues.apache.org/jira/browse/ATLAS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-925: -- Attachment: ATLAS-925.patch > Change master version to 0.8-incubating > --- > > Key: ATLAS-925 > URL: https://issues.apache.org/jira/browse/ATLAS-925 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-925.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-925) Change master version to 0.8-incubating
Shwetha G S created ATLAS-925: - Summary: Change master version to 0.8-incubating Key: ATLAS-925 URL: https://issues.apache.org/jira/browse/ATLAS-925 Project: Atlas Issue Type: Sub-task Reporter: Shwetha G S Assignee: Shwetha G S Fix For: 0.7-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-926) Change version in 0.7 branch to 0.7-incubating
Shwetha G S created ATLAS-926: - Summary: Change version in 0.7 branch to 0.7-incubating Key: ATLAS-926 URL: https://issues.apache.org/jira/browse/ATLAS-926 Project: Atlas Issue Type: Sub-task Reporter: Shwetha G S Assignee: Shwetha G S Fix For: 0.7-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-924) Release 0.7-incubating
Shwetha G S created ATLAS-924: - Summary: Release 0.7-incubating Key: ATLAS-924 URL: https://issues.apache.org/jira/browse/ATLAS-924 Project: Atlas Issue Type: Task Reporter: Shwetha G S Fix For: 0.7-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-923) Hive hook: hive_table.description should be set to table comments
Shwetha G S created ATLAS-923: - Summary: Hive hook: hive_table.description should be set to table comments Key: ATLAS-923 URL: https://issues.apache.org/jira/browse/ATLAS-923 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S ATLAS-819 added description attribute to hive_table. But description is not set, it can be set to table comment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-919) UI : Deleted references should be filtered out
[ https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-919: -- Fix Version/s: (was: 0.7-incubating) > UI : Deleted references should be filtered out > -- > > Key: ATLAS-919 > URL: https://issues.apache.org/jira/browse/ATLAS-919 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Suma Shivaprasad >Assignee: Keval Bhatt >Priority: Critical > Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, Screen Shot > 2016-06-20 at 3.56.33 PM.png > > > Foe eg: In a hive_table one of the columns could be dropped in which case the > columns array will have the deleted column as well. This could be completely > filtered out in the UI. The way to identify this is to check if the entity > state is DELETED when going through the references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-819) All user defined types should have a set of common attributes
[ https://issues.apache.org/jira/browse/ATLAS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341063#comment-15341063 ] Shwetha G S commented on ATLAS-819: --- Yes, the plan is to return system attributes as well. But since they can't be modified, they won't be part of type system. We will return createTime, lastModifiedTime, createdUser and modifiedUser in get entity definition along with id and state. It will be handled in ATLAS-916 > All user defined types should have a set of common attributes > - > > Key: ATLAS-819 > URL: https://issues.apache.org/jira/browse/ATLAS-819 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-819-v2.patch, ATLAS-819.patch > > > It would be very convenient if all user defined types have a conventional set > of common attributes including: > * name > * description > * owner > * created at > * modified at -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-822) Type updates - add supertypes
[ https://issues.apache.org/jira/browse/ATLAS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-822: - Assignee: Shwetha G S > Type updates - add supertypes > - > > Key: ATLAS-822 > URL: https://issues.apache.org/jira/browse/ATLAS-822 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > > In type updates, we allow adding super types. But set of super types is > maintained in every entity, and this type update will require updating all > the entities of that type which is not handled currently. We should either > update all entities or not allow updating super type information -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-493) Entity Versioning Support - Audit only
[ https://issues.apache.org/jira/browse/ATLAS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-493: -- Fix Version/s: (was: 0.7-incubating) > Entity Versioning Support - Audit only > -- > > Key: ATLAS-493 > URL: https://issues.apache.org/jira/browse/ATLAS-493 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: Shwetha G S > > General Use Case > Atlas must be able to track the evolution of assets as they change. Each > evolution (or version) of each asset must be recorded in order to track > lineage > Delete Use Case > If an asset is deleted, the asset should not show up searches unless > explicitly searched for. > Requirements > Be able to show changes over time to be implemented through Audit Log > Requires API support to retrieve history -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-589) Document entity audit
[ https://issues.apache.org/jira/browse/ATLAS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-589: -- Fix Version/s: (was: 0.7-incubating) > Document entity audit > - > > Key: ATLAS-589 > URL: https://issues.apache.org/jira/browse/ATLAS-589 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-822) Type updates - add supertypes
[ https://issues.apache.org/jira/browse/ATLAS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339940#comment-15339940 ] Shwetha G S commented on ATLAS-822: --- Yes, we shouldn't allow updating supertypes > Type updates - add supertypes > - > > Key: ATLAS-822 > URL: https://issues.apache.org/jira/browse/ATLAS-822 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Fix For: 0.7-incubating > > > In type updates, we allow adding super types. But set of super types is > maintained in every entity, and this type update will require updating all > the entities of that type which is not handled currently. We should either > update all entities or not allow updating super type information -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-807) Search for entities in v1 API could be very costly.
[
https://issues.apache.org/jira/browse/ATLAS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-807:
--
Fix Version/s: (was: 0.7-incubating)
> Search for entities in v1 API could be very costly.
> ---
>
> Key: ATLAS-807
> URL: https://issues.apache.org/jira/browse/ATLAS-807
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>
> As part of ATLAS-491, there is a new entity search API that uses Lucene
> syntax. This search could be very costly, because the starting pipeline
> filters for those vertices which have an attribute {entityText}. This is
> added for pretty much every entity added to Atlas. So the Gremlin pipeline
> could result in a lot of results. I am not entirely sure what the impact of
> this will be, but filing it to keep track of analysis.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-828) Entity audit creates lot of records for unchanged entities or irrelevant updates
[ https://issues.apache.org/jira/browse/ATLAS-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-828: -- Fix Version/s: (was: 0.7-incubating) > Entity audit creates lot of records for unchanged entities or irrelevant > updates > > > Key: ATLAS-828 > URL: https://issues.apache.org/jira/browse/ATLAS-828 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala > > Run a script to create 100 hive_tables in the same database. > There will be about 100 audit records for the database indicating there was > an entity update on it. The information in each update is the same (probably > there's some timestamp that's changing, haven't looked very carefully). > This is not very useful information, and is likely to make users miss more > relevant updates to the DB entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-819) All user defined types should have a set of common attributes
[ https://issues.apache.org/jira/browse/ATLAS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-819: -- Attachment: ATLAS-819-v2.patch Addressed review comments > All user defined types should have a set of common attributes > - > > Key: ATLAS-819 > URL: https://issues.apache.org/jira/browse/ATLAS-819 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-819-v2.patch, ATLAS-819.patch > > > It would be very convenient if all user defined types have a conventional set > of common attributes including: > * name > * description > * owner > * created at > * modified at -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-591) Atlas client ssl configuration failure
[
https://issues.apache.org/jira/browse/ATLAS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-591:
--
Fix Version/s: (was: 0.7-incubating)
> Atlas client ssl configuration failure
> --
>
> Key: ATLAS-591
> URL: https://issues.apache.org/jira/browse/ATLAS-591
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>
> When server is not set-up with ssl, client shouldn't configure params for ssl
> {noformat}
> 2016-03-23 13:59:35,013 DEBUG [main]: atlas.ApplicationProperties
> (ApplicationProperties.java:logConfiguration(86)) - atlas.enableTLS = false
> 2016-03-23 13:59:35,018 DEBUG [main]: atlas.ApplicationProperties
> (ApplicationProperties.java:logConfiguration(86)) - atlas.rest.address =
> http://localhost:21000
> 2016-03-23 13:59:35,420 DEBUG [Atlas Logger 0]: security.SecureClientUtils
> (SecureClientUtils.java:newConnConfigurator(138)) - Cannot load customized
> ssl related configuration. Fallback to system-generic settings.
> java.io.FileNotFoundException: /etc/security/clientKeys/all.jks (No such file
> or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.loadTrustManager(ReloadingX509TrustManager.java:164)
> at
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.(ReloadingX509TrustManager.java:81)
> at
> org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.init(FileBasedKeyStoresFactory.java:209)
> at org.apache.hadoop.security.ssl.SSLFactory.init(SSLFactory.java:131)
> at
> org.apache.atlas.security.SecureClientUtils.newSslConnConfigurator(SecureClientUtils.java:150)
> at
> org.apache.atlas.security.SecureClientUtils.newConnConfigurator(SecureClientUtils.java:136)
> at
> org.apache.atlas.security.SecureClientUtils.getClientConnectionHandler(SecureClientUtils.java:69)
> at org.apache.atlas.AtlasClient.(AtlasClient.java:126)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.(HiveMetaStoreBridge.java:97)
> at
> org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:195)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:62)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:181)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-660) Validate that same entity is part of two composite references
[ https://issues.apache.org/jira/browse/ATLAS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-660: -- Fix Version/s: (was: 0.7-incubating) > Validate that same entity is part of two composite references > - > > Key: ATLAS-660 > URL: https://issues.apache.org/jira/browse/ATLAS-660 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > Currently, atlas allows an entity to be part of composite references of two > parent entities. For example, hive_column is a composite attribute of > hive_table. A hive_column entity can't be part of two different hive_table > entities (by the definition of composite which means child entity's lifecycle > depends on parent entity's lifecycle) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-676) Enforcing unique attribute values for struct/trait
[ https://issues.apache.org/jira/browse/ATLAS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-676: -- Fix Version/s: (was: 0.7-incubating) > Enforcing unique attribute values for struct/trait > -- > > Key: ATLAS-676 > URL: https://issues.apache.org/jira/browse/ATLAS-676 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > > In ATLAS-622, titan doesn't handle unique attributes anymore and it needs to > be handled manually. The jira takes care of enforcing uniqueness on first > unique attribute of the class type as part of entity de-duping. But > uniqueness on struct/trait attributes are not handled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-811) Entity delete should check for required reverse references - soft deletes
[ https://issues.apache.org/jira/browse/ATLAS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-811: -- Fix Version/s: (was: 0.7-incubating) > Entity delete should check for required reverse references - soft deletes > - > > Key: ATLAS-811 > URL: https://issues.apache.org/jira/browse/ATLAS-811 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > > DeleteHandler.deleteEdgeBetweenVertices() checks for elements.size(). With > soft deletes, even the deleted elements are part of the array. It should > instead check for active elements -- This message was sent by Atlassian JIRA (v6.3.4#6332)
