Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: separate catalog schema API #25468

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Conversation

hiltontj
Copy link
Contributor

@hiltontj hiltontj commented Oct 16, 2024

Separate out methods of the Catalog API that are used on the query side into a new trait DatabaseSchemaProvider. The new trait includes methods from the Catalog that get the underlying DatabaseSchema or interact with names/IDs.

This will allow for a separate implementation of the Catalog for pro that only needs to hold a replicated/combined view in-memory of one or more catalogs without the need to do persistence that a write buffer's catalog needs to do.

While in there I also switched the QueryExecutorImpl::new method to take an args struct to avoid the clippy lint.

@hiltontj hiltontj added the v3 label Oct 16, 2024
@hiltontj hiltontj self-assigned this Oct 16, 2024
@hiltontj hiltontj force-pushed the hiltontj/catalog-interfaces branch 4 times, most recently from eabaaa6 to f861337 Compare October 16, 2024 15:05
@hiltontj hiltontj marked this pull request as ready for review October 16, 2024 15:18
Copy link
Contributor

@praveen-influx praveen-influx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@hiltontj hiltontj merged commit 10b6a28 into main Oct 16, 2024
15 checks passed
@hiltontj hiltontj deleted the hiltontj/catalog-interfaces branch October 16, 2024 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants