jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-7251) BinaryTextExtractor should not ignore parse exception - they should at least be logged at DEBUG in all cases
Date Fri, 09 Feb 2018 16:07:00 GMT

     [ https://issues.apache.org/jira/browse/OAK-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vikas Saurabh resolved OAK-7251.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Done in trunk at [r1823671|https://svn.apache.org/r1823671].

> 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
>
>
> 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.3#76005)

Mime
View raw message