sigram opened a new issue, #95:
URL: https://github.com/apache/solr-sandbox/issues/95
Requests picked up from the incoming Kafka queue are processed in
`KafkaCrossDcConsumer.pollAndProcessRequests`. In case of UPDATE requests
before they are sent to the target Solr they are first "collapsed", i.e. data
from multiple update requests is appended to a single outgoing UpdateRequest,
as long as other request parameters match the first request.
However, this must lead to reordering of updates, because Solr always
processes all "add" ops first when processing an UpdateRequest. The original
ordering of incoming ops is lost in the single collapsed outgoing request.
Imagine the following scenario:
* Input:
* add(A), add(B)
* del(A)
* add(A') // modified A with the same id
End result: A', B
* Collapsed output:
* add(A), add(B), add(A')
* del(A)
End result: B
Perhaps in some environments this is very unlikely to happen but cannot be
assumed to work in general. I propose to add an option to turn it off, set to
OFF by default.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
