Bug in gremlin 2.30?

[np10k]

Hi all. I think there is a problem in gremlin.

Suppose we have a gml graph (test.gml) like this:

graph [

node [

id 1

blueprintsId "123"

]

node [

id 2

blueprintsId "456"

]

]

now let's read the gml:

gremlin> g = new TinkerGraph()

==>tinkergraph[vertices:0 edges:0]

gremlin> g.loadGML("...test.gml")

==>null

and then remove a vertex and save in a gml file:

gremlin> v=g.v(1)         

==>v[1]

gremlin> g.removeVertex(v)

==>null

gremlin> g.saveGML("...test2.gml")

==>null

At this point opening the gml test2, I have this:

graph [

node [

id 1

blueprintsId "2"

blueprintsId "456"

]

]

Note that there is a new blueprintsId!

What's the reason? 

Thank you!

[Stephen Mallette]

That looks like a bug.  It shouldn't be writing two blueprintsId property values.  Can you please create an blueprints issue in GitHub referencing this post?

--
You received this message because you are subscribed to the Google Groups "Gremlin-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gremlin-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[np10k]

done at: https://github.com/tinkerpop/gremlin/issues/375