Output nodes and edges in similarity search#1975
Merged
Conversation
8532ab1 to
08d5b82
Compare
dc8a1de to
b36faef
Compare
b36faef to
0cfd177
Compare
c83d78f to
015b081
Compare
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
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.
What changes were proposed in this pull request?
create gqldocuments + output nodes and edges as well as gqldocument in that object
Why are the changes needed?
so i can get node types and props in semantic search
Does this PR introduce any user-facing change? If yes is this documented?
How was this patch tested?
Are there any further changes required?