-
Notifications
You must be signed in to change notification settings - Fork 24
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
Stale data in Solr; method to cleanly remove it #177
Comments
heddn
pushed a commit
to heddn/search_api_pantheon
that referenced
this issue
Mar 29, 2024
Any reason to not submit a patch/MR to search_api_solr that removes the devel dependency on search_api_solr_devel to allow the command to be used without Devel? Maybe move the command to the parent search_api_solr module? |
I've opened https://www.drupal.org/project/search_api_solr/issues/3440032. If that gets support, I'm happy to open an MR or patch to move the namespace of the drush command. |
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.
I have a CI/CD build that fresh installs the site and adds default content. Each install causes the Solr index to index more and more data and the old data from past installs never gets flushed.
Describe the solution you'd like
Search API Solr Devel module has a command to solve this. But that module requires the install of devel module. Which we don't do on Pantheon. The ideal solution is to clone that stand-alone drush command into Pantheon, since it is primarily an issue on Pantheon. Then we can easily fix this problem during the CI build
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Add a custom drush command on all my projects that work on Pantheon. Which is what I'm doing now. But we can do better then that.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: