Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.9, 1.0, 1.0.1
    • Fix Version/s: 1.3
    • Component/s: indexing
    • Labels:
      None

      Description

      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.

        Attachments

        1. org.apache.jackrabbit.extractor.jpg
          46 kB
          Jukka Zitting
        2. org.apache.jackrabbit.core.query-extractor.jpg
          23 kB
          Jukka Zitting
        3. org.apache.jackrabbit.core.query.lucene-extractor.jpg
          64 kB
          Jukka Zitting
        4. jackrabbit-query-r421461.patch
          40 kB
          Jukka Zitting
        5. jackrabbit-query-r420472.patch
          36 kB
          Jukka Zitting
        6. jackrabbit-extractor-r420472.patch
          46 kB
          Jukka Zitting

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mreutegg Marcel Reutegger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: