On Tue, Dec 29, 2009 at 3:03 AM, Mohamed Parvez <par...@gmail.com> wrote:
> I have looked in the that thread earlier. But there is no option there for > a > solution from Solr side. > > I mean the two more options there are > 1] Use database triggers instead of DIH to manage updating the index :- > This out of question as we cant run 1000 odd triggers every hour to delete. > > 2] Some sort of ORM use its interception:- > This is also out of question as the deletes happens form external system or > directly on the database, not through our application. > > > To Say in Short, Solr Should have something thing to keep the index synced > with the database. As of now its one way street, updates rows, on DB will > go > to the index. Deleted rows in the DB, will not be deleted from the Index > > How can Solr figure out what has been deleted? Should it go through each row and comparing against each doc? Even then some things are not possible (think indexed fields). It would be far efficient to just do a full-import each time instead. -- Regards, Shalin Shekhar Mangar.
