feat: Search pipeline name in pipeline run API#129
Open
yuechao-qin wants to merge 1 commit intoycq/search-pipeline-run-legacy-filterfrom
Open
feat: Search pipeline name in pipeline run API#129yuechao-qin wants to merge 1 commit intoycq/search-pipeline-run-legacy-filterfrom
yuechao-qin wants to merge 1 commit intoycq/search-pipeline-run-legacy-filterfrom
Conversation
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Feb 26, 2026
yuechao-qin
commented
Feb 27, 2026
f8f6e26 to
004fc05
Compare
f8b3f75 to
7a7a60b
Compare
7a7a60b to
2b4e624
Compare
004fc05 to
64651a0
Compare
2b4e624 to
10cd01f
Compare
64651a0 to
bb02751
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.

TL;DR
Implemented search
namein Pipeline Runs.What changed?
Functional
API
GET /api/pipeline_runs/filter_query. Example query (not URL encoded for example):/api?filter_query={"and": [{"value_equals": {"key": "system/pipeline_run.name", "value": "My pipeline run name"}}]}API
POST /api/pipeline_runs/abc123system/pipeline_run.nameMy pipeline run nameOther
backfill_pipeline_name_annotationsfunction to populate existing pipeline runs with name annotationsHow to test?
SystemKey.NAMEwork with different predicate types (exists, equals, contains, in)Why make this change?