[
https://issues.apache.org/jira/browse/TINKERPOP3-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546673#comment-14546673
]
stephen mallette commented on TINKERPOP3-684:
---------------------------------------------
Is there some test in our suite that enforces a behavior that says "if
supportsMultiProperties=false then throw an exception for Vertex.properties()"?
I can't seem to find one, in which case is there a reason you don't implement
that method with the knowledge that your implementation will only every get
back a unique list of properties (i.e. each property will have a different key
or if they specify a key it will always return just one property)?
> IoTest failling on 3.0.0.M9-incubating-rc2
> ------------------------------------------
>
> Key: TINKERPOP3-684
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-684
> Project: TinkerPop 3
> Issue Type: Bug
> Components: io
> Affects Versions: 3.0.0.GA
> Reporter: pieter martin
>
> I am running {code}IoTest.shouldReadWriteVerticesNoEdgesToGraphSON{code}
> which fails with {code}java.lang.UnsupportedOperationException: Properties on
> a vertex property is not supported{code}
> This is happening because {code}StarGraph.of(final Vertex vertex){code}
> is calling {code}vp.properties().forEachRemaining(p ->
> starVertexProperty.property(p.key(), p.value()));{code}
> This invokes vp.properties and alas this is not allowed as the graph does not
> support properties on properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
