Fix baloo_file_extractor being destroyed while commiting
Review Request #124836 - Created Aug. 20, 2015 and submitted
Since we emit the filenames before we start indexing them, for diagnostic reasons, simply counting the number of files written to stdout is not enough we need to make sure baloo_file_extractor has commited before it is destroyed (when indexing the last batch or suspending it). So now we wait for baloo_file_extractor to write "batch commited" to stdout before the ExtractorProcess emits done.
Occasionally, baloo was not being able to resume from suspended state after my previous patch which was most likely because we were killing baloo_file_extractor while committing, messing up the index. This seeems to be fixed now.
This makes sense. But perhaps you want to move to a better way instead of just counting lines. Maybe some kind of specification on what should be sent/received. The extractor could always send some kind of message when it started indexing and finished indexing each file.