-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Trigger indexing from a recipe #12199
Labels
Milestone
Comments
25 tasks
Maybe a good candidate for our new |
lampersky
added a commit
to lampersky/OrchardCore
that referenced
this issue
Aug 29, 2022
lampersky
added a commit
to lampersky/OrchardCore
that referenced
this issue
Aug 30, 2022
lampersky
added a commit
to lampersky/OrchardCore
that referenced
this issue
Aug 30, 2022
lampersky
added a commit
to lampersky/OrchardCore
that referenced
this issue
Aug 30, 2022
lampersky
added a commit
to lampersky/OrchardCore
that referenced
this issue
Aug 31, 2022
lampersky
added a commit
to lampersky/OrchardCore
that referenced
this issue
Aug 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, when we are creating a search index from a recipe it doesn't build the index. This causes issues with Lucene and Elasticsearch where the Queries won't return any results and also Elasticsearch will log an issue about "all shards failed" if nothing has been indexed yet in its indexes.
Describe the solution you'd like
As an enhancement. It would be nice to be able to trigger an index to be rebuilt or reset from a scheduled background task as a one-time only task.
The text was updated successfully, but these errors were encountered: