fix: handle null values correctly for legacy source connector#132
Merged
ali-ince merged 2 commits intoneo4j:mainfrom Jun 11, 2024
ali-ince:fix-null-schema-old-connector
Merged
fix: handle null values correctly for legacy source connector#132ali-ince merged 2 commits intoneo4j:mainfrom ali-ince:fix-null-schema-old-connector
ali-ince merged 2 commits intoneo4j:mainfrom
ali-ince:fix-null-schema-old-connector
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR fixes a problem where NULL values returned as part of a QUERY strategy are not handled correctly and causes errors in the connector.
Forward port of neo4j-contrib/neo4j-streams#628.