jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1878) Use Apache Tika for text extraction
Date Thu, 16 Apr 2009 10:41:15 GMT

    [ https://issues.apache.org/jira/browse/JCR-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699630#action_12699630
] 

Marcel Reutegger commented on JCR-1878:
---------------------------------------

I don't feel that comfortable with the new dependencies that were added with this change.
More specifically the size of icu4j and ooxml-schemas. The first is about 4MB and the latter
13MB (!). Comparing the size of jackrabbit-standalone in 1.5 with current trunk shows that
it doubled from 20 to over 40 MB.

What do others think about this?

> 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