On Fri, Feb 24, 2012 at 12:06 PM, Per Steffensen <st...@designware.dk> wrote: > Sami Siren skrev: > >>>> Given that you've set a uniqueKey-field and there already exists a >>>> document with that uniqueKey, it will delete the old one and insert the >>>> new one. There is really no difference between the semantics - updates >>>> do not exist. >>>> To create a UNIQUE-constraint as you know it from a database you have to >>>> check whether a document is already in the index *or* whether it is >>>> already pending (waiting for getting flushed to the index). >>>> Fortunately Solr manages a so called pending-set with all those >>>> documents waiting for beeing flushed to disk (Solr 3.5). >>>> >>>> >>> >>> We are using latest greates 4.0-SNAPSHOT code, because we want to take >>> advantage of SolrCloud stuff. Can you give a code-pointer to where I can >>> find the pending-set stuff? >>> >> >> >> I am not sure if this is what you're asking but you should be able to >> get the latest data from Solr by using >> realtime get http://wiki.apache.org/solr/RealTimeGet >> > > Thanks a lot! I might be very usefull, if this provide 100% real time get - > that is, if it gets the latest version of the document, also when neither a > soft-commit nor a hard-commit has been performed since the lastest version > of the document was indexed. Does it do that, or does it need a soft commit > (then I believe it is only a near real time get operation)?
I believe it does not require any kind of commit to happen so it should really be a real time get as the name suggests. -- Sami Siren
