Avoid calling the database in case of exception for a period configured #3941
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
pbench
approved these changes
Feb 20, 2023
pbougue
approved these changes
Feb 21, 2023
xlqian
approved these changes
Feb 21, 2023
|
Kudos, SonarCloud Quality Gate passed! |
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.
If There is an exception while sending a query to the database, we should update last_update time to NOW so that no query is send to the data base for another update_interval as configured.
This correction avoids access to the data for each service as street_network, external_service as well as bss_provide for a period of update_interval as configured.
There are some minor modifications to reduce possible error.
Relates to: https://navitia.atlassian.net/browse/NAV-1819