But how do you know when the document actually makes it to solr, especially if you are using commitWithin and not explicitly calling commit.
One solution is to have a status field in the database such as 0 - unindexed 1 - indexing 2 - committed / verified And have a separate process query solr for documents in the indexing state and set them to committed if they are queryable in solr. On Tue, Sep 7, 2010 at 14:26, Geert-Jan Brits <gbr...@gmail.com> wrote: >>Please let me know if there are any other ideas / suggestions to implement > this. > > You're indexing program should really take care of this IMHO. Each time your > indexer inserts a document to Solr, flag the corresponding entity in your > RDBMS, each time you delete, remove the flag. You should implement this as a > transaction to make sure all is still fine in the unlikely event of a crash > midway. > > 2010/9/7 bbarani <bbar...@gmail.com> > >> >> Hi, >> >> I am trying to get complete list of unique document ID and compare it with >> that of back end to make sure that both back end and SOLR documents are in >> sync. >> >> Is there a way to fetch the complete list of data from a particular column >> in SOLR document? >> >> Once I get the list, I can easily compare it against the DB and delete the >> orphan documents.. >> >> Please let me know if there are any other ideas / suggestions to implement >> this. >> >> Thanks, >> Barani >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Is-there-a-way-to-fetch-the-complete-list-of-data-from-a-particular-column-in-SOLR-document-tp1435586p1435586.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> >
