[
https://issues.apache.org/jira/browse/ATLAS-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664130#comment-16664130
]
ASF subversion and git services commented on ATLAS-2520:
--------------------------------------------------------
Commit 5317a7215e21321235c1b9cc99d61d78b10659eb in atlas's branch
refs/heads/master from apoorvnaik
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=5317a72 ]
ATLAS-2520: Introduce JanusGraphTraversal to deprecate use of
GremlinScriptEngine
> 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)
