Is there an ETA on Neptune returning full element data?
Currently, Neptune still behaves like configured with ReferenceElementStrategy, i.e. it only returns element ids and labels. I remember this was about to change...is this still true and is there an ETA ?
6 Replies
Hello @Daniel Weber curious if you have tried the
materializeProperties configuration? g.with('materializeProperties', 'all').V() . See https://tinkerpop.apache.org/docs/current/reference/ and search for materializePropertiesSorry I just found the documentation that neptune doesn't support
materializeProperties https://docs.aws.amazon.com/neptune/latest/userguide/access-graph-gremlin-differences.html#feature-gremlin-differences-properties-on-elementsGremlin standards compliance in Amazon Neptune - Amazon Neptune
Overview of differences between the Neptune and TinkerPop implementations of Gremlin.
Depending on what exactly you are looking to do you can get all the properties returned by default (instead of reference elements) if you query the HTTPS endpoint instead of using web cokets and the driver
still working on getting
materializeProperties into Neptune for websockets. not sure what the ETA is just yet i'm afraid.
@Arthur from gdotv i assume materializeProperties would be useful to use from a Neptune perspective?Definitely yeah!
Thanks everybody for clarification 🙂