FieldIndex：unindex_object 无法删除 documentId
我们在 Plone 3.3 日志中似乎出现随机错误：
78：错误 Zope.UnIndex FieldIndex：unindex_object 无法从索引 getCompleteness 中删除 documentId 513478895。这不应该发生。
getCompleteness 是来自 Archetypes 访问器方法的自定义索引。
这个错误是什么意思？
是否应该采取行动，例如添加一些特殊的自定义附加组件？
We are seeming random errors in Plone 3.3 logs:
78: ERROR Zope.UnIndex FieldIndex: unindex_object could not remove documentId 513478895 from index getCompleteness. This should not happen.
getCompleteness is our custom index coming from an Archetypes accessor method.
What does this error mean?
Should there be action taken e.g. by adding some special to custom add-ons?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这意味着您的 Portal_catalog（特别是一个或多个索引）不一致。 Portal_catalog 不一致的原因有多种。要么是由于索引实现中的问题，要么是由于应用程序代码中的错误。在这种情况下，您应该尝试从 ZMI 中“清除并重建”。
It means that your portal_catalog - in particular one or more indexes - are inconsistent. There are various reasons why the portal_catalog can be become inconsistent. Either through issues in the index implementation or through errors in the application code. In such a case you should try "Clear and Rebuild" from the ZMI.
这说明你的目录不一致；它认为它具有一个文档的索引信息，并且在取消索引时它无法再找到相同的信息。
出现此错误后，您的目录实际上不再那么不一致，因为文档的索引不再不一致。从这方面来说，目录是相当有弹性的。
如果您更频繁地看到该错误，则需要验证您的自定义索引是否正确处理索引和取消索引，因为它的内部数据结构更频繁地不同步。
It means that your catalog was inconsistent; it thought it had indexing information for one document, and on un-index it couldn't find that same information anymore.
After this error, your catalog is actually a little less inconsistent as the document is no longer inconsistently indexed. The catalog is quite resilient in that way.
If you see the error more often, you'll need to verify that your custom index is taking care of indexing and unindexing properly, as it's internal data structures are getting out of sync more often.