[
https://issues.apache.org/jira/browse/JCR-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010795#comment-13010795
]
Paco Avila commented on JCR-2873:
---------------------------------
Great, I was missing this feature for years! At least, now I can see which
document were not indexed. Is also possible to make a relation between the
document and the text extraction error?
> Add a way to locate full text extraction problems
> -------------------------------------------------
>
> Key: JCR-2873
> URL: https://issues.apache.org/jira/browse/JCR-2873
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: indexing, jackrabbit-core
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.3.0
>
>
> Full text indexing of a binary document can fail for various reasons.
> Currently we just log a generic error message in such cases, which makes it
> difficult for the user to locate such problems for review and reindexing. We
> should improve this by making the logs more informative or by adding some
> other mechanism for locating troublesome documents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
