[cassandra] Prevent fallback to old schema for operation names table in case of db issues #6061
+148
−34
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.
Which problem is this PR solving?
Description of the changes
The current operation names table check logic creates
OperationNamesStorage
instance pointing to old schema table in case of issues with Cassandra.OperationNamesStorage
constructorNewOperationsStorage
to returnerror
if both old and new tables doesn't exist or both of their existence cannot be checked. Since there was noerror
returned fromNewOperationsStorage
earlier had to update the dependencies and handle theerror
accordingly.How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test