You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2006/12/20 16:30:21 UTC

[jira] Resolved: (JCR-415) Enhance indexing of binary content

     [ http://issues.apache.org/jira/browse/JCR-415?page=all ]

Marcel Reutegger resolved JCR-415.
----------------------------------

    Fix Version/s: 1.3
       Resolution: Fixed

In addition to the previously mentioned steps I also implemented the deferred text extraction as discussed with Jukka in this jira issue. The helper class TextExtractorReader has been removed again.

Fixed in revision: 489112

If noone objects within a week I will remove the now obsolete module jackrabbit-index-filters.

> Enhance indexing of binary content
> ----------------------------------
>
>                 Key: JCR-415
>                 URL: http://issues.apache.org/jira/browse/JCR-415
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: indexing
>    Affects Versions: 1.0, 1.0.1, 0.9
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: jackrabbit-extractor-r420472.patch, jackrabbit-query-r420472.patch, jackrabbit-query-r421461.patch, org.apache.jackrabbit.core.query-extractor.jpg, org.apache.jackrabbit.core.query.lucene-extractor.jpg, org.apache.jackrabbit.extractor.jpg
>
>
> Indexing of binary content should be enhanced in order to allow either configuration what fields are indexed or provide better support for custom NodeIndexer implementations.
> The current design has a couple of flaws that should be addressed at the same time:
> - Reader instances are requested from the text filters even though the reader might never be used
> - only jcr:data properties of nt:resource nodes are fulltext indexed
> - It is up to the text filter implementation to decide the lucene field name for the text representation, responsibility should be moved to the NodeIndexer. A text filter should only provide a Reader instance.
> With those changes a custom NodeIndexer can then decide if a binary property has one or more representations in the index.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira