I can't reproduce reliably, so I'm suspecting there are issues in our code.
I'm refactoring to avoid the problem entirely.
Thanks for the response though Erick.
Greg
On 8 September 2010 21:51, Greg Pendlebury wrote:
> Thanks,
>
> I'll create a deliberate test tomorrow feed some random data thro
Thanks,
I'll create a deliberate test tomorrow feed some random data through it
several times to see what happens.
I'm also working on simply improving the buffer to handle the situation
internally, but a few hours of testing isn't a big deal.
Ta,
Greg
On 8 September 2010 21:41, Erick Erickson
This would be surprising behavior, if you can reliably reproduce this
it's worth a JIRA.
But (and I'm stretching a bit here) are you sure you're committing at the
end of the batch AND are you sure you're looking after the commit? Here's
the scenario: Your updated document is a position 1 and 100 i
Does anyone know with certainty how (or even if) order is evaluated when
updates are performed by batch?
Our application internally buffers solr documents for speed of ingest before
sending them to the server in chunks. The XML documents sent to the solr
server contain all documents in the order t
