Skip to content

Support Neptune DB 1.3.2.0 #612

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
michaelnchin opened this issue Jun 7, 2024 · 0 comments
Closed

Support Neptune DB 1.3.2.0 #612

michaelnchin opened this issue Jun 7, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@michaelnchin
Copy link
Member

Community Note

  • Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Is your feature request related to a problem? Please describe.

Neptune DB engine version 1.3.2.0 is generally available as of 6/3: https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.3.2.0.html

This release implements several major changes that may warrant modifications to graph-notebook, including (but not limited to):

  • Tinkerpop 3.7.x - Neptune DB now supports TinkerPop versions from 3.6.2 to 3.7.1. The latest version allowed by graph-notebook is 3.6.2, which should be upgraded for parity. Additionally, TinkerPop 3.7 has added, removed, or renamed numerous message serializers, a change which renders invalid several currently permitted inputs to the --profile-serializer argument of %%gremlin profile.
  • Query Plan Cache - Neptune DB now supports the openCypher QPC functionality that was previously available only for Neptune Analytics. We should now change %%oc to un-restrict the --plan-cache option for Neptune DB hosts, taking consideration that the QPC implementation is slightly different for DB, which requires passing a query hint instead of an HTTP parameter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Resolved
Development

No branches or pull requests

1 participant