You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Bryn Cooke (JIRA)" <ji...@apache.org> on 2015/04/24 13:04:38 UTC
[jira] [Created] (TINKERPOP3-642) ElementIdStrategy behaves
strangely if you set the ID field via the underlying property name
Bryn Cooke created TINKERPOP3-642:
-------------------------------------
Summary: ElementIdStrategy behaves strangely if you set the ID field via the underlying property name
Key: TINKERPOP3-642
URL: https://issues.apache.org/jira/browse/TINKERPOP3-642
Project: TinkerPop 3
Issue Type: Bug
Reporter: Bryn Cooke
Occures in Titan, but I believe that the fix is probably on the TP side
{code:java}
strategy = ElementIdStrategy.build().idPropertyKey("name").create()
ig = GraphTraversalSource.build().with(strategy).create(g)
ig.addV("name", "test");
ig.V().valueMap();
==>[name:[b979ade9-e328-455d-bd53-9fc0674993f1]] //Expected "test"
{code}
I would expect to still be able to set the name property as normal and for it to be also accessible via id or name properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)