[jira] [Updated] (ATLAS-806) Business Taxonomy related types should be registered one time on server startup.
[ https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-806: --- Attachment: ATLAS-806.patch > Business Taxonomy related types should be registered one time on 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: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-806.patch > > > The Taxonomy type is currently being registered on the first call to the API. > We have seen this could have issues if calls are made in parallel - as could > happen in a web situation. Atlas already has the necessary framework to > register types at startup time which was introduced as part of ATLAS-512. > This should be used here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-794) Business Catalog Update
[ https://issues.apache.org/jira/browse/ATLAS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328007#comment-15328007 ] John Speidel edited comment on ATLAS-794 at 6/13/16 7:29 PM: - New patch (ATLAS-794-3.patch) with changes to address 400 response when attempting to update taxonomy name. was (Author: jspeidel): Changes to address 400 response when attempting to update taxonomy name. > Business Catalog Update > --- > > Key: ATLAS-794 > URL: https://issues.apache.org/jira/browse/ATLAS-794 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-794-2.patch, ATLAS-794-3.patch, ATLAS-794.patch > > > Business Catalog should support Update of all fields of a Term -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-794) Business Catalog Update
[ https://issues.apache.org/jira/browse/ATLAS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-794: --- Attachment: ATLAS-794-3.patch Changes to address 400 response when attempting to update taxonomy name. > Business Catalog Update > --- > > Key: ATLAS-794 > URL: https://issues.apache.org/jira/browse/ATLAS-794 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-794-2.patch, ATLAS-794-3.patch, ATLAS-794.patch > > > Business Catalog should support Update of all fields of a Term -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-794) Business Catalog Update
[ https://issues.apache.org/jira/browse/ATLAS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-794: --- Attachment: ATLAS-794-2.patch patch v2 addresses issues raised in review > Business Catalog Update > --- > > Key: ATLAS-794 > URL: https://issues.apache.org/jira/browse/ATLAS-794 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-794-2.patch, ATLAS-794.patch > > > Business Catalog should support Update of all fields of a Term -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-794) Business Catalog Update
[
https://issues.apache.org/jira/browse/ATLAS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323810#comment-15323810
]
John Speidel edited comment on ATLAS-794 at 6/10/16 3:35 AM:
-
Supports updating of taxonomy and term property values not including the 'name'
property. Only one taxonomy or term can be updated at a time with this patch.
Allowing for updates of multiple taxonomies/terms based on a query isn't
included in this patch and would be ~ 1 additional days work.
{code}
Usage: PUT api/v1/taxonomies/taxonomy1/terms/term1
{
"description" : "newValue"
}
{code}
was (Author: jspeidel):
Supports updating of taxonomy and term property values not including the 'name'
property. Only one taxonomy or term can be updated at a time with this patch.
Allowing for updates of multiple taxonomies/terms based on a query isn't
included in this patch and would be ~ 1 additional days work.
Usage: PUT api/v1/taxonomies/taxonomy1/terms/term1
{
"description" : "newValue"
}
> Business Catalog Update
> ---
>
> Key: ATLAS-794
> URL: https://issues.apache.org/jira/browse/ATLAS-794
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-794.patch
>
>
> Business Catalog should support Update of all fields of a Term
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-794) Business Catalog Update
[
https://issues.apache.org/jira/browse/ATLAS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Speidel updated ATLAS-794:
---
Attachment: ATLAS-794.patch
Supports updating of taxonomy and term property values not including the 'name'
property. Only one taxonomy or term can be updated at a time with this patch.
Allowing for updates of multiple taxonomies/terms based on a query isn't
included in this patch and would be ~ 1 additional days work.
Usage: PUT api/v1/taxonomies/taxonomy1/terms/term1
{
"description" : "newValue"
}
> Business Catalog Update
> ---
>
> Key: ATLAS-794
> URL: https://issues.apache.org/jira/browse/ATLAS-794
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-794.patch
>
>
> Business Catalog should support Update of all fields of a Term
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-794) Business Catalog Update
[
https://issues.apache.org/jira/browse/ATLAS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323810#comment-15323810
]
John Speidel edited comment on ATLAS-794 at 6/10/16 3:35 AM:
-
Supports updating of taxonomy and term property values not including the 'name'
property. Only one taxonomy or term can be updated at a time with this patch.
Allowing for updates of multiple taxonomies/terms based on a query isn't
included in this patch and would be ~ 1 additional days work.
USAGE:
{code}
PUT api/v1/taxonomies/taxonomy1/terms/term1
{
"description" : "newValue"
}
{code}
was (Author: jspeidel):
Supports updating of taxonomy and term property values not including the 'name'
property. Only one taxonomy or term can be updated at a time with this patch.
Allowing for updates of multiple taxonomies/terms based on a query isn't
included in this patch and would be ~ 1 additional days work.
{code}
Usage: PUT api/v1/taxonomies/taxonomy1/terms/term1
{
"description" : "newValue"
}
{code}
> Business Catalog Update
> ---
>
> Key: ATLAS-794
> URL: https://issues.apache.org/jira/browse/ATLAS-794
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-794.patch
>
>
> Business Catalog should support Update of all fields of a Term
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-858) Unable to delete terms via API which are 3 or more levels deep
[ https://issues.apache.org/jira/browse/ATLAS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316952#comment-15316952 ] John Speidel commented on ATLAS-858: Yes, that also works, and is an acceptable use (shorter url's) but don't provide for an explicit hierarchy. The url's with the explicit hierarchy are the "official" url's which are returned by the api to the user. > Unable to delete terms via API which are 3 or more levels deep > -- > > Key: ATLAS-858 > URL: https://issues.apache.org/jira/browse/ATLAS-858 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: John Speidel >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-858.patch > > > Attempting to delete a term that is 3 or more levels deep results in an error > response: > DELETE > api/atlas/v1/taxonomies/taxonomy1/terms/term1/terms/term11/terms/term111 > 405 - Method Not Allowed > This is because I for got to add a service method for deleting sub terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-845) Atlas UI to delete terms using API
[ https://issues.apache.org/jira/browse/ATLAS-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314890#comment-15314890 ] John Speidel commented on ATLAS-845: The issue described above where deleting sub-terms fails with 405 status is being tracked by ATLAS-858. > Atlas UI to delete terms using API > -- > > Key: ATLAS-845 > URL: https://issues.apache.org/jira/browse/ATLAS-845 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.7-incubating >Reporter: Keval Bhatt >Assignee: Kalyani Kashikar > Fix For: 0.7-incubating > > Attachments: ATLAS-845.1.patch, ATLAS-845.patch > > > Providing delete term feature using delete term api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-858) Unable to delete terms via API which are 3 or more levels deep
[ https://issues.apache.org/jira/browse/ATLAS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314878#comment-15314878 ] John Speidel commented on ATLAS-858: This issue was originally reported in ATLAS-845. > Unable to delete terms via API which are 3 or more levels deep > -- > > Key: ATLAS-858 > URL: https://issues.apache.org/jira/browse/ATLAS-858 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: John Speidel >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-858.patch > > > Attempting to delete a term that is 3 or more levels deep results in an error > response: > DELETE > api/atlas/v1/taxonomies/taxonomy1/terms/term1/terms/term11/terms/term111 > 405 - Method Not Allowed > This is because I for got to add a service method for deleting sub terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-858) Unable to delete terms via API which are 3 or more levels deep
[ https://issues.apache.org/jira/browse/ATLAS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-858: --- Attachment: ATLAS-858.patch > Unable to delete terms via API which are 3 or more levels deep > -- > > Key: ATLAS-858 > URL: https://issues.apache.org/jira/browse/ATLAS-858 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: John Speidel >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-858.patch > > > Attempting to delete a term that is 3 or more levels deep results in an error > response: > DELETE > api/atlas/v1/taxonomies/taxonomy1/terms/term1/terms/term11/terms/term111 > 405 - Method Not Allowed > This is because I for got to add a service method for deleting sub terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-858) Unable to delete terms via API which are 3 or more levels deep
John Speidel created ATLAS-858: -- Summary: Unable to delete terms via API which are 3 or more levels deep Key: ATLAS-858 URL: https://issues.apache.org/jira/browse/ATLAS-858 Project: Atlas Issue Type: Bug Affects Versions: 0.7-incubating Reporter: John Speidel Assignee: John Speidel Fix For: 0.7-incubating Attempting to delete a term that is 3 or more levels deep results in an error response: DELETE api/atlas/v1/taxonomies/taxonomy1/terms/term1/terms/term11/terms/term111 405 - Method Not Allowed This is because I for got to add a service method for deleting sub terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-845) Atlas UI to delete terms using API
[ https://issues.apache.org/jira/browse/ATLAS-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312829#comment-15312829 ] John Speidel commented on ATLAS-845: The above comment was regarding deleting terms > 3 levels deep. > Atlas UI to delete terms using API > -- > > Key: ATLAS-845 > URL: https://issues.apache.org/jira/browse/ATLAS-845 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.7-incubating >Reporter: Keval Bhatt >Assignee: Kalyani Kashikar > Fix For: 0.7-incubating > > Attachments: ATLAS-845.patch > > > Providing delete term feature using delete term api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-845) Atlas UI to delete terms using API
[ https://issues.apache.org/jira/browse/ATLAS-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312827#comment-15312827 ] John Speidel commented on ATLAS-845: I have reproduced this issue and understand the root cause. I should have a patch available either today or tomorrow. > Atlas UI to delete terms using API > -- > > Key: ATLAS-845 > URL: https://issues.apache.org/jira/browse/ATLAS-845 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.7-incubating >Reporter: Keval Bhatt >Assignee: Kalyani Kashikar > Fix For: 0.7-incubating > > Attachments: ATLAS-845.patch > > > Providing delete term feature using delete term api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312390#comment-15312390 ] John Speidel commented on ATLAS-793: I agree with this approach [~yhemanth]. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793-2.patch, ATLAS-793-3.patch, ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311174#comment-15311174 ] John Speidel commented on ATLAS-793: I finally reproduced this after many, many attempts today. In the case where I did reproduce it, I hadn't yet run quick start. I saw the message once, and couldn't cause the issue again. As I just reproduced this, and can't cause the issue again at the moment, I still haven't identified a root cause. This issue didn't noticeably affect the user requests meaning that all taxonomy and term creations where successful as were all UI interactions as well as api requests. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793-2.patch, ATLAS-793-3.patch, ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310352#comment-15310352 ] John Speidel commented on ATLAS-793: Great, I will try your steps to see if I can reproduce. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793-2.patch, ATLAS-793-3.patch, ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-793: --- Attachment: ATLAS-793-3.patch Latest patch (ATLAS-793-3.patch) addresses the warning about query not being indexed and doing a full vertex scan. This patch doesn't address the transaction timeout issue as I wasn't able to reproduce after more than one hour attempting to do so. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793-2.patch, ATLAS-793-3.patch, ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-793: --- Attachment: ATLAS-793-2.patch Uploaded new patch 'ATLAS-793-2.patch' which contains changes for all review issues unless otherwise noted in the review. Also, doesn't address the comments included in this Jira as described in my comments. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793-2.patch, ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304581#comment-15304581 ] John Speidel commented on ATLAS-793: [~yhemanth] At this time I don't know why the above transaction timeout message occurs. I will post a new patch with changes for the issues raised in the review and will then investigate this message. Perhaps we file a new Jira for this issue so that we can make the delete functionality available while I am investigating? > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304570#comment-15304570 ] John Speidel commented on ATLAS-793: [~yhemanth] The reason for this log message is because I added a clause to all queries to return only non-deleted (active) vertices. This clause is basically (Constants.STATE_PROPERTY_KEY:ACTIVE). At this time, this property isn't indexed by Atlas which results in a non-indexed vertex scan. This clause is required in the query to ensure that deleted vertices aren't returned. Let me know if you would like me to add this index in GraphBackedSearchIndexer.java. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-793) Business Catalog Delete
[ https://issues.apache.org/jira/browse/ATLAS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302306#comment-15302306 ] John Speidel commented on ATLAS-793: This patch doesn't delete term 'types' because this functionality isn't exposed in MetadataService or MetadataRepository. This doesn't effect business catalog but if users query /types after deleting terms in a taxonomy, the type will still exist. > Business Catalog Delete > --- > > Key: ATLAS-793 > URL: https://issues.apache.org/jira/browse/ATLAS-793 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: ATLAS-793.patch > > > Business Catalog API should support deletion of Terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-805) Quickstart is failing if run after queries to the business taxonomy API
[
https://issues.apache.org/jira/browse/ATLAS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289841#comment-15289841
]
John Speidel commented on ATLAS-805:
I have attached a patch for the issue where transactions weren't committed in
BaseQuery of the catalog module.
Also added a test that asserts that the transaction is committed.
Note: Although this does fix this issue in this exact case, we should really
consider intercepting each request and calling graph.rollback() to ensure that
the thread wasn't re-pooled without being committed or rolled back.
> Quickstart is failing if run after queries to the business taxonomy API
> ---
>
> Key: ATLAS-805
> URL: https://issues.apache.org/jira/browse/ATLAS-805
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-805.patch, application.log
>
>
> * On a fresh Atlas server, using a REST client like curl or Postman, make a
> call to the business taxonomy API. E.g.
> http://localhost:21000/api/atlas/v1/taxonomies
> * This will return an empty result set
> * Run quick_start.py.
> This fails with an exception as follows:
> {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:321)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:316)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)\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
>
[jira] [Updated] (ATLAS-805) Quickstart is failing if run after queries to the business taxonomy API
[
https://issues.apache.org/jira/browse/ATLAS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Speidel updated ATLAS-805:
---
Attachment: ATLAS-805.patch
> Quickstart is failing if run after queries to the business taxonomy API
> ---
>
> Key: ATLAS-805
> URL: https://issues.apache.org/jira/browse/ATLAS-805
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-805.patch, application.log
>
>
> * On a fresh Atlas server, using a REST client like curl or Postman, make a
> call to the business taxonomy API. E.g.
> http://localhost:21000/api/atlas/v1/taxonomies
> * This will return an empty result set
> * Run quick_start.py.
> This fails with an exception as follows:
> {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:321)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:316)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)\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
>
[jira] [Commented] (ATLAS-805) Quickstart is failing if run after queries to the business taxonomy API
[
https://issues.apache.org/jira/browse/ATLAS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289335#comment-15289335
]
John Speidel commented on ATLAS-805:
oops, wrong Hemanth. Sorry.
I meant to specify: [~yhemanth]
> Quickstart is failing if run after queries to the business taxonomy API
> ---
>
> Key: ATLAS-805
> URL: https://issues.apache.org/jira/browse/ATLAS-805
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: application.log
>
>
> * On a fresh Atlas server, using a REST client like curl or Postman, make a
> call to the business taxonomy API. E.g.
> http://localhost:21000/api/atlas/v1/taxonomies
> * This will return an empty result set
> * Run quick_start.py.
> This fails with an exception as follows:
> {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:321)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:316)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)\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
>
[jira] [Commented] (ATLAS-805) Quickstart is failing if run after queries to the business taxonomy API
[
https://issues.apache.org/jira/browse/ATLAS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289321#comment-15289321
]
John Speidel commented on ATLAS-805:
[~Hemanth] Adding @GraphTransaction to BaseQuery.execute() doesn't result in
the transaction interceptor being invoked because the catalog directory isn't
included in the repository metadata model where the interceptor is registered.
Explicitly calling commit in base query appears to fix this issue.
I need to do some more testing and want to look over a few more things before
providing a patch.
> Quickstart is failing if run after queries to the business taxonomy API
> ---
>
> Key: ATLAS-805
> URL: https://issues.apache.org/jira/browse/ATLAS-805
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: application.log
>
>
> * On a fresh Atlas server, using a REST client like curl or Postman, make a
> call to the business taxonomy API. E.g.
> http://localhost:21000/api/atlas/v1/taxonomies
> * This will return an empty result set
> * Run quick_start.py.
> This fails with an exception as follows:
> {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:321)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:316)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)\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
>
[jira] [Commented] (ATLAS-805) Quickstart is failing if run after queries to the business taxonomy API
[
https://issues.apache.org/jira/browse/ATLAS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289274#comment-15289274
]
John Speidel commented on ATLAS-805:
Typically in transactional systems, wrapping non-mutating queries in a
transaction isn't required.
But, after looking into this issue I discovered that Titan actually does
mutations to the graph behind the scenes during non-mutating queries. So, even
simple read operations need to be committed. As mentioned by Hemanth, the
catalog queries weren't being committed, which resulted in the implicit thread
scoped transaction started by the catalog query remaining active on the thread
after the catalog request completed.
Looking into implementing a solution now.
> Quickstart is failing if run after queries to the business taxonomy API
> ---
>
> Key: ATLAS-805
> URL: https://issues.apache.org/jira/browse/ATLAS-805
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> * On a fresh Atlas server, using a REST client like curl or Postman, make a
> call to the business taxonomy API. E.g.
> http://localhost:21000/api/atlas/v1/taxonomies
> * This will return an empty result set
> * Run quick_start.py.
> This fails with an exception as follows:
> {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:321)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:316)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)\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
>
>
[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-491: --- Attachment: ATLAS-491.patch > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch, > ATLAS-491.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287815#comment-15287815 ] John Speidel commented on ATLAS-491: I am going to try to attach the latest patch to this Jira. If you don't see it, then the upload failed again. Attempting to upload the previous patch failed and it appears that it caused your network to be blacklisted. > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287810#comment-15287810 ] John Speidel commented on ATLAS-491: Regarding the question about Taxonomy results being returned with entity queries. To be clear, this observation is with DSL queries and not "v1/entities" queries which won't return taxonomy results. The reason for this is that taxonomies are implemented as entities under the covers. Terms are modeled as traits under the covers. To provide a 'singleton' term instance, each term(trait) is associated with its owning taxonomy. > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283406#comment-15283406 ] John Speidel commented on ATLAS-491: I have been unable to upload the patch to the jira but the latest patch is available at review board. > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-491: --- Attachment: test.txt > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch, test.txt > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-491: --- Attachment: ATLAS-491.patch > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch, > ATLAS-491.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-491: --- Attachment: (was: business-catalog-WIP.patch) > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: > 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy
[ https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-491: --- Attachment: business-catalog-WIP.patch Attached a WIP patch of the business catalog functionality. This code is still a work in progress and needs cleanup/refactoring and hardening and is therefore not ready to be considered for merging. Taxonomy and Term resources currently can't be updated or deleted. Unit tests are not yet included. > Business Catalog / Taxonomy > --- > > Key: ATLAS-491 > URL: https://issues.apache.org/jira/browse/ATLAS-491 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.7-incubating >Reporter: Erik Bergenholtz >Assignee: John Speidel > Fix For: 0.7-incubating > > Attachments: business-catalog-WIP.patch > > > s a Atlas UX user, I need to: > Browse business taxonomy hieracharlically through tree > Search by Tags > Search by combination of keyword, tag, free text in search field > All search from view context of taxonomy. If 3 levels deep, then the search > should be narrow to that scope. > expose search ordering capabilities available through SOLR. > As a Data Steward, I need to: > Manage the taxonomy of objects including > Objects Management: > Creating new objects > Modify the object details - annotations, external links, tags, acceptable use > policy, etc > Delete objects (in UI - changing status in backend,and versioning changes) > Relationship management: > creating relationship of objects as a parent or child > assigning tagging to taxonomy > verify tag inheritance > Verify tag impact on tag based policy - ranger API call > Tag Management: > List > Search > Edit > Delete (change state to archive) > All user should be able to comment on any business catalog entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-706) Unable to query for traits which contain a '.' character in their name
John Speidel created ATLAS-706: -- Summary: Unable to query for traits which contain a '.' character in their name Key: ATLAS-706 URL: https://issues.apache.org/jira/browse/ATLAS-706 Project: Atlas Issue Type: Bug Reporter: John Speidel For traits which contain a '.' character in their name, or most other non alpha-numeric characters, DSL queries using the 'isa' operator fail. This is because the atlas query lexer/parser treat these characters as token separators. So for a trait named "foo.bar" if you do a query for "isa foo.bar" this is parsed as "isa foo". This prevents querying of catalog terms which are modeled as traits and contain '.' characters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-20) Rename env variables from METADATA to ATLAS
[ https://issues.apache.org/jira/browse/ATLAS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060370#comment-15060370 ] John Speidel commented on ATLAS-20: --- [~suma.shivaprasad] The changes to environment variable names in the patch will require changes in Ambari since Ambari sets these env vars such as "METADATA_CONF", etc. Without these Ambari changes, Ambari will be unable to start Atlas after the env var name changes. > Rename env variables from METADATA to ATLAS > --- > > Key: ATLAS-20 > URL: https://issues.apache.org/jira/browse/ATLAS-20 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.5-incubating >Reporter: Venkatesh Seetharam >Assignee: Rishabh Bhardwaj > Attachments: ATLAS-20.patch, ATLAS-20.v2.patch, ATLAS-20.v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-306) change javadoc generation from 'package' to 'site' phase
[ https://issues.apache.org/jira/browse/ATLAS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-306: --- Attachment: ATLAS-306-2.patch > change javadoc generation from 'package' to 'site' phase > > > Key: ATLAS-306 > URL: https://issues.apache.org/jira/browse/ATLAS-306 > Project: Atlas > Issue Type: Task >Reporter: John Speidel >Assignee: John Speidel > Attachments: ATLAS-306-2.patch, ATLAS-306.patch > > > Currently the javadoc plugin is executed in the maven 'package' phase. This > causes issues when the project is build as a dependency from another project > which aggregates the javadoc aggregation. Also, generating javadoc in the > 'package' phase negatively affects the build time for developers. > It seems that the current 'standard' is to generate javadocs in the 'site' > phase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-306) change javadoc generation from 'package' to 'site' phase
[ https://issues.apache.org/jira/browse/ATLAS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-306: --- Attachment: ATLAS-306.patch > change javadoc generation from 'package' to 'site' phase > > > Key: ATLAS-306 > URL: https://issues.apache.org/jira/browse/ATLAS-306 > Project: Atlas > Issue Type: Task >Reporter: John Speidel >Assignee: John Speidel > Attachments: ATLAS-306.patch > > > Currently the javadoc plugin is executed in the maven 'package' phase. This > causes issues when the project is build as a dependency from another project > which aggregates the javadoc aggregation. Also, generating javadoc in the > 'package' phase negatively affects the build time for developers. > It seems that the current 'standard' is to generate javadocs in the 'site' > phase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-298) Add unit test for TitanGraphProvider
John Speidel created ATLAS-298: -- Summary: Add unit test for TitanGraphProvider Key: ATLAS-298 URL: https://issues.apache.org/jira/browse/ATLAS-298 Project: Atlas Issue Type: Task Reporter: John Speidel Assignee: John Speidel Priority: Minor Currently there is no unit test for this class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-275: --- Attachment: ATLAS-275.patch > Improve error message when creating a trait and not specifying all required > trait attributes > > > Key: ATLAS-275 > URL: https://issues.apache.org/jira/browse/ATLAS-275 > Project: Atlas > Issue Type: Task >Reporter: John Speidel >Assignee: John Speidel > Attachments: ATLAS-275.patch > > > When an attempt is made to add a trait to an entity where not all of the > trait attributes are provided, the error msg returned to the user is: > "Error deserializing trait instance" > The user than needs to dig through the provided stack trace to see what the > actual problem is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
John Speidel created ATLAS-275: -- Summary: Improve error message when creating a trait and not specifying all required trait attributes Key: ATLAS-275 URL: https://issues.apache.org/jira/browse/ATLAS-275 Project: Atlas Issue Type: Task Reporter: John Speidel Assignee: John Speidel When an attempt is made to add a trait to an entity where not all of the trait attributes are provided, the error msg returned to the user is: "Error deserializing trait instance" The user than need to dig through the provided stack trace to see what the actual problem is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
[
https://issues.apache.org/jira/browse/ATLAS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985901#comment-14985901
]
John Speidel edited comment on ATLAS-275 at 11/2/15 7:55 PM:
-
Attached patch provides better error message when a required trait attribute is
missing:
{code}
error: "Invalid Trait specified. Field 'expiry_date' can't be null:
AttributeInfo{name='expiry_date',
dataType=org.apache.atlas.typesystem.types.DataTypes$DateType@70cfbe37,
multiplicity=Multiplicity{lower=1, upper=1, isUnique=false}, isComposite=false,
isUnique=false, isIndexable=true, reverseAttributeName='null'}"
{code}
was (Author: jspeidel):
Attached patch provides better error message when a required trait attribute is
missing:
error: "Invalid Trait specified. Field 'expiry_date' can't be null:
AttributeInfo{name='expiry_date',
dataType=org.apache.atlas.typesystem.types.DataTypes$DateType@70cfbe37,
multiplicity=Multiplicity{lower=1, upper=1, isUnique=false}, isComposite=false,
isUnique=false, isIndexable=true, reverseAttributeName='null'}"
> Improve error message when creating a trait and not specifying all required
> trait attributes
>
>
> Key: ATLAS-275
> URL: https://issues.apache.org/jira/browse/ATLAS-275
> Project: Atlas
> Issue Type: Task
>Reporter: John Speidel
>Assignee: John Speidel
> Attachments: ATLAS-275.patch
>
>
> When an attempt is made to add a trait to an entity where not all of the
> trait attributes are provided, the error msg returned to the user is:
> "Error deserializing trait instance"
> The user than needs to dig through the provided stack trace to see what the
> actual problem is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-275: --- Description: When an attempt is made to add a trait to an entity where not all of the trait attributes are provided, the error msg returned to the user is: "Error deserializing trait instance" The user than needs to dig through the provided stack trace to see what the actual problem is. was: When an attempt is made to add a trait to an entity where not all of the trait attributes are provided, the error msg returned to the user is: "Error deserializing trait instance" The user than need to dig through the provided stack trace to see what the actual problem is. > Improve error message when creating a trait and not specifying all required > trait attributes > > > Key: ATLAS-275 > URL: https://issues.apache.org/jira/browse/ATLAS-275 > Project: Atlas > Issue Type: Task >Reporter: John Speidel >Assignee: John Speidel > > When an attempt is made to add a trait to an entity where not all of the > trait attributes are provided, the error msg returned to the user is: > "Error deserializing trait instance" > The user than needs to dig through the provided stack trace to see what the > actual problem is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
