fix: add option for faster resource type item or test determination #125
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
hectoras
reviewed
Sep 11, 2024
hectoras
reviewed
Sep 11, 2024
hectoras
approved these changes
Sep 12, 2024
Version
There are 0 BREAKING CHANGE, 0 feature, 2 fixes |
tikhanovichA
approved these changes
Sep 17, 2024
pnal
deleted the
feat/ADF-1761/avoid-slow-query-to-determine-resource-type
branch
Merged
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.
This PR aims to avoid recursive class structure querying to identify resource type in the most cases.
Some background:
For translations we import a huge amount of test packages that triggers indexation and as well as we use nested and huge classes structure. It was found that at some point we have a huge frequently repeated query which stresses DB: