I am able to reproduce the problem, it does simply cause some of the tasks to be relaunched due to a collision between the initialisation of the mappers which install the content of the pear packages to the same location. The output should be fine though and it won't affect the processing of the documents (once the task is re-ran).
I've just committed a change to the uima module which should address the issue. The PEAR package is now unpacked in a unique location for every mapper. This could be optimized by reusing an existing unpacked location but would required locking etc... suggestions and patches welcome!
Read full article from UIMA PEAR file error - Google Groups
No comments:
Post a Comment