Bug #2635
Fixes needed for resuming ingestion(overwrite etc) after instance comes back up
Description
Noticed on Sep 29th that Book with index name pytorch-python-api-ks23sep22 was stuck at id 2531 on Dev.
Debugging showed that resumption logic has bugs.
Updated by Ayush Khandelwal about 2 years ago
- Due date set to 09/30/2022
- Status changed from New to In Progress
- Estimated time set to 3.00 h
Updated by Ayush Khandelwal about 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Updated by Ayush Khandelwal about 2 years ago
- Due date changed from 09/30/2022 to 10/03/2022
- Status changed from Resolved to Reopened
- % Done changed from 100 to 50
Updated by Ayush Khandelwal about 2 years ago
Bug:
Scenario:
If the book has 6 documents.
Move the documents to tempContent
All the 6 documents are saved to tempContent and tempContentSupplement. Now, the lastAddedDocumentId will be <documentProcessingId>-6.
Move the documents to content
In the moveTempContentDataToDSAndES() method, it will get lastAddedDocumentId as <documentProcessingId>-6. This lastAddedDocumentId is 6 because it is last updated to tempContent and not the content.
then List<tempDocumentKeys>(sorted in descending order) will be processed 1 by 1. Here, the tempDocument will be <documentProcessingId>-6.
As both lastAddedDocumentId and tempDocument Id is equal, it will not save/update that document to content kind
Updated by Ayush Khandelwal about 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Updated by Ayush Khandelwal about 2 years ago
- Status changed from Resolved to Feedback
Working as expected on QA
Updated by Ayush Khandelwal about 2 years ago
- Assignee changed from Ayush Khandelwal to Ram Kordale