You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/06/06 02:19:00 UTC
[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&focusedCommentId=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)