Enforce Gremlin protocol and serializer based on database type #697
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelnchin
force-pushed
the
gremlin-expanded-serializers-neptune-adjustments
branch
from
5f19ed4
to
339be6c
Compare
michaelnchin
deleted the
gremlin-expanded-serializers-neptune-adjustments
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: N/A
Description of changes:
connection_protocolandmessage_serializerbased on service typemessage_serializernot enforcing serializer input compatible with the GremlinPython driver when connecting to non-Neptune endpointsmessage_serializerto GraphSON-untyped serializers on HTTP connectionsBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.