Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: None
-
Component/s: contrib - DataImportHandler
-
Labels:None
Description
If the EntityProcessor of a subentity throws an Exception in its init() Method, DocBuilder logs "Import completed successfully" and calls commit instead of calling rollback.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Thanks for the test Frank. There are more problems. In single thread mode, an error causes a rollback but in threaded mode, a commit is called.
I was looking at this problem again today. The onError attributes are not used to deal with exceptions from EntityProcessor.init() method. They are only used for reading rows, applying transformers and inserting documents into Solr.
The real problem was that in multi-threaded mode, the exceptions from EntityProcessor.init were being eaten up so a commit was called instead of rolling back the changes. I've fixed that to re-throw the exception up the hierarchy.
Fixed a bug in the tests. The index was not being emptied in tearDown so even after rollback, the index had 4 documents.
Just to show that multi-threaded does honor the onError attribute, I've added a test which uses a transformer which always fails.
The older two tests are used to demonstrate that both multi-threaded and serial mode show the same characteristic for a failing entity processor.
Committed revision 1161505 on trunk and 1161510 on branch_3x.
patch for the unittest to clarify the problem