Skip to content

Properties in BaseDocument of Traversal are empty #50

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

Closed
lukasmahr opened this issue Sep 12, 2016 · 4 comments
Closed

Properties in BaseDocument of Traversal are empty #50

lukasmahr opened this issue Sep 12, 2016 · 4 comments

Comments

@lukasmahr
Copy link

Hi,

I think the issue #21 still exists for traversals. I tested the following code from version 2.7.4 up to 3.0.2 with ArangoDB version 3.0.5:

TraversalQueryOptions options = new TraversalQueryOptions();
options.setGraphName("GRAPHNAME");
options.setDirection(Direction.OUTBOUND);
options.setStartVertex("COL/123");
TraversalEntity<BaseDocument, BaseDocument> traversalEntity = arangoDb.getTraversal(options, BaseDocument.class, BaseDocument.class);
traversalEntity.getVertices().get(0).getEntity().getProperties().size(); // <--- this returns 0 for every entity

The TraversalEntity contains the correct vertices and edges, but the properties are missing.
Reading the startVertex with arangoDb.getDocument("COL/123", BaseDocument.class) works fine (including the properties).

Thank you in advance!

@a-brandt
Copy link
Contributor

Hello!
I released version 3.0.3 of arangodb-java-driver to fix the problem.
Please try again with that version.

@lukasmahr
Copy link
Author

Thank you very much! The problem is fixed.

But i recognized another issue:

traversalEntity.getPaths().get(0).getEdges().get(0).getFromVertexHandle();
traversalEntity.getPaths().get(0).getEdges().get(0).getToVertexHandle();

The properties of the BaseDocument contain the "_from" and "_to" value with the handle. But both of these statements above return NULL.

a-brandt pushed a commit that referenced this issue Sep 14, 2016
a-brandt pushed a commit that referenced this issue Sep 14, 2016
@a-brandt
Copy link
Contributor

I fixed the problem in the current snapshot version 3.0.4-SNAPSHOT and will be released soon.

@mvollmary
Copy link

fixed in version 3.0.4

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

3 participants