[ZCM] [ZC] 840/ 3 Resolve "Make Update Catalog resistant to failures"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #840 Update (Resolve) "Make Update Catalog resistant to failures"
 Status Resolved, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/840

==============================================================
= Resolve - Entry #3 by ajung on May 16, 2004 6:47 am

 Status: Accepted => Resolved

The functionality is now more fail-safe. Every reindexed
documented is being logged and exceptions will be caught and logged as well.

Changes are on the SVN trunk and 2.7 branch (appears in 2.7.1)
________________________________________
= Assign - Entry #2 by ajung on May 13, 2004 1:19 pm

 Status: Pending => Accepted

 Supporters added: ajung

I have this on my todo list for the near future
________________________________________
= Request - Entry #1 by bjorn on Mar 6, 2003 9:39 pm

In sites with lots of content "ZCatalog -> Advanced -> Update Catalog" will fail for one or more content.  As far as I can tell, this makes the entire update fail to commit.

Even worse, there is no mention in the error logs about which document it failed on and which method it failed on!  This makes it really hard and time-consuming to track down indexing problems.

I suggest that the "Update Catalog" gets an option (or make the default be) to capture errors, but continue indexing.  The errors that are recorded gets extended with the object id (path) and the method that failed (e.g., SearchableText).
==============================================================