This is a bug in the DB in version 3.1.RC2 and 3.1.RC3. It is fixed in
final version 3.1, which we release at the moment. It should be available
in the next 1-2 days.
With that version you need the java driver in version 4.1.0, because we
changed the velocystream protocol in the DB version 3.1, to remove the need
of an extra velocystream endpoint. Driver version 4.1.0 only works with the
final release and not with the RCs.
You can use Map for every result, not only for sinlge documents.
Your approach, to use Map for these queries, is correct and will work when
ArangoDB 3.1 is released.
Am Montag, 31. Oktober 2016 11:12:19 UTC+1 schrieb Rob Keevil:
>
> On further inspection I suspect this is a bug. The query:
> FOR v, e IN 1..3 OUTBOUND 'persons/eve' GRAPH 'knows_graph' RETURN {v:v,
> e: e}
> errors the java driver with a null pointer, whether I use a Map or
> BaseDocument
>
> The equivalent query:
> FOR v, e IN 1..3 OUTBOUND 'persons/eve' GRAPH 'knows_graph' RETURN {v:
> {"_key": v._key, "_id": v._id, "_rev": v._rev, "name": v.name}, e:
> {"_key": e._key, "_id": e._id, "_rev": e._rev, "_from":e._from, "_to":e.
> _to}}
> works for both types.
>
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
