-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Fix schemaCacheTTL ParseServerOption is not working #7138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7138 +/- ##
==========================================
+ Coverage 93.90% 93.92% +0.02%
==========================================
Files 169 169
Lines 12535 12535
==========================================
+ Hits 11771 11774 +3
+ Misses 764 761 -3
Continue to review full report at Codecov.
|
|
Can you write a test for when TTL expires? |
davimacedo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me. @dplewis any other comment?
…7138) * Add Test case for checking SchemaCacheTTL * Fix schemaCacheTTL not working issue * Add Test case for TTL expires Co-authored-by: Roach Chang <roach.chang@aoitek.com>
|
🎉 This change has been released in version 5.0.0-beta.1 |
|
🎉 This change has been released in version 5.0.0 |
New Pull Request Checklist
Issue Description
It seems
schemaCacheTTLParseServerOption is not working. It still follows cacheAdapter's setting.Related issue: closes #7119
Approach
Pass the schemaCacheTTL config to the cacheController while setting the schema cache.
TODOs before merging