AWS Neptune updating gremlin driver to 3.6.2 introduced many bugs to working queries
After updating Amazon Neptune engine version from 1.2.0.2 to 1.2.1.0 and the Gremlin.Net (C# nuget) driver from 3.5.2 to 3.6.2, suddenly queries started throwing exceptions, specifically exceptions about serialization errors. To pinpoint the cause, I downgraded the Gremlin.Net driver to 3.5.2 while leaving the engine version updated to 1.2.1.0, the queries started working like before.
The problem is, according to the AWS documentation, the minimum required Gremlin.net version is 3.6.2
Will there be a problem keeping the Gremlin.net driver version to 3.5.2? Will there be any side effects?
Resources:
Aws documentation: https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.2.1.0.html#engine-releases-1.2.1.0-query-versions
The problem is, according to the AWS documentation, the minimum required Gremlin.net version is 3.6.2
Will there be a problem keeping the Gremlin.net driver version to 3.5.2? Will there be any side effects?
Resources:
Aws documentation: https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.2.1.0.html#engine-releases-1.2.1.0-query-versions
Apache TinkerPop is an open source graph computing framework and the home of the Gremlin graph query language.
1,376Members
Resources
Similar Threads
Was this page helpful?
