Enable find jobs by fleet_id in backoffice - #2474
Draft
Alberto Vilches (avilches) wants to merge 2 commits into
Draft
Enable find jobs by fleet_id in backoffice#2474Alberto Vilches (avilches) wants to merge 2 commits into
Alberto Vilches (avilches) wants to merge 2 commits into
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.
Summary
Lets the job list search in the admin backoffice match by fleet_id, and adds a background (concurrent) index on that column so the search stays fast. The Runner column now shows the engine job id (ray_job_id or fleet_id) as the link to the job page, with Ray/Fleets as a label underneath, instead of just the runner name.
Details and comments
fleet_id had no index before, so the migration uses PostgreSQL's CREATE INDEX CONCURRENTLY to avoid locking api_job while it builds. It falls back to a plain index on non-PostgreSQL backends, since the test suite runs against SQLite.