SOLR-17330: When not set, loadOnStartup defaults to true #2513
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.
SOLR-17330
Description
That's a pretty small change, replacing default value for
loadOnStartup
fromfalse
totrue
when the value is missing from core properties.The default value when creating a new core is already
true
, so I don't expect any behavior change. Fixing this because I wasted some time understanding the code because of the inconsistent values.I filled a Jira to track it, but I did not update the
CHANGES
file since no user should perceive the change (let me know if that's necessary).Solution
Just set default to true.
Tests
None
Checklist
Please review the following and check all that apply:
main
branch../gradlew check
.