There's no easy way to determine which rows have been skipped - but you can either re-run the delta index again for that model:
User.index_delta Or, if you want to index everything for that model, you can do this like so: indexer --config config/production.sphinx.conf --rotate user_core user_delta Cheers -- Pat On 18/02/2012, at 6:23 PM, Krishnaprasad Varma wrote: > Hi > > I have a user table which is indexed with delayed jobs. Everything is > working quite well . > Sometimes when the delayed jobs server goes down, the delta index > creation fails . hence there exists a mis match between the counts as > explained below > > User.count = 1002 > User.search.total_entries = 820 > > The remaining 180 has to be re processed to create the delta indexes . > > I Tried rebuilding the indexes . But I have other models as well and > rebuilding can be done only together which takes more than a hour as i > have millions of data in one of the models . > > How can i tackle this situation . > > Is there any way to index a particular model ? that to without > stopping the searchd daemon ? > Is there any way to check weather all the items in the table has been > indexed ? if not what are the rows which has been skipped ? > > Thank you > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/thinking-sphinx?hl=en. > -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
