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/07/19 19:31:00 UTC

[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<String> 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)