Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/267#issuecomment-197536538
I won't deny confusion, but I thought that you only get weird stuff with
TinkerGraph when you use it in the default mode where types matter for the ids.
When you define an id manager, it returns expected results:
```text
gremlin> conf = new BaseConfiguration()
==>org.apache.commons.configuration.BaseConfiguration@6273c5a4
gremlin>
conf.setProperty('gremlin.graph','org.apache.tinkerpop.gremlin.tinkergraph.structure.TinkerGraph')
==>null
gremlin> conf.setProperty('gremlin.tinkergraph.vertexIdManager','LONG')
==>null
gremlin> graph = TinkerGraph.open(conf)
==>tinkergraph[vertices:0 edges:0]
gremlin> TinkerFactory.generateModern(graph)
==>null
gremlin> g = graph.traversal()
==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
gremlin> g.V(1).values("name")
==>marko
gremlin> g.V().hasId(1).values("name")
==>marko
gremlin> g.V("1").values("name")
==>marko
gremlin> g.V().hasId("1").values("name")
==>marko
```
I'm pretty sure that other graphs don't suffer this problem either - it's
just the default type system of TinkerGraph that forces the expected type of
the id to match..
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
