rework search indexing #12447
Merged
rework search indexing #12447
Conversation
This file contains hidden or 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
- reconfigure the docsearch scraper to store component and version for each res - switch from the Docker image to a resuable GitHub Action - add publish-docsearch-config extension to transform Handlebars into YAML
spring-projects-issues
added
the
status: waiting-for-triage
marcusdacoregio
added
in: docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When this is merged, the first build will generate and publish the docsearch-config.json file. That fill will subsequently be used by the scraper.
Once that build is complete, a maintainer will need to trigger the "Rebuild Search Index" workflow. That will generate a new search index. However, this index will still work with the existing client.
Next, the UI PR that enhances the search client will need to be merged. (spring-io/antora-ui-spring#49)
Finally, a full build of the site (Deploy Docs) will need to be triggered by a maintainer. At that point, the new search records and client will be rolled out.