Log problematic records id instead of throwing exceptions in search:populate task
|Assignee:||José Raddaoui Marín||% Done:|
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:|
#2 Updated by José Raddaoui Marín over 5 years ago
- Status changed from In progress to QA/Review
- Assignee changed from José Raddaoui Marín to Dan Gillean
- Priority changed from High to Medium
Merged in qa/2.4.x
Now, the "Couldn't find information object (id: $id)" exceptions should be logged at the end of the process, without breaking the search index (only those records and their descendants won't be added). It will be the same for all types of records (actors, terms, etc.)
#4 Updated by José Raddaoui Marín over 5 years ago
Hi Dan, if you have access to the database you could do the following ...
Connect to MySQL:
mysql -hlocalhost -uroot -p
Select the "AtoM" database:
Find some IO ids:
SELECT id FROM information_object;
Delete the publication status for some of those ids (change the ids):
DELETE FROM status WHERE object_id IN (91384, 91387, 91523);
Delete the slug for some of those IOs (change the ids):
DELETE FROM slug WHERE object_id IN (82328, 87113, 82489);
Then try to populate the search index.
#5 Updated by Dan Gillean about 5 years ago
- File cli-search-pop-errors-output.png added
- Status changed from QA/Review to Feedback
- Assignee changed from Dan Gillean to José Raddaoui Marín
the text output says: "Please, contact with an administrator."
It shouldn't have the "with." Should read: Please, contact an administrator.
This is minor, however!