Update README description for Apache Solr #2487
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Keeps these descriptions up to date with changes the Apache Solr project made recently in their README, documentation, website, etc. Additional context at: - https://solr.apache.org/ - https://issues.apache.org/jira/browse/SOLR-16295 - apache/solr#2692
|
@gerlowskija, the checks seem to be failing, can you address? Thoughts @shalinmangar @dsmiley @janhoy @HoustonPutman? |
|
Yep, should be fixed - looks like the GH Action needs approval to re-run, but Thanks for giving it a look @whalelines ! |
tianon
approved these changes
Sep 11, 2024
|
Merging based on the wording matching the upstream references -- if one of the |
|
This is approved, sorry for missing it earlier |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Keeps these descriptions up to date with changes the Apache Solr project made recently in their README, documentation, website, etc.
Additional context at: