[jira] [Updated] (ATLAS-2932) Update DSL to use Java Traversal API
[ https://issues.apache.org/jira/browse/ATLAS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2932: --- Attachment: 0002-ATLAS-2932-Update-DSL-to-use-Tinkerpop-Java-APIs-ins.patch > Update DSL to use Java Traversal API > > > Key: ATLAS-2932 > URL: https://issues.apache.org/jira/browse/ATLAS-2932 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0, trunk >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0 > > Attachments: > 0002-ATLAS-2932-Update-DSL-to-use-Tinkerpop-Java-APIs-ins.patch > > > Change DSL code to use Java Tinkerpop Traversals instead of > GremlinScriptEngine -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script
[ https://issues.apache.org/jira/browse/ATLAS-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2520: --- Attachment: (was: 0001-DSL-using-graph-traversal.patch) > Use JanusGraph traversal over gremlin script > - > > Key: ATLAS-2520 > URL: https://issues.apache.org/jira/browse/ATLAS-2520 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0 > > Attachments: > 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch, Screen Shot > 2018-06-05 at 6.16.42 PM.png, Screen Shot 2018-06-05 at 6.19.33 PM.png > > > Currently lot of code in Atlas follow a concept of GremlinQueryProvider which > gives TP2 and TP3 queries depending on the graph backend being used. Since > Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to > remove TP2 related queries/abstractions and use the GraphTraversal Java API > provided by JanusGraph. > > PRO: Lot of unused code can be removed, more expressive Graph > querying/traversal. > CONS: Decommissioning TP2 completely is a major engineering effort -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script
[ https://issues.apache.org/jira/browse/ATLAS-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2520: --- Attachment: 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch > Use JanusGraph traversal over gremlin script > - > > Key: ATLAS-2520 > URL: https://issues.apache.org/jira/browse/ATLAS-2520 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0 > > Attachments: > 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch, Screen Shot > 2018-06-05 at 6.16.42 PM.png, Screen Shot 2018-06-05 at 6.19.33 PM.png > > > Currently lot of code in Atlas follow a concept of GremlinQueryProvider which > gives TP2 and TP3 queries depending on the graph backend being used. Since > Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to > remove TP2 related queries/abstractions and use the GraphTraversal Java API > provided by JanusGraph. > > PRO: Lot of unused code can be removed, more expressive Graph > querying/traversal. > CONS: Decommissioning TP2 completely is a major engineering effort -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2932) Update DSL to use Java Traversal API
Apoorv Naik created ATLAS-2932: -- Summary: Update DSL to use Java Traversal API Key: ATLAS-2932 URL: https://issues.apache.org/jira/browse/ATLAS-2932 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0, trunk Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.1.0 Change DSL code to use Java Tinkerpop Traversals instead of GremlinScriptEngine -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2929) Fix netty issues when running with embedded Cassandra
[ https://issues.apache.org/jira/browse/ATLAS-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2929. Resolution: Fixed > Fix netty issues when running with embedded Cassandra > - > > Key: ATLAS-2929 > URL: https://issues.apache.org/jira/browse/ATLAS-2929 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > This is resolved by pull request # 13 on Github -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2929) Fix netty issues when running with embedded Cassandra
[ https://issues.apache.org/jira/browse/ATLAS-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658319#comment-16658319 ] Apoorv Naik commented on ATLAS-2929: Fixes ATLAS-2919 > Fix netty issues when running with embedded Cassandra > - > > Key: ATLAS-2929 > URL: https://issues.apache.org/jira/browse/ATLAS-2929 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > This is resolved by pull request # 13 on Github -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2929) Fix netty issues when running with embedded Cassandra
Apoorv Naik created ATLAS-2929: -- Summary: Fix netty issues when running with embedded Cassandra Key: ATLAS-2929 URL: https://issues.apache.org/jira/browse/ATLAS-2929 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.1.0, 2.0.0 This is resolved by pull request # 13 on Github -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2924) Use encoded property name in getEncodedProperty() and setEncodedProperty() methods
[ https://issues.apache.org/jira/browse/ATLAS-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652379#comment-16652379 ] Apoorv Naik commented on ATLAS-2924: +1 Changes look good. > Use encoded property name in getEncodedProperty() and setEncodedProperty() > methods > -- > > Key: ATLAS-2924 > URL: https://issues.apache.org/jira/browse/ATLAS-2924 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: trunk, 0.8.3, 1.1.0 > > Attachments: > 0001-ATLAS-2924-Use-encoded-property-name-in-getEncodedPr-branch-0.8.patch, > 0001-ATLAS-2924-Use-encoded-property-name-in-getEncodedPr-master.patch > > > Use encoded property name in all access to getEncodedProperty() and > setEncodedProperty() methods -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1553) Property loading framework
[ https://issues.apache.org/jira/browse/ATLAS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1553. Resolution: Won't Do > Property loading framework > -- > > Key: ATLAS-1553 > URL: https://issues.apache.org/jira/browse/ATLAS-1553 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > I see that atlas has multiple ways of loading properties/configuration, I > think it'd be a better idea to introduce a property/config frameworkthat > produces apache commons configuration object or java properties object for > more streamlined use. I've seen 3 mixes of config > Load directly into property files > Use spring bean placeholder > Read into apache commons configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1954) UTs and ITs
[ https://issues.apache.org/jira/browse/ATLAS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1954. Resolution: Fixed > UTs and ITs > --- > > Key: ATLAS-1954 > URL: https://issues.apache.org/jira/browse/ATLAS-1954 > Project: Atlas > Issue Type: Sub-task >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > Add Unit test for all possible cases, ITs might a simple extension to those -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1956) AtlasSearchResult to include filter attributes by default
[ https://issues.apache.org/jira/browse/ATLAS-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1956. Resolution: Fixed > AtlasSearchResult to include filter attributes by default > - > > Key: ATLAS-1956 > URL: https://issues.apache.org/jira/browse/ATLAS-1956 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: trunk > > > If no attributes are specified in the SearchParameters then by default > AtlasSearchResult should include the attributes present in the filter criteria -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2149) Cleanup V1 typedef listener interfaces
[ https://issues.apache.org/jira/browse/ATLAS-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2149. Resolution: Fixed > Cleanup V1 typedef listener interfaces > -- > > Key: ATLAS-2149 > URL: https://issues.apache.org/jira/browse/ATLAS-2149 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8-incubating, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0, 0.8.1, 0.8-incubating > > > Currently GraphBackedSearchIndexer implements typedef change listener for V1 > and V2 structures, this change removes the V1 dependency to avoid any > conflict/race during the index creation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2210) Add relationship methods to AtlasClientV2
[ https://issues.apache.org/jira/browse/ATLAS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2210. Resolution: Won't Do > Add relationship methods to AtlasClientV2 > - > > Key: ATLAS-2210 > URL: https://issues.apache.org/jira/browse/ATLAS-2210 > Project: Atlas > Issue Type: Improvement >Reporter: Andrew Hulbert >Assignee: Apoorv Naik >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2218) Test stability across branches
[ https://issues.apache.org/jira/browse/ATLAS-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2218. Resolution: Fixed > Test stability across branches > -- > > Key: ATLAS-2218 > URL: https://issues.apache.org/jira/browse/ATLAS-2218 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > The tests are pretty inconsistent in runs across master and branch-0.8. This > has been preventing a clean build in apache jenkins for a while now. This > JIRA is aimed at ensuring build success across master and latest release > branch. > Goals: > 1. Make IT runs consistent > 2. Make UTs run successfully on both > 3. Separate UTs and ITs in webapp module > 4. Fix UTs in distro module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2335) [DSL] Query with multiple aggregator of same type fails
[ https://issues.apache.org/jira/browse/ATLAS-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16645546#comment-16645546 ] Apoorv Naik commented on ATLAS-2335: Janusgraph java traversal fixes this issue. > [DSL] Query with multiple aggregator of same type fails > --- > > Key: ATLAS-2335 > URL: https://issues.apache.org/jira/browse/ATLAS-2335 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > eg DB select min(name), min(owner) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2225) Split properties per module and concatenate in distro
[ https://issues.apache.org/jira/browse/ATLAS-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2225. Resolution: Later > Split properties per module and concatenate in distro > - > > Key: ATLAS-2225 > URL: https://issues.apache.org/jira/browse/ATLAS-2225 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2479) [Docs] Update Atlas user docs and REST API specs
[ https://issues.apache.org/jira/browse/ATLAS-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2479. Resolution: Fixed > [Docs] Update Atlas user docs and REST API specs > - > > Key: ATLAS-2479 > URL: https://issues.apache.org/jira/browse/ATLAS-2479 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1746) Test refactor and cleanup
[ https://issues.apache.org/jira/browse/ATLAS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1746. Resolution: Later > Test refactor and cleanup > - > > Key: ATLAS-1746 > URL: https://issues.apache.org/jira/browse/ATLAS-1746 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > Currently the tests have different coding patterns, someplace we rely on DI > for getting Objects other places we manually create instances of classes (or > dependencies) under test. > Ideally it should only be done either by DI or hand construct all the time > rather than relying on DI. The former seems to be a cleaner approach as we > get to validate the DI behavior as well. > The patch will remove all manual instantiations and replace them with > Injectable components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1683) Add bean validation to request bodies
[ https://issues.apache.org/jira/browse/ATLAS-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1683. Resolution: Later > Add bean validation to request bodies > - > > Key: ATLAS-1683 > URL: https://issues.apache.org/jira/browse/ATLAS-1683 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > Add java bean validation to all resources consuming request bodies, better to > handle data validation even before reaching the graph store. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2848) Fix property name in ApplicationProperties class
[
https://issues.apache.org/jira/browse/ATLAS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-2848.
Resolution: Fixed
> Fix property name in ApplicationProperties class
>
>
> Key: ATLAS-2848
> URL: https://issues.apache.org/jira/browse/ATLAS-2848
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
>
> {color:#00} atlas.graph.cache.tx-cache.size is wrong, change to
> atlas.graph.cache.tx-cache-size{color}
> {color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2848) Fix property name in ApplicationProperties class
[
https://issues.apache.org/jira/browse/ATLAS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2848:
---
Fix Version/s: (was: 0.8.3)
> Fix property name in ApplicationProperties class
>
>
> Key: ATLAS-2848
> URL: https://issues.apache.org/jira/browse/ATLAS-2848
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
>
> {color:#00} atlas.graph.cache.tx-cache.size is wrong, change to
> atlas.graph.cache.tx-cache-size{color}
> {color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2848) Fix property name in ApplicationProperties class
[
https://issues.apache.org/jira/browse/ATLAS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2848:
---
Affects Version/s: (was: 0.8.2)
(was: 0.8.1)
> Fix property name in ApplicationProperties class
>
>
> Key: ATLAS-2848
> URL: https://issues.apache.org/jira/browse/ATLAS-2848
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
>
> {color:#00} atlas.graph.cache.tx-cache.size is wrong, change to
> atlas.graph.cache.tx-cache-size{color}
> {color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2848) Fix property name in ApplicationProperties class
Apoorv Naik created ATLAS-2848:
--
Summary: Fix property name in ApplicationProperties class
Key: ATLAS-2848
URL: https://issues.apache.org/jira/browse/ATLAS-2848
Project: Atlas
Issue Type: Bug
Affects Versions: 1.0.0, 0.8.2, 0.8.1
Reporter: Apoorv Naik
Assignee: Apoorv Naik
Fix For: 0.8.3, 1.1.0
{color:#00} atlas.graph.cache.tx-cache.size is wrong, change to
atlas.graph.cache.tx-cache-size{color}
{color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2834) In HA environment, authorizer initialization is done only on first access.
[ https://issues.apache.org/jira/browse/ATLAS-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2834: --- Attachment: 0001-ATLAS-2834-Init-authorizer-when-Atlas-is-in-HA-mode.patch > In HA environment, authorizer initialization is done only on first access. > -- > > Key: ATLAS-2834 > URL: https://issues.apache.org/jira/browse/ATLAS-2834 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Anuja Leekha >Priority: Major > Labels: atlas > Fix For: 1.1.0 > > Attachments: > 0001-ATLAS-2834-Init-authorizer-when-Atlas-is-in-HA-mode.patch > > > In HA environment, Atlas doesn't make a call to Ranger to download Atlas > policies unless it is accessed for the first time. > This is not an HA specific feature and the behavior should be consistent with > non HA feature - of downloading Atlas policies from Ranger when Atlas is > restarted after enabling Ranger plugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2834) In HA environment, authorizer initialization is done only on first access.
[ https://issues.apache.org/jira/browse/ATLAS-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik reassigned ATLAS-2834: -- Assignee: Apoorv Naik > In HA environment, authorizer initialization is done only on first access. > -- > > Key: ATLAS-2834 > URL: https://issues.apache.org/jira/browse/ATLAS-2834 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Anuja Leekha >Assignee: Apoorv Naik >Priority: Major > Labels: atlas > Fix For: 1.1.0 > > Attachments: > 0001-ATLAS-2834-Init-authorizer-when-Atlas-is-in-HA-mode.patch > > > In HA environment, Atlas doesn't make a call to Ranger to download Atlas > policies unless it is accessed for the first time. > This is not an HA specific feature and the behavior should be consistent with > non HA feature - of downloading Atlas policies from Ranger when Atlas is > restarted after enabling Ranger plugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long
[ https://issues.apache.org/jira/browse/ATLAS-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2827: --- Attachment: (was: 0001-Indexed-string-compaction-patch.patch) > Unable to persist vertex when indexed string attribute is really long > - > > Key: ATLAS-2827 > URL: https://issues.apache.org/jira/browse/ATLAS-2827 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8.1, 0.8.2, 1.0.0, trunk >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.3, 1.1.0 > > > Titan/Janus creates an inverted index key which exceeds the row length > restriction imposed by HBase hence the vertex fails to persist with backend > exception. > > Solution: > In the entity graph mapping, before persisting the vertex we need to trim > down the value (although it'll cause data loss) to avoid Atlas becoming non > functional for such edge cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long
[ https://issues.apache.org/jira/browse/ATLAS-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2827: --- Affects Version/s: trunk 0.8.1 0.8.2 1.0.0 > Unable to persist vertex when indexed string attribute is really long > - > > Key: ATLAS-2827 > URL: https://issues.apache.org/jira/browse/ATLAS-2827 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8.1, 0.8.2, 1.0.0, trunk >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > Titan/Janus creates an inverted index key which exceeds the row length > restriction imposed by HBase hence the vertex fails to persist with backend > exception. > > Solution: > In the entity graph mapping, before persisting the vertex we need to trim > down the value (although it'll cause data loss) to avoid Atlas becoming non > functional for such edge cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long
Apoorv Naik created ATLAS-2827: -- Summary: Unable to persist vertex when indexed string attribute is really long Key: ATLAS-2827 URL: https://issues.apache.org/jira/browse/ATLAS-2827 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Titan/Janus creates an inverted index key which exceeds the row length restriction imposed by HBase hence the vertex fails to persist with backend exception. Solution: In the entity graph mapping, before persisting the vertex we need to trim down the value (although it'll cause data loss) to avoid Atlas becoming non functional for such edge cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2817) Update to JanusGraph 0.3.x
[ https://issues.apache.org/jira/browse/ATLAS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2817. Resolution: Fixed > Update to JanusGraph 0.3.x > -- > > Key: ATLAS-2817 > URL: https://issues.apache.org/jira/browse/ATLAS-2817 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: 0001-Janusgraph-update-to-0.3.0.patch > > > There are couple of index related improvements in this version which helps > resolve the slowness in few of our DSL queries. This upgrade would speed up > DSL execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2817) Update to JanusGraph 0.3.x
[ https://issues.apache.org/jira/browse/ATLAS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579209#comment-16579209 ] Apoorv Naik commented on ATLAS-2817: Committed to master : https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=4ddceacb0dc4add848a97a445a3091624aaaff7e > Update to JanusGraph 0.3.x > -- > > Key: ATLAS-2817 > URL: https://issues.apache.org/jira/browse/ATLAS-2817 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: 0001-Janusgraph-update-to-0.3.0.patch > > > There are couple of index related improvements in this version which helps > resolve the slowness in few of our DSL queries. This upgrade would speed up > DSL execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2817) Update to JanusGraph 0.3.x
[ https://issues.apache.org/jira/browse/ATLAS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2817: --- Attachment: 0001-Janusgraph-update-to-0.3.0.patch > Update to JanusGraph 0.3.x > -- > > Key: ATLAS-2817 > URL: https://issues.apache.org/jira/browse/ATLAS-2817 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: 0001-Janusgraph-update-to-0.3.0.patch > > > There are couple of index related improvements in this version which helps > resolve the slowness in few of our DSL queries. This upgrade would speed up > DSL execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2812) Upgrade commons-fileupload to 1.3.3
[ https://issues.apache.org/jira/browse/ATLAS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576860#comment-16576860 ] Apoorv Naik commented on ATLAS-2812: Looks good for commit. Thanks Sarath. > Upgrade commons-fileupload to 1.3.3 > --- > > Key: ATLAS-2812 > URL: https://issues.apache.org/jira/browse/ATLAS-2812 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating, 0.8.1, 0.8.2 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0, 0.8.3, 1.1.0 > > Attachments: 0001-ATLAS-2812-Upgrade-commons-fileupload-to-1.3.3.patch > > > Atlas packages commons-fileupload-1.2.1.jar which has a potential security > vulnerability > Need to upgrade to 1.3.1+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
[
https://issues.apache.org/jira/browse/ATLAS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575740#comment-16575740
]
Apoorv Naik edited comment on ATLAS-2816 at 8/10/18 4:12 AM:
-
One suggestion, use the followReferences flag instead of hardcoding the
ignoreRelationship param. This would make is easier to toggle if certain
deployment scenario wants to use the relationship details to be captured in the
entityText. Also follow this guideline for patch creation,
# Work on a local branch
# Commit the patch on local branch
# Generate patch using "git format-patch origin/master" (this way you get
credit by including author info in the patch)
# Attach the patch to JIRA
HTH
was (Author: apoorvnaik):
One suggestion, use the followReferences flag instead of hardcoding the
ignoreRelationship param. This would make is easier to toggle if certain
deployment scenario wants to use the relationship details to be captured in the
entityText.
HTH
> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
>
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Assignee: Apoorv Naik
>Priority: Major
> Attachments: ATLAS-2816.01.patch
>
>
> We encountered a problem when using Hive bridge in production. One database
> has 5000+ tables. Importing the first table costs only tens of milliseconds,
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds
> to import one table.
> After investigation, we realized that it is not necessary for the
> {{FullTextMapperV2}} to retrieve all the relationship of the database each
> time a table is imported. The time complexity of importing a whole database
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}:
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will
> not use relationship attributes of the entity, this can save plenty of time
> when importing entities with a large number of relations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
[
https://issues.apache.org/jira/browse/ATLAS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575740#comment-16575740
]
Apoorv Naik commented on ATLAS-2816:
One suggestion, use the followReferences flag instead of hardcoding the
ignoreRelationship param. This would make is easier to toggle if certain
deployment scenario wants to use the relationship details to be captured in the
entityText.
HTH
> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
>
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Priority: Major
> Attachments: ATLAS-2816.01.patch
>
>
> We encountered a problem when using Hive bridge in production. One database
> has 5000+ tables. Importing the first table costs only tens of milliseconds,
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds
> to import one table.
> After investigation, we realized that it is not necessary for the
> {{FullTextMapperV2}} to retrieve all the relationship of the database each
> time a table is imported. The time complexity of importing a whole database
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}:
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will
> not use relationship attributes of the entity, this can save plenty of time
> when importing entities with a large number of relations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
[
https://issues.apache.org/jira/browse/ATLAS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik reassigned ATLAS-2816:
--
Assignee: Apoorv Naik
> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
>
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Assignee: Apoorv Naik
>Priority: Major
> Attachments: ATLAS-2816.01.patch
>
>
> We encountered a problem when using Hive bridge in production. One database
> has 5000+ tables. Importing the first table costs only tens of milliseconds,
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds
> to import one table.
> After investigation, we realized that it is not necessary for the
> {{FullTextMapperV2}} to retrieve all the relationship of the database each
> time a table is imported. The time complexity of importing a whole database
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}:
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will
> not use relationship attributes of the entity, this can save plenty of time
> when importing entities with a large number of relations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
[
https://issues.apache.org/jira/browse/ATLAS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575327#comment-16575327
]
Apoorv Naik commented on ATLAS-2816:
Please submit a patch or create a review on reviewboard with suggested changes.
> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
>
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Priority: Major
>
> We encountered a problem when using Hive bridge in production. One database
> has 5000+ tables. Importing the first table costs only tens of milliseconds,
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds
> to import one table.
> After investigation, we realized that it is not necessary for the
> {{FullTextMapperV2}} to retrieve all the relationship of the database each
> time a table is imported. The time complexity of importing a whole database
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}:
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will
> not use relationship attributes of the entity, this can save plenty of time
> when importing entities with a large number of relations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2817) Update to JanusGraph 0.3.x
Apoorv Naik created ATLAS-2817: -- Summary: Update to JanusGraph 0.3.x Key: ATLAS-2817 URL: https://issues.apache.org/jira/browse/ATLAS-2817 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik There are couple of index related improvements in this version which helps resolve the slowness in few of our DSL queries. This upgrade would speed up DSL execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef
[
https://issues.apache.org/jira/browse/ATLAS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572207#comment-16572207
]
Apoorv Naik commented on ATLAS-2815:
Awaiting build
([https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/545/)]
result.
> Slow UI load and REST improvement for entities with ownedRef
>
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
> Issue Type: Improvement
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param-
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions,
> then the server will send the attributes accordingly in referredEntities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef
[
https://issues.apache.org/jira/browse/ATLAS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2815:
---
Issue Type: Improvement (was: Bug)
> Slow UI load and REST improvement for entities with ownedRef
>
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
> Issue Type: Improvement
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param-
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions,
> then the server will send the attributes accordingly in referredEntities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef
[
https://issues.apache.org/jira/browse/ATLAS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2815:
---
Summary: Slow UI load and REST improvement for entities with ownedRef
(was: 'Properties' tab performance improvement )
> Slow UI load and REST improvement for entities with ownedRef
>
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
> Issue Type: Bug
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param-
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions,
> then the server will send the attributes accordingly in referredEntities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2815) 'Properties' tab performance improvement
[
https://issues.apache.org/jira/browse/ATLAS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2815:
---
Fix Version/s: 1.1.0
trunk
> 'Properties' tab performance improvement
> -
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
> Issue Type: Bug
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param-
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions,
> then the server will send the attributes accordingly in referredEntities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-1957) MultiVertex graph query
[
https://issues.apache.org/jira/browse/ATLAS-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-1957.
Resolution: Won't Do
> MultiVertex graph query
> ---
>
> Key: ATLAS-1957
> URL: https://issues.apache.org/jira/browse/ATLAS-1957
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: trunk
>
>
> There are lot of use cases where the graph query needs to be executed against
> a given set of vertices, right now the only way to do it to first determine a
> unique indexed attribute for those and then use that as the very first has
> condition filter.
> e.g. graph.query().has("__guid", IN, Set guids)
> This makes it difficult to perform hops in the graph traversal using the
> query API alone.
> Titan0 and Titan1 has the ability to perform queries on multiple vertices in
> one go, which would benefit us in the future.
> This enhancement will track the implementation of the MultiVertexQuery
> feature across Titan0 and Titan1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-1958) Better graph traversal APIs
[ https://issues.apache.org/jira/browse/ATLAS-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-1958. Resolution: Won't Do > Better graph traversal APIs > > > Key: ATLAS-1958 > URL: https://issues.apache.org/jira/browse/ATLAS-1958 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > Right now the only way to perform deep/complex graph traversals is through > the Gremlin API. > Currently atlas has an ExpressionFactory abstraction which internally > generates groovy expression as per the compatible TinkerPop version. It > requires solid understanding of the TypeSystem, gremlin query structure, > required optimizations etc. > Instead, TinkerPop itself supports a Gremlin pipeline (TP2) and a > GraphTraversal (TP3), which are good abstractions over the gremlin query > language. We should have a Querying abstraction in Atlas which is agnostic to > the underlying Graph implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue
[ https://issues.apache.org/jira/browse/ATLAS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2786: --- Fix Version/s: 1.1.0 0.8.3 trunk > [Atlas HA] Zookeeper connection issue > - > > Key: ATLAS-2786 > URL: https://issues.apache.org/jira/browse/ATLAS-2786 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1, 0.8.2, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Critical > Fix For: trunk, 0.8.3, 1.1.0 > > Attachments: > 0001-ATLAS-2786-Honor-ZK-server-ensemble-provided-in-conf.patch > > > The curator client right now only connects to the very first zookeeper server > regardless of the number of zookeeper servers provided in the configuration. > > Due to this behavior if the ZK (that Atlas connected to during startup) goes > down then Atlas fails to serve further request while constantly trying to > reconnect to the dead ZK server. > > This patch makes the change in configuration parsing to allow fallback to > different ZK servers in case the primary goes down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2786) [Atlas HA] Zookeeper connection issue
Apoorv Naik created ATLAS-2786: -- Summary: [Atlas HA] Zookeeper connection issue Key: ATLAS-2786 URL: https://issues.apache.org/jira/browse/ATLAS-2786 Project: Atlas Issue Type: Improvement Affects Versions: 1.0.0, 0.8.2, 0.8.1 Reporter: Apoorv Naik Assignee: Apoorv Naik The curator client right now only connects to the very first zookeeper server regardless of the number of zookeeper servers provided in the configuration. Due to this behavior if the ZK (that Atlas connected to during startup) goes down then Atlas fails to serve further request while constantly trying to reconnect to the dead ZK server. This patch makes the change in configuration parsing to allow fallback to different ZK servers in case the primary goes down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue
[ https://issues.apache.org/jira/browse/ATLAS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2786: --- Issue Type: Bug (was: Improvement) > [Atlas HA] Zookeeper connection issue > - > > Key: ATLAS-2786 > URL: https://issues.apache.org/jira/browse/ATLAS-2786 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1, 0.8.2, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Critical > > The curator client right now only connects to the very first zookeeper server > regardless of the number of zookeeper servers provided in the configuration. > > Due to this behavior if the ZK (that Atlas connected to during startup) goes > down then Atlas fails to serve further request while constantly trying to > reconnect to the dead ZK server. > > This patch makes the change in configuration parsing to allow fallback to > different ZK servers in case the primary goes down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2780) Update AtlasAdminClient to accept username/password via cmdline
[ https://issues.apache.org/jira/browse/ATLAS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2780. Resolution: Fixed Fix Version/s: 2.0.0 1.1.0 > Update AtlasAdminClient to accept username/password via cmdline > --- > > Key: ATLAS-2780 > URL: https://issues.apache.org/jira/browse/ATLAS-2780 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Currently the code doesn't accept the username, password via cmdline options. > > This change will allow a user to specify the combo using -u : -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2780) Update AtlasAdminClient to accept username/password via cmdline
Apoorv Naik created ATLAS-2780: -- Summary: Update AtlasAdminClient to accept username/password via cmdline Key: ATLAS-2780 URL: https://issues.apache.org/jira/browse/ATLAS-2780 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Currently the code doesn't accept the username, password via cmdline options. This change will allow a user to specify the combo using -u : -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege
[ https://issues.apache.org/jira/browse/ATLAS-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2746: --- Fix Version/s: 1.0.0 trunk > [Glossary] Simple Term/Category creation should work with CREATE privilege > -- > > Key: ATLAS-2746 > URL: https://issues.apache.org/jira/browse/ATLAS-2746 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0, trunk > > > Currently this operation needs following privileges > > Entity.READ, Entity.CREATE, Entity.UPDATE > > with the change simple term/category creation without any other relations > e.g. children, parent, categorized terms etc. can work with > > Entity.READ and Entity.CREATE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege
Apoorv Naik created ATLAS-2746: -- Summary: [Glossary] Simple Term/Category creation should work with CREATE privilege Key: ATLAS-2746 URL: https://issues.apache.org/jira/browse/ATLAS-2746 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Currently this operation needs following privileges Entity.READ, Entity.CREATE, Entity.UPDATE with the change simple term/category creation without any other relations e.g. children, parent, categorized terms etc. can work with Entity.READ and Entity.CREATE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege
[ https://issues.apache.org/jira/browse/ATLAS-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2746: --- Affects Version/s: 1.0.0 > [Glossary] Simple Term/Category creation should work with CREATE privilege > -- > > Key: ATLAS-2746 > URL: https://issues.apache.org/jira/browse/ATLAS-2746 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0, trunk > > > Currently this operation needs following privileges > > Entity.READ, Entity.CREATE, Entity.UPDATE > > with the change simple term/category creation without any other relations > e.g. children, parent, categorized terms etc. can work with > > Entity.READ and Entity.CREATE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2520) Use JanusGraph traversal over gremlin script
[ https://issues.apache.org/jira/browse/ATLAS-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502750#comment-16502750 ] Apoorv Naik commented on ATLAS-2520: Initial code changes show tremendous improvement in DSL execution. For the DSLQueriesTest suite the (best case) numbers TP2: 90s TP3: 25s > Use JanusGraph traversal over gremlin script > - > > Key: ATLAS-2520 > URL: https://issues.apache.org/jira/browse/ATLAS-2520 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: Screen Shot 2018-06-05 at 6.16.42 PM.png, Screen Shot > 2018-06-05 at 6.19.33 PM.png > > > Currently lot of code in Atlas follow a concept of GremlinQueryProvider which > gives TP2 and TP3 queries depending on the graph backend being used. Since > Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to > remove TP2 related queries/abstractions and use the GraphTraversal Java API > provided by JanusGraph. > > PRO: Lot of unused code can be removed, more expressive Graph > querying/traversal. > CONS: Decommissioning TP2 completely is a major engineering effort -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script
[ https://issues.apache.org/jira/browse/ATLAS-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2520: --- Attachment: Screen Shot 2018-06-05 at 6.16.42 PM.png > Use JanusGraph traversal over gremlin script > - > > Key: ATLAS-2520 > URL: https://issues.apache.org/jira/browse/ATLAS-2520 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: Screen Shot 2018-06-05 at 6.16.42 PM.png, Screen Shot > 2018-06-05 at 6.19.33 PM.png > > > Currently lot of code in Atlas follow a concept of GremlinQueryProvider which > gives TP2 and TP3 queries depending on the graph backend being used. Since > Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to > remove TP2 related queries/abstractions and use the GraphTraversal Java API > provided by JanusGraph. > > PRO: Lot of unused code can be removed, more expressive Graph > querying/traversal. > CONS: Decommissioning TP2 completely is a major engineering effort -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script
[ https://issues.apache.org/jira/browse/ATLAS-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2520: --- Attachment: Screen Shot 2018-06-05 at 6.19.33 PM.png > Use JanusGraph traversal over gremlin script > - > > Key: ATLAS-2520 > URL: https://issues.apache.org/jira/browse/ATLAS-2520 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: Screen Shot 2018-06-05 at 6.16.42 PM.png, Screen Shot > 2018-06-05 at 6.19.33 PM.png > > > Currently lot of code in Atlas follow a concept of GremlinQueryProvider which > gives TP2 and TP3 queries depending on the graph backend being used. Since > Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to > remove TP2 related queries/abstractions and use the GraphTraversal Java API > provided by JanusGraph. > > PRO: Lot of unused code can be removed, more expressive Graph > querying/traversal. > CONS: Decommissioning TP2 completely is a major engineering effort -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2739) Update version in branch-1.0 to 1.1.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/ATLAS-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501086#comment-16501086 ] Apoorv Naik commented on ATLAS-2739: +1 for the patch. Thanks [~madhan.neethiraj] > Update version in branch-1.0 to 1.1.0-SNAPSHOT > -- > > Key: ATLAS-2739 > URL: https://issues.apache.org/jira/browse/ATLAS-2739 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.1.0 > > Attachments: ATLAS-2739.patch > > > Now that Apache Atlas 1.0.0 has been released, update branch-1.0 to use > version 1.1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2721) [Glossary] Rename displayName to name
[ https://issues.apache.org/jira/browse/ATLAS-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2721: --- Fix Version/s: 1.0.0 > [Glossary] Rename displayName to name > - > > Key: ATLAS-2721 > URL: https://issues.apache.org/jira/browse/ATLAS-2721 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > A new attr displayText will be introduced later for UI use. This patch > renames the displayName attr to name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2721) [Glossary] Rename displayName to name
Apoorv Naik created ATLAS-2721: -- Summary: [Glossary] Rename displayName to name Key: ATLAS-2721 URL: https://issues.apache.org/jira/browse/ATLAS-2721 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik A new attr displayText will be introduced later for UI use. This patch renames the displayName attr to name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2720) [Docs] What's new in Atlas 1.0
Apoorv Naik created ATLAS-2720: -- Summary: [Docs] What's new in Atlas 1.0 Key: ATLAS-2720 URL: https://issues.apache.org/jira/browse/ATLAS-2720 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2444) HDFS NameNode Federation support
[ https://issues.apache.org/jira/browse/ATLAS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488313#comment-16488313 ] Apoorv Naik edited comment on ATLAS-2444 at 5/24/18 2:17 AM: - Committed updates to following branch * master: http://git-wip-us.apache.org/repos/asf/atlas/commit/bcd5bb60732833f000e8e50f1f16b2cf3dbc32c * branch-1.0: was (Author: apoorvnaik): Committed updates to following branch * master: [http://git-wip-us.apache.org/repos/asf/atlas/commit/|http://git-wip-us.apache.org/repos/asf/atlas/commit/3ec37cae]bcd5bb60732833f000e8e50f1f16b2cf3dbc32c * branch-1.0: > HDFS NameNode Federation support > > > Key: ATLAS-2444 > URL: https://issues.apache.org/jira/browse/ATLAS-2444 > Project: Atlas > Issue Type: Bug >Reporter: Srikanth Venkat >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > With Hadoop 3, HDFS supports multiple namespaces; each namespace is serviced > by a cluster of name-nodes identified by a nameServiceId. HDFS path entity in > Atlas should be updated to capture the the nameServiceId of the namenode > cluster for the path. Also, references to individual namenode in the path > should be replaced with corresponding nameServiceID. > Changes: > # HDFS model to include a new attribute called nameServiceId, default will > be empty > # hdfs path's qualified name will include the cluster info as well > # All Hooks dealing with HDFS path will resolve the host:port to the > respective nameServiceId -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2444) HDFS NameNode Federation support
[ https://issues.apache.org/jira/browse/ATLAS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488313#comment-16488313 ] Apoorv Naik commented on ATLAS-2444: Committed updates to following branch * master: [http://git-wip-us.apache.org/repos/asf/atlas/commit/|http://git-wip-us.apache.org/repos/asf/atlas/commit/3ec37cae]bcd5bb60732833f000e8e50f1f16b2cf3dbc32c * branch-1.0: > HDFS NameNode Federation support > > > Key: ATLAS-2444 > URL: https://issues.apache.org/jira/browse/ATLAS-2444 > Project: Atlas > Issue Type: Bug >Reporter: Srikanth Venkat >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > With Hadoop 3, HDFS supports multiple namespaces; each namespace is serviced > by a cluster of name-nodes identified by a nameServiceId. HDFS path entity in > Atlas should be updated to capture the the nameServiceId of the namenode > cluster for the path. Also, references to individual namenode in the path > should be replaced with corresponding nameServiceID. > Changes: > # HDFS model to include a new attribute called nameServiceId, default will > be empty > # hdfs path's qualified name will include the cluster info as well > # All Hooks dealing with HDFS path will resolve the host:port to the > respective nameServiceId -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-2444) HDFS NameNode Federation support
[ https://issues.apache.org/jira/browse/ATLAS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik reopened ATLAS-2444: Updates needed in the code as per hadoop committer's review, HDFS-13502. > HDFS NameNode Federation support > > > Key: ATLAS-2444 > URL: https://issues.apache.org/jira/browse/ATLAS-2444 > Project: Atlas > Issue Type: Bug >Reporter: Srikanth Venkat >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > With Hadoop 3, HDFS supports multiple namespaces; each namespace is serviced > by a cluster of name-nodes identified by a nameServiceId. HDFS path entity in > Atlas should be updated to capture the the nameServiceId of the namenode > cluster for the path. Also, references to individual namenode in the path > should be replaced with corresponding nameServiceID. > Changes: > # HDFS model to include a new attribute called nameServiceId, default will > be empty > # hdfs path's qualified name will include the cluster info as well > # All Hooks dealing with HDFS path will resolve the host:port to the > respective nameServiceId -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2705) [Search] Term search shows deleted entities by default
[ https://issues.apache.org/jira/browse/ATLAS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2705: --- Attachment: (was: 0002-ATLAS-2705-2.patch) > [Search] Term search shows deleted entities by default > -- > > Key: ATLAS-2705 > URL: https://issues.apache.org/jira/browse/ATLAS-2705 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2705-Search-using-term-shouldn-t-show-deleted-.patch > > > Search should only show deleted entities if requested. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2705) [Search] Term search shows deleted entities by default
[ https://issues.apache.org/jira/browse/ATLAS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2705: --- Attachment: 0002-ATLAS-2705-2.patch > [Search] Term search shows deleted entities by default > -- > > Key: ATLAS-2705 > URL: https://issues.apache.org/jira/browse/ATLAS-2705 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2705-Search-using-term-shouldn-t-show-deleted-.patch, > 0002-ATLAS-2705-2.patch > > > Search should only show deleted entities if requested. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site
[ https://issues.apache.org/jira/browse/ATLAS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483395#comment-16483395 ] Apoorv Naik commented on ATLAS-2698: Committed to following branches: * master: [https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=d218fb4f2fe1551f8f9eb5fba69e38e0d25b10dc] * branch-1.0: [https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=a95fcdb55ef04d7528f2e355358ec41c31eb3782] > [Glossary] Add docs related to Glossary for Apache site > --- > > Key: ATLAS-2698 > URL: https://issues.apache.org/jira/browse/ATLAS-2698 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch > > > Updating the docs module to include documentation around Glossary -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2705) [Search] Term search shows deleted entities by default
Apoorv Naik created ATLAS-2705: -- Summary: [Search] Term search shows deleted entities by default Key: ATLAS-2705 URL: https://issues.apache.org/jira/browse/ATLAS-2705 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik Search should only show deleted entities if requested. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2705) [Search] Term search shows deleted entities by default
[ https://issues.apache.org/jira/browse/ATLAS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2705: --- Fix Version/s: 1.0.0 > [Search] Term search shows deleted entities by default > -- > > Key: ATLAS-2705 > URL: https://issues.apache.org/jira/browse/ATLAS-2705 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > Search should only show deleted entities if requested. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2703) [Glossary] Term relation edge shouldn't be deleted when entity is deleted
Apoorv Naik created ATLAS-2703: -- Summary: [Glossary] Term relation edge shouldn't be deleted when entity is deleted Key: ATLAS-2703 URL: https://issues.apache.org/jira/browse/ATLAS-2703 Project: Atlas Issue Type: Bug Reporter: Apoorv Naik Assignee: Apoorv Naik With a recent hard delete change all internal relationship edges were deleted, when an entity is deleted the desired behavior is to mark the relation as DELETED (soft delete). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2702) [Glossary] Term's qualifiedName not persisted after anchor change
[ https://issues.apache.org/jira/browse/ATLAS-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480903#comment-16480903 ] Apoorv Naik commented on ATLAS-2702: Committed on master: https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=9044e0375cea58641b0f54c1732980f1401fd845 > [Glossary] Term's qualifiedName not persisted after anchor change > - > > Key: ATLAS-2702 > URL: https://issues.apache.org/jira/browse/ATLAS-2702 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0-alpha, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2702) [Glossary] Term's qualifiedName not persisted after anchor change
[ https://issues.apache.org/jira/browse/ATLAS-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2702. Resolution: Fixed > [Glossary] Term's qualifiedName not persisted after anchor change > - > > Key: ATLAS-2702 > URL: https://issues.apache.org/jira/browse/ATLAS-2702 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0-alpha, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2701) [Glossary] Usage attribute not getting persisted for Term
[ https://issues.apache.org/jira/browse/ATLAS-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2701. Resolution: Fixed Committed on master: https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=9044e0375cea58641b0f54c1732980f1401fd845 > [Glossary] Usage attribute not getting persisted for Term > - > > Key: ATLAS-2701 > URL: https://issues.apache.org/jira/browse/ATLAS-2701 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0-alpha, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2701) [Glossary] Usage attribute not getting persisted for Term
Apoorv Naik created ATLAS-2701: -- Summary: [Glossary] Usage attribute not getting persisted for Term Key: ATLAS-2701 URL: https://issues.apache.org/jira/browse/ATLAS-2701 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0-alpha, 1.0.0 Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2702) [Glossary] Term's qualifiedName not persisted after anchor change
Apoorv Naik created ATLAS-2702: -- Summary: [Glossary] Term's qualifiedName not persisted after anchor change Key: ATLAS-2702 URL: https://issues.apache.org/jira/browse/ATLAS-2702 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0-alpha, 1.0.0 Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2700) [Glossary] Error code fixes
Apoorv Naik created ATLAS-2700: -- Summary: [Glossary] Error code fixes Key: ATLAS-2700 URL: https://issues.apache.org/jira/browse/ATLAS-2700 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0-alpha, 1.0.0 Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 Fix error code messages for certain cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site
[ https://issues.apache.org/jira/browse/ATLAS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2698: --- Attachment: (was: 0001-ATLAS-2698-Glossary-related-documentation.patch) > [Glossary] Add docs related to Glossary for Apache site > --- > > Key: ATLAS-2698 > URL: https://issues.apache.org/jira/browse/ATLAS-2698 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch > > > Updating the docs module to include documentation around Glossary -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site
[ https://issues.apache.org/jira/browse/ATLAS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2698: --- Attachment: 0001-ATLAS-2698-Glossary-related-documentation.patch > [Glossary] Add docs related to Glossary for Apache site > --- > > Key: ATLAS-2698 > URL: https://issues.apache.org/jira/browse/ATLAS-2698 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch > > > Updating the docs module to include documentation around Glossary -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site
[ https://issues.apache.org/jira/browse/ATLAS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2698: --- Attachment: 0001-ATLAS-2698-Glossary-related-documentation.patch > [Glossary] Add docs related to Glossary for Apache site > --- > > Key: ATLAS-2698 > URL: https://issues.apache.org/jira/browse/ATLAS-2698 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0-alpha >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch > > > Updating the docs module to include documentation around Glossary -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site
Apoorv Naik created ATLAS-2698: -- Summary: [Glossary] Add docs related to Glossary for Apache site Key: ATLAS-2698 URL: https://issues.apache.org/jira/browse/ATLAS-2698 Project: Atlas Issue Type: Improvement Affects Versions: 1.0.0-alpha Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 Updating the docs module to include documentation around Glossary -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1874) V2 DSL search query does not support for count() but v1 do.
[
https://issues.apache.org/jira/browse/ATLAS-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-1874.
Resolution: Fixed
> V2 DSL search query does not support for count() but v1 do.
> ---
>
> Key: ATLAS-1874
> URL: https://issues.apache.org/jira/browse/ATLAS-1874
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.1
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0, 0.8.1
>
>
> v1 DSL query supports count()
> {noformat}
> curl -u admin:admin
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/discovery/search/dsl?query=hive_table%20where%20db.name%3D%22default%22%20select%20count()%20as%20%27count%27'
> | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 5370 5370 0339 0 --:--:-- 0:00:01 --:--:-- 339
> {
> "count": 1,
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "long",
> "isComposite": false,
> "isIndexable": false,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "count",
> "reverseAttributeName": null
> }
> ],
> "typeDescription": null,
> "typeName": "__tempQueryResultStruct286",
> "typeVersion": "1.0"
> },
> "query": "hive_table where db.name=\"default\" select count() as 'count'",
> "queryType": "dsl",
> "requestId": "pool-2-thread-9 - 47389e3f-bbf1-4209-8e50-8a3235a7e5a9",
> "results": [
> {
> "$typeName$": "__tempQueryResultStruct286",
> "count": 68
> }
> ]
> }
> {noformat}
> v2 DSL search query does not
> {noformat}
> curl -u admin:admin
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/v2/search/dsl?limit=25=true=where+db.name%3D%22default%22+select+count()+as+%27count%27=hive_table&_=1497434602692'
> | python -m json.tool
> {
> "queryText": "`hive_table` where db.name=\"default\" select count() as
> 'count'",
> "queryType": "DSL"
> }
> {noformat}
> *From the initial analysis, it seems like, V2 API response does not have the
> count attribute which is cause for this failure.* might want to consider
> adding the count in V2?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-1874) V2 DSL search query does not support for count() but v1 do.
[
https://issues.apache.org/jira/browse/ATLAS-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik reassigned ATLAS-1874:
--
Assignee: Apoorv Naik
> V2 DSL search query does not support for count() but v1 do.
> ---
>
> Key: ATLAS-1874
> URL: https://issues.apache.org/jira/browse/ATLAS-1874
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.1
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> v1 DSL query supports count()
> {noformat}
> curl -u admin:admin
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/discovery/search/dsl?query=hive_table%20where%20db.name%3D%22default%22%20select%20count()%20as%20%27count%27'
> | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 5370 5370 0339 0 --:--:-- 0:00:01 --:--:-- 339
> {
> "count": 1,
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "long",
> "isComposite": false,
> "isIndexable": false,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "count",
> "reverseAttributeName": null
> }
> ],
> "typeDescription": null,
> "typeName": "__tempQueryResultStruct286",
> "typeVersion": "1.0"
> },
> "query": "hive_table where db.name=\"default\" select count() as 'count'",
> "queryType": "dsl",
> "requestId": "pool-2-thread-9 - 47389e3f-bbf1-4209-8e50-8a3235a7e5a9",
> "results": [
> {
> "$typeName$": "__tempQueryResultStruct286",
> "count": 68
> }
> ]
> }
> {noformat}
> v2 DSL search query does not
> {noformat}
> curl -u admin:admin
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/v2/search/dsl?limit=25=true=where+db.name%3D%22default%22+select+count()+as+%27count%27=hive_table&_=1497434602692'
> | python -m json.tool
> {
> "queryText": "`hive_table` where db.name=\"default\" select count() as
> 'count'",
> "queryType": "DSL"
> }
> {noformat}
> *From the initial analysis, it seems like, V2 API response does not have the
> count attribute which is cause for this failure.* might want to consider
> adding the count in V2?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-2623) Assigning duplicate term to entity
[
https://issues.apache.org/jira/browse/ATLAS-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-2623.
Resolution: Not A Problem
> Assigning duplicate term to entity
> --
>
> Key: ATLAS-2623
> URL: https://issues.apache.org/jira/browse/ATLAS-2623
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Minor
> Fix For: 1.0.0
>
>
> Assigned term to entity using following request body POSTed to
> /api/atlas/v2/glossary/terms//assignedEntities
> {code}
> [\{"guid":"c8075f3c-a9f1-4060-a113-fc4819e5f647"}]
> {code}
> Fired the same POST query again. Request succeeded with 204.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-2636) Business catalog: Creating a glossary with incorrect GUID, fails first time. When the same request with the same payload returns "409 conflict" saying "Glossary category
[
https://issues.apache.org/jira/browse/ATLAS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik resolved ATLAS-2636.
Resolution: Fixed
Resolved by ATLAS-2667
> Business catalog: Creating a glossary with incorrect GUID, fails first time.
> When the same request with the same payload returns "409 conflict" saying
> "Glossary category with qualifiedName category1 already exists"
> --
>
> Key: ATLAS-2636
> URL: https://issues.apache.org/jira/browse/ATLAS-2636
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>
> * Create a category with below payload, this will fail with 500 internal
> error.
> {noformat}
> {
> "qualifiedName": "category1",
> "displayName": "Bank accounts",
> "anchor": {
> "glossaryGuid": "-1"
> }
> }
> {noformat}
> * Repeat the same request again, now atlas throws below error
> {noformat}
> {
> "errorCode": "ATLAS-409-00-00A",
> "errorMessage": "Glossary category with qualifiedName category1 already
> exists"
> }
> {noformat}
> Does this mean, the first request succeeded to register the category?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-2636) Business catalog: Creating a glossary with incorrect GUID, fails first time. When the same request with the same payload returns "409 conflict" saying "Glossary category
[
https://issues.apache.org/jira/browse/ATLAS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik reassigned ATLAS-2636:
--
Assignee: Apoorv Naik
> Business catalog: Creating a glossary with incorrect GUID, fails first time.
> When the same request with the same payload returns "409 conflict" saying
> "Glossary category with qualifiedName category1 already exists"
> --
>
> Key: ATLAS-2636
> URL: https://issues.apache.org/jira/browse/ATLAS-2636
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>
> * Create a category with below payload, this will fail with 500 internal
> error.
> {noformat}
> {
> "qualifiedName": "category1",
> "displayName": "Bank accounts",
> "anchor": {
> "glossaryGuid": "-1"
> }
> }
> {noformat}
> * Repeat the same request again, now atlas throws below error
> {noformat}
> {
> "errorCode": "ATLAS-409-00-00A",
> "errorMessage": "Glossary category with qualifiedName category1 already
> exists"
> }
> {noformat}
> Does this mean, the first request succeeded to register the category?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2623) Assigning duplicate term to entity
[
https://issues.apache.org/jira/browse/ATLAS-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-2623:
---
Priority: Minor (was: Major)
> Assigning duplicate term to entity
> --
>
> Key: ATLAS-2623
> URL: https://issues.apache.org/jira/browse/ATLAS-2623
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Minor
> Fix For: 1.0.0
>
>
> Assigned term to entity using following request body POSTed to
> /api/atlas/v2/glossary/terms//assignedEntities
> {code}
> [\{"guid":"c8075f3c-a9f1-4060-a113-fc4819e5f647"}]
> {code}
> Fired the same POST query again. Request succeeded with 204.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2686) [Glossary] Restrict Term deletion if it's assigned to any entity
[ https://issues.apache.org/jira/browse/ATLAS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478220#comment-16478220 ] Apoorv Naik commented on ATLAS-2686: branch-1.0: https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=fd00220cdf69defbe4733eb863dfbd52bf17ff3b > [Glossary] Restrict Term deletion if it's assigned to any entity > > > Key: ATLAS-2686 > URL: https://issues.apache.org/jira/browse/ATLAS-2686 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2686-Term-can-t-be-deleted-if-it-s-assigned-to.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2343) [DSL] Where keyword has become mandatory
[ https://issues.apache.org/jira/browse/ATLAS-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik reassigned ATLAS-2343: -- Assignee: Ashutosh Mestry > [DSL] Where keyword has become mandatory > - > > Key: ATLAS-2343 > URL: https://issues.apache.org/jira/browse/ATLAS-2343 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 1.0.0 > > > eg. DB name=a fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2343) [DSL] Where keyword has become mandatory
[ https://issues.apache.org/jira/browse/ATLAS-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik resolved ATLAS-2343. Resolution: Fixed Fix Version/s: 1.0.0 > [DSL] Where keyword has become mandatory > - > > Key: ATLAS-2343 > URL: https://issues.apache.org/jira/browse/ATLAS-2343 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 1.0.0 > > > eg. DB name=a fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2686) [Glossary] Restrict Term deletion if it's assigned to any entity
[ https://issues.apache.org/jira/browse/ATLAS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2686: --- Attachment: 0001-ATLAS-2686-Term-can-t-be-deleted-if-it-s-assigned-to.patch > [Glossary] Restrict Term deletion if it's assigned to any entity > > > Key: ATLAS-2686 > URL: https://issues.apache.org/jira/browse/ATLAS-2686 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2686-Term-can-t-be-deleted-if-it-s-assigned-to.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2685) [Glossary] Impose displayName restiction for Glossary, term & category
[ https://issues.apache.org/jira/browse/ATLAS-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2685: --- Attachment: 0001-ATLAS-2685-Impose-displayName-restrictions-for-Gloss.patch > [Glossary] Impose displayName restiction for Glossary, term & category > -- > > Key: ATLAS-2685 > URL: https://issues.apache.org/jira/browse/ATLAS-2685 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Attachments: > 0001-ATLAS-2685-Impose-displayName-restrictions-for-Gloss.patch > > > As per ATLAS-1410 discussions, there certain restriction in place for the > displayName of the Glossary, term and category. This patch enforces those > naming restrictions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: 0001-ATLAS-2671-Dependency-upgrades.patch > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2671-Dependency-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: (was: 0001-Dependency-upgrades.patch) > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2671-Dependency-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2689) Change version from 1.0.0-SNAPSHOT to 1.0.0
[ https://issues.apache.org/jira/browse/ATLAS-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476843#comment-16476843 ] Apoorv Naik commented on ATLAS-2689: +1 > Change version from 1.0.0-SNAPSHOT to 1.0.0 > --- > > Key: ATLAS-2689 > URL: https://issues.apache.org/jira/browse/ATLAS-2689 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2689.patch > > > Update pom.xml files to replace version 1.0.0-SNAPSHOT to 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476842#comment-16476842 ] Apoorv Naik commented on ATLAS-2671: *Version* Spring: 4.3.8 => 4.3.17 Spring security: 4.2.4 => 4.2.6 Jackson: 2.9.2 => 2.9.5 Tinkerpop: 3.2.6 => 3.3.3 Lucene upgrade to 7.3.0 > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2679) [Glossary] Derive category's qualifiedName using hierarchy
[ https://issues.apache.org/jira/browse/ATLAS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476809#comment-16476809 ] Apoorv Naik commented on ATLAS-2679: Committed to master https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=66f8ae16045b79d8839ee2088fc5cc64ffa2fa5d > [Glossary] Derive category's qualifiedName using hierarchy > -- > > Key: ATLAS-2679 > URL: https://issues.apache.org/jira/browse/ATLAS-2679 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > > Currently the qualifiedName is derived using displayName and Glossary's > qualifiedName. > > In this patch, the qualifiedName is derived from it's Hierarchy and any > changes in the hierarchy itself will trigger a cascaded update of all > children. > > E.g. Cat1 is parent category, Cat2 is child category > > Derived qualfiedName of Cat2 = Cat2.Cat1@ > > The following actions trigger a cascaded update of the children categories > > # Change of anchor > # Change of Parent > # Removal of children from a parent (similar to #2) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2686) [Glossary] Restrict Term deletion if it's assigned to any entity
[ https://issues.apache.org/jira/browse/ATLAS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2686: --- Summary: [Glossary] Restrict Term deletion if it's assigned to any entity (was: [Glossary] Term can't be deleted if it's assigned to any entity) > [Glossary] Restrict Term deletion if it's assigned to any entity > > > Key: ATLAS-2686 > URL: https://issues.apache.org/jira/browse/ATLAS-2686 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2686) [Glossary] Term can't be deleted if it's assigned to any entity
Apoorv Naik created ATLAS-2686: -- Summary: [Glossary] Term can't be deleted if it's assigned to any entity Key: ATLAS-2686 URL: https://issues.apache.org/jira/browse/ATLAS-2686 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2685) [Glossary] Impose displayName restiction for Glossary, term & category
Apoorv Naik created ATLAS-2685: -- Summary: [Glossary] Impose displayName restiction for Glossary, term & category Key: ATLAS-2685 URL: https://issues.apache.org/jira/browse/ATLAS-2685 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik As per ATLAS-1410 discussions, there certain restriction in place for the displayName of the Glossary, term and category. This patch enforces those naming restrictions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: (was: 0002-Spring-upgrades.patch) > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: 0001-Dependency-upgrades.patch > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch, > 0002-Spring-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-2671: --- Attachment: (was: 0001-Jackson-and-Lucene-dependency-upgrade.patch) > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-Dependency-upgrades.patch, > 0002-Spring-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2679) [Glossary] Derive category's qualifiedName using hierarchy
Apoorv Naik created ATLAS-2679: -- Summary: [Glossary] Derive category's qualifiedName using hierarchy Key: ATLAS-2679 URL: https://issues.apache.org/jira/browse/ATLAS-2679 Project: Atlas Issue Type: Improvement Reporter: Apoorv Naik Assignee: Apoorv Naik Currently the qualifiedName is derived using displayName and Glossary's qualifiedName. In this patch, the qualifiedName is derived from it's Hierarchy and any changes in the hierarchy itself will trigger a cascaded update of all children. E.g. Cat1 is parent category, Cat2 is child category Derived qualfiedName of Cat2 = Cat2.Cat1@ The following actions trigger a cascaded update of the children categories # Change of anchor # Change of Parent # Removal of children from a parent (similar to #2) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
