Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cardinality resolves to VertexProperty$Cardinality on server #1222

Open
pluradj opened this issue Aug 14, 2018 · 1 comment
Open

Cardinality resolves to VertexProperty$Cardinality on server #1222

pluradj opened this issue Aug 14, 2018 · 1 comment

Comments

@pluradj
Copy link
Member

pluradj commented Aug 14, 2018

Reported on janusgraph-users

gremlin> JanusGraph.version()
==>0.3.0
gremlin> Cardinality
==>class org.janusgraph.core.Cardinality
gremlin> :remote connect tinkerpop.server conf/remote.yaml session
==>Configured localhost/127.0.0.1:8182
gremlin> :> Cardinality
==>class org.apache.tinkerpop.gremlin.structure.VertexProperty$Cardinality

It would be better if the class loading order was the same between a local Gremlin Console session vs scripts sent to a remote Gremlin Server. This behavior is new in 0.3.0 and does not appear in 0.2.1.

@pluradj
Copy link
Member Author

pluradj commented Aug 28, 2018

A valid workaround is to use the fully-qualified org.janusgraph.core.Cardinality where needed.

This was likely caused by the upgrade to TinkerPop 3.3.x, so a fix in TinkerPop could be necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant