I have a scenario where the same SOLR document is being updated several times within a few ms of each other due to how the source system is sending in field updates on the document.
The problem I am trying to solve is that the order of these updates isn’t guaranteed once the multi threaded SOLRJ client starts sending them to SOLR, and older updates are overlaying the newer updates on the same document. I would like to use a timestamp versioning so that the older document change won’t be sent into SOLR, but I didn’t see any automated way of doing this based on the document timestamp. Is there a good way to handle this scenario in SOLR 4.6? It seems that we would have to be soft auto committing with a subsecond level as well, is that even possible? Thanks, Chris
