jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1878) Use Apache Tika for text extraction
Date Tue, 07 Apr 2009 15:52:13 GMT

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

Jukka Zitting resolved JCR-1878.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0
         Assignee: Jukka Zitting

Jackrabbit now uses Apache Tika (version 0.3) as the default text extractor.

All the previous text extractor classes still exist, so any existing configurations should
still work as before.

> Use Apache Tika for text extraction
> -----------------------------------
>
>                 Key: JCR-1878
>                 URL: https://issues.apache.org/jira/browse/JCR-1878
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-text-extractors
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 1.6.0
>
>
> Once Apache Tika is released with a resolution to TIKA-175 (making Tika available to
Java 1.4 projects), we should replace our direct parser library dependencies with Tika parsers.
Ideally we'd just use the Tika AutoDetectParser that'll automatically detect the type of a
binary and parse it accordingly, solving JCR-728.
> I guess we should keep some level of backwards compatibility with existing textFilterClasses="..."
configurations, perhaps by keeping the existing TextExtractor classes as wrappers around respective
Tika parsers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message