[ENH] Add index on database_id, name on collections table in sysdb

[jairad26]

Description of changes

This PR adds a new index on the collections table on (databse_id, name). This is the first of 2 PRs to remove the existing index on (name, database_id). This is because list collections does a full table scan on collections to filter where database_id matches. By moving the index to database_id first, it supports both the list_collection use case of indexing on database_id, while maintaining the index which is useful for get_collection (which indexes on name and database id)

before:

after:

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?

Observability plan

What is the plan to instrument and monitor this change?

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[jairad26]

• [ENH] Add index on database_id, name on collections table in sysdb #5102 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

Add Index on (database_id, name) to collections Table in sysdb

This PR introduces a new unique index on the collections table in the sysdb database for the columns (database_id, name). The change is part of a two-step migration to optimize collection listing queries by shifting the index order, which currently leads to full table scans when filtering by database_id.

Key Changes

• Added migration file to create a unique index on (database_id, name) for the collections table.
• Updated the migration checksum in atlas.sum to reflect the new migration.

Affected Areas

• Database schema (collections table)
• Migration files

This summary was automatically generated by @propel-code-bot