Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-3017

Allow edismax stopword filter factory implementation to be specified

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 4.0-ALPHA
    • Fix Version/s: 4.0-ALPHA
    • Component/s: None
    • Labels:
      None

      Description

      Currently, the edismax query parser assumes that stopword filtering is being done by StopFilter: the removal of the stop filter is performed by looking for an instance of 'StopFilterFactory' (hard-coded) within the associated field's analysis chain.

      We'd like to be able to use our own stop filters whilst keeping the edismax stopword removal goodness. The supplied patch allows the stopword filter factory class to be supplied as a param, "stopwordFilterClassName". If no value is given, the default (StopFilterFactory) is used.

      Another option I looked into was to extend StopFilterFactory to create our own filter. Unfortunately, StopFilterFactory's 'create' method returns StopFilter, not TokenStream. StopFilter is also final.

        Attachments

        1. edismax_stop_filter_factory.patch
          14 kB
          Michael Dodsworth
        2. SOLR-3017.patch
          11 kB
          Erick Erickson
        3. SOLR-3017.patch
          45 kB
          Michael Dodsworth
        4. SOLR-3017-without-guava-alternative.patch
          45 kB
          Michael Dodsworth

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mdodsworth@salesforce.com Michael Dodsworth
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: