You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2019/08/06 09:22:00 UTC
[jira] [Commented] (OAK-7251) BinaryTextExtractor should not ignore
parse exception - they should at least be logged at DEBUG in all cases
[ https://issues.apache.org/jira/browse/OAK-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900811#comment-16900811 ]
Vikas Saurabh commented on OAK-7251:
------------------------------------
Backported to 1.8 branch at [r1864480|https://svn.apache.org/r1864480].
> BinaryTextExtractor should not ignore parse exception - they should at least be logged at DEBUG in all cases
> ------------------------------------------------------------------------------------------------------------
>
> Key: OAK-7251
> URL: https://issues.apache.org/jira/browse/OAK-7251
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Major
> Fix For: 1.9.0, 1.10.0
>
>
> BinaryTextExtractor ignores missing library error like:
> {noformat}
> } catch (LinkageError e) {
> // Capture and ignore errors caused by extraction libraries
> // not being present. This is equivalent to disabling
> // selected media types in configuration, so we can simply
> // ignore these errors.
> {noformat}
> or
> {noformat}
> // Capture and report any other full text extraction problems.
> // The special STOP exception is used for normal termination.
> if (!handler.isWriteLimitReached(t)) {
> {noformat}
> We should at not skip these errors - some information should at least be available at DEBUG.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)