[fix](test) fix unstable sql cache testing because meta default is eventual consistency #60114
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.
doris's default is eventual consistency, and the observer may not see the latest metadata.
this will cause some strange case, e.g. alter table rename a column, and than query can not not see the new column, and the version id not change when the query, so hit the legacy sql cache and the testing failed.
this pr set enable_strong_consistency_read=true when test sql cache to avoid this problem
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)