-
Notifications
You must be signed in to change notification settings - Fork 493
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
Indexing: Create API endpoint(s) that allows an admin to detect/delete stale solr record #4225
Labels
Comments
djbrooke
changed the title
Indexing: Create an API endpoint that allows an admin to delete a stale solr record.
Indexing: Create an API endpoint that allows an admin to detect/delete stale solr record
Feb 26, 2020
djbrooke
changed the title
Indexing: Create an API endpoint that allows an admin to detect/delete stale solr record
Indexing: Create API endpoint(s) that allows an admin to detect/delete stale solr record
Feb 26, 2020
See #4205 for some very detailed discussion. |
ekraffmiller
added a commit
that referenced
this issue
Aug 19, 2020
database, and in Solr. Added a new API method for clearing all orphans. (#4225)
ekraffmiller
added a commit
that referenced
this issue
Sep 8, 2020
ekraffmiller
added a commit
that referenced
this issue
Sep 8, 2020
ekraffmiller
added a commit
that referenced
this issue
Sep 8, 2020
with rest of the status message (#4225)
ekraffmiller
added a commit
that referenced
this issue
Sep 8, 2020
ekraffmiller
added a commit
that referenced
this issue
Sep 10, 2020
ekraffmiller
added a commit
that referenced
this issue
Sep 10, 2020
pdurbin
added a commit
that referenced
this issue
Sep 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Although probably rare, see #4205, there may be orphaned solr records that need to be removed outside of Dataverse, directly from the Solr API. It would be more convenient if an admin could use the familiar Dataverse API to pass the identifier of a stale dataset record to be removed.
The text was updated successfully, but these errors were encountered: