IMPROVED: Tenant support for query plans #2955
Open
Conversation
This file contains 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
rPraml
changed the title
rPraml
added a commit
to FOCONIS/ebean
that referenced
this pull request
Aug 10, 2023
rPraml
force-pushed
the
tenant-support-for-query-plans
branch
from
4c619b2 to
1c0a811
Compare
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.
We have a multi tenant application (~50 tenants, TenantMode.DB_WITH_MASTER)
and with #2954 we have a great tool to generate HTML metrics and inspect the live running application.Unfortunately, query-plan collect works only for the master DB as the tenantId is not captured.
In our case, every tenant-db has the same layout, but the master db is nearly empty and collecting plans there makes no sense.
In this PR I changed this, so that the tenantId is captured and the plan is collected from the correct DB