Add a way to pass database
context as header from swagger UI
#12695
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.
Description
This is a best effort attempt to allow passing database context as http header to perform table/schema specific requests.
The approach piggy backs on the
@Authorization
API on swagger to inject the database header disguised as API Auth key.Post this change the swagger UI will have an option to set the database context once and use it throughout all operations.
Input screen will look like
Related resources
Database
support in Pinot #12333database
http header #12417