You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Suma Shivaprasad (JIRA)" <ji...@apache.org> on 2015/09/14 13:49:45 UTC
[jira] [Commented] (ATLAS-145) DSL - Fix back reference DSL to
gremlin translation issues
[ https://issues.apache.org/jira/browse/ATLAS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743407#comment-14743407 ]
Suma Shivaprasad commented on ATLAS-145:
----------------------------------------
We need to change the DSL to gremlin translation here to
g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", T.eq, "Reporting")).map().toList()
> DSL - Fix back reference DSL to gremlin translation issues
> ----------------------------------------------------------
>
> Key: ATLAS-145
> URL: https://issues.apache.org/jira/browse/ATLAS-145
> Project: Atlas
> Issue Type: Bug
> Reporter: Suma Shivaprasad
>
> GremlinQuery.scala
> /*
> * TODO
> * Translation Issues:
> * 1. back references in filters. For e.g. testBackreference: 'DB as db Table where (db.name = "Reporting")'
> * this is translated to:
> * g.V.has("typeName","DB").as("db").in("Table.db").and(_().back("db").has("name", T.eq, "Reporting")).map().toList()
> * But the '_().back("db") within the and is ignored, the has condition is applied on the current element.
> * The solution is to to do predicate pushdown and apply the filter immediately on top of the referred Expression.
> */
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)