atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Venkat (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2216) Remove Catalog/Taxonomy feature from Atlas
Date Wed, 18 Oct 2017 06:32:00 GMT


Srikanth Venkat commented on ATLAS-2216:

[] This will be a good approach to helping Atlas users migrate to newer
and more scalable graph technology while mitigating risk with the current inefficient implementations
that might have undesirable side effects for Atlas users. +1 for this approach! 

> Remove Catalog/Taxonomy feature from Atlas
> ------------------------------------------
>                 Key: ATLAS-2216
>                 URL:
>             Project: Atlas
>          Issue Type: Task
>          Components:  atlas-core
>    Affects Versions: 1.0.0
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>             Fix For: 1.0.0
> Taxonomy was introduced as a tech preview feature earlier, but the following challenges
in design/implementation make it necessary to replace the current implementation with newer
features being introduced:
> 1. Current implementation uses tags to model taxonomy terms, which limits a term to be
associated to one entity only. Associating with multiple entities would require copying of
a term, making it difficult to manage.
> 2. Current implementation uses dot separated naming convention to model taxonomy hierarchy.
This makes it inefficient to rebuild taxonomy hierarchy.
> 3. Current implementation uses tinkerpop blueprints API and makes it difficult for migration
to newer tinkerpop version.
> 4. Current implementation is tied to tinkerpop2/titan0 version and since this is not
abstracted; it blocks the introduction of JanusGraph into Atlas
> ATLAS-1410 introduces a new Glossary API, which uses entities to model taxonomy terms
and uses relationships feature to associate terms with entities. Also, the new model includes
categories, which makes Glossary to be used for wider use-cases. Use of relationships to associate
terms with entities would also allow tag-propagation more naturally.
> Given above, I propose to remove current tech-preview implementation of taxonomy feature
from both server-side and UI in master branch. Once this is removed, existing taxonomy terms
will be seen as tags along with rest of the tags.

This message was sent by Atlassian JIRA

View raw message