Yep, I was thinking of this on a <uniqueKey> field. I was assuming that there was a PK in the database that you were mapping to the uniqueKey field, but if that's not so then it's more of a problem.
But you'd have problems anyway if you *don't* have a uniqueKey when it comes time to update any records, so it might be worth going back around and putting one in... Erick On Wed, Sep 29, 2010 at 10:40 AM, dshvadskiy <dshvads...@gmail.com> wrote: > > Using TermComponent is an interesting suggestion. However my understanding > it > will work only for unique terms. For example compare database primary key > with Solr id field. A variation of that is to calculate some kind of > unique > record hash and store it in the index.Then retrieve id and hash via > TermComponent and compare them with hash calculated on database record. > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Best-way-to-check-Solr-index-for-completeness-tp1598626p1602597.html > Sent from the Solr - User mailing list archive at Nabble.com. >
