You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Community Note
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):3.6.2
to3.7.1
. The latest version allowed bygraph-notebook
is3.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
.%%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.The text was updated successfully, but these errors were encountered: