Summary: | Invalid record in sample data leading to error when displaying | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | caroline.cyr-la-rose, jonathan.druart |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Victor Grousset/tuxayo
2021-05-11 23:12:06 UTC
Hi Joubu, can you tell if the record is there for a purpose? Maybe the unit tests? I keep stumbling on it too when I need to reindex Elasticsearch. Yes, 369 is known to be buggy. I think we should keep it. Is there a more elegant way then deleting it by SQL when you need to reindex? (In reply to Katrin Fischer from comment #3) > Is there a more elegant way then deleting it by SQL when you need to reindex? IIRC bad records are skipped, it should not prevent other records to be indexed. (In reply to Jonathan Druart from comment #4) > (In reply to Katrin Fischer from comment #3) > > Is there a more elegant way then deleting it by SQL when you need to reindex? > > IIRC bad records are skipped, it should not prevent other records to be > indexed. You are right - I had issues there in the past, but testing it just now it seems to work ok. |