[fix](info_db) avoid infodb query timeout when external catalog info is too large or is not reachable #18662
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
…is too large or is not reachable
github-actions
bot
added
area/planner
morningman
changed the title
Contributor
Author
|
run buildall |
morningman
added a commit
that referenced
this pull request
Apr 14, 2023
…is too large or is not reachable (#18662) When query tables in information_schema databases, it may timeout due to: There are external catalog with too many tables. The external catalog is unreachable So I add a new FE config infodb_support_ext_catalog. The default is false, which means that when select from tables in information_schema database, the result will not contain the information of the table in external catalog. Describe your changes.
gnehil
pushed a commit
to gnehil/doris
that referenced
this pull request
Apr 21, 2023
…is too large or is not reachable (apache#18662) When query tables in information_schema databases, it may timeout due to: There are external catalog with too many tables. The external catalog is unreachable So I add a new FE config infodb_support_ext_catalog. The default is false, which means that when select from tables in information_schema database, the result will not contain the information of the table in external catalog. Describe your changes.
Reminiscent
pushed a commit
to Reminiscent/doris
that referenced
this pull request
May 15, 2023
…is too large or is not reachable (apache#18662) When query tables in information_schema databases, it may timeout due to: There are external catalog with too many tables. The external catalog is unreachable So I add a new FE config infodb_support_ext_catalog. The default is false, which means that when select from tables in information_schema database, the result will not contain the information of the table in external catalog. Describe your changes.
Closed
mongo360
pushed a commit
to mongo360/doris
that referenced
this pull request
Jul 12, 2023
…is too large or is not reachable (apache#18662) When query tables in information_schema databases, it may timeout due to: There are external catalog with too many tables. The external catalog is unreachable So I add a new FE config infodb_support_ext_catalog. The default is false, which means that when select from tables in information_schema database, the result will not contain the information of the table in external catalog. Describe your changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…is too large or is not reachable
Proposed changes
Issue Number: close #xxx
When query tables in
information_schemadatabases, it may timeout due to:So I add a new FE config
infodb_support_ext_catalog.The default is false, which means that when select from tables in information_schema database,
the result will not contain the information of the table in external catalog.
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...