On Tue, 15 Jul 2008 10:48:14 +0200
Jarek Zgoda <[EMAIL PROTECTED]> wrote:
> >> 2) I don't want to overwrite old content with new one.
> >>
> >> Means, if I add duplicate content in solr and the content already
> >> exists, the old content should not be overwritten.
> >
> > before inserting a new document, query the index - if you get a result back,
> > then don't insert. I don't know of any other way.
>
> This operation is not atomic, so you get a race condition here. Other
> than that, it seems fine. ;)
of course - but i am not sure you can control atomicity at the SOLR level
(yet? ;) ) for /update handler - so it'd have to either be a custom handler, or
your app being the only one accessing and controlling write access to it that
way. It definitely gets more interesting if you start adding shards ;)
_________________________
{Beto|Norberto|Numard} Meijome
"All parts should go together without forcing. You must remember that the parts
you are reassembling were disassembled by you. Therefore, if you can't get them
together again, there must be a reason. By all means, do not use hammer." IBM
maintenance manual, 1975
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
