lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shalin Shekhar Mangar <shalinman...@gmail.com>
Subject Re: How to handle multiple sub second updates to same SOLR Document
Date Sun, 26 Jan 2014 05:13:56 GMT
There is no timestamp versioning as such in Solr but there is a new
document based versioning which will allow you to specify your own
(externally assigned) versions.

See the "Document Centric Versioning Constraints" section at
https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents

Sub-second soft auto commit can be expensive but it is hard to say if
it will be too expensive for your use-case. You must benchmark it
yourself.

On Sat, Jan 25, 2014 at 11:51 PM, christopher palm <cpalm3@gmail.com> wrote:
> 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



-- 
Regards,
Shalin Shekhar Mangar.

Mime
View raw message