-
Notifications
You must be signed in to change notification settings - Fork 13k
regression: adjust license #30948
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
regression: adjust license #30948
Conversation
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-6.5.0 #30948 +/- ##
=================================================
+ Coverage 49.86% 51.33% +1.47%
=================================================
Files 784 813 +29
Lines 14950 15234 +284
Branches 2791 2817 +26
=================================================
+ Hits 7455 7821 +366
+ Misses 7081 6984 -97
- Partials 414 429 +15
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
It appears to me that when you do a change like this: it can lead to the following fatal error on startup: That is, you can't just simply change the options for an index. You have to somehow handle the transition from the old options to the new options. |
|
This PR adds a migration that drops the old index, however the migrations don't run until after the index creation was attempted. After the migration runs, we have no index at all, neither with its new or old options. We don't attempt again to create the index until RC is restarted again, so for that entire run, those queries will require COLLSCANs. Is there a way of having the migrations not only drop the old index but also immediately trigger the re-creation? A possible solution is to name the index explicitly, mentioning the options, e.g. |
Proposed changes (including videos or screenshots)
Issue(s)
Steps to test or reproduce
Further comments