[jira] [Commented] (TINKERPOP-1048) Vertex lookups by id are inconsistent

["stephen mallette (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955608#comment-15955608 ] 

stephen mallette commented on TINKERPOP-1048:
---------------------------------------------

Another interesting aspect to this issue is that doing a {{GraphReader.readObject(graph, TinkerGraph.class)}} will instantiate a TinkerGraph with the default of ANY which is the best choice for an {{IdManager}} given that the graph being read in could be data from a graph of a different type - like a subgraph of a JanusGraph for example. If that's the case, then defaulting to something other than ANY would cause this feature to break.

I come back to this issue every so often and always find some new blocker to fixing it. Annoying.

> Vertex lookups by id are inconsistent
> -------------------------------------
>
>                 Key: TINKERPOP-1048
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1048
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: tinkergraph
>    Affects Versions: 3.1.1-incubating
>            Reporter: Daniel Kuppitz
>            Assignee: stephen mallette
>
> {{graph.vertices(id)}}, {{g.V(id)}} and {{g.V().hasId(id)}} should all return the same result. However, currently only the latter respects the {{toString()}} representation of ids.
> {noformat}
> gremlin> g.addV().id()
> ==>12
> gremlin> graph.vertices("12")
> gremlin> g.V("12")
> gremlin> g.V().hasId("12")
> ==>v[12]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)