Adding node filtering on src and dst endpoints for edges #2362
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
…for edges. Compiles, still needs to be added to GraphQL and tested.
…and dst() endpoints.
shivamka1
reviewed
Oct 28, 2025
shivamka1
reviewed
Oct 28, 2025
raphtory/src/db/graph/views/filter/edge_endpoint_property_filtered_graph.rs
Show resolved
Hide resolved
…emporal property, and node_type filtering on edge src and dst endpoints in GraphQL.
Collaborator
Collaborator
|
I think we can continue our work pertaining to this feature in this PR -> #2364. Hence closing this one. |
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?
Adding all node filtering options on src and dst endpoints for edges. This includes property and metadata filtering, as well as operations that can be chained to them.
Why are the changes needed?
Edge src and dst filtering is currently limited to name and id, which is restrictive and inconsistent with the rest of the filtering system.
Does this PR introduce any user-facing change? If yes is this documented?
The same APIs available for node filtering will now be available for filter.Edge.src() and filter.Edge.dst()
How was this patch tested?
Tests to be added