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

stopword filter config error in sample schema

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4
    • Component/s: None
    • Labels:
      None

      Description

      The sample schema enables position increments for the StopFilter for the index analyzer but not the query analyzer.
      introduced back in SOLR-521

      1. SOLR-879.patch
        2 kB
        Yonik Seeley

        Activity

        Hide
        gsingers Grant Ingersoll added a comment -

        Bulk close for Solr 1.4

        Show
        gsingers Grant Ingersoll added a comment - Bulk close for Solr 1.4
        Hide
        yseeley@gmail.com Yonik Seeley added a comment -

        committed.

        Show
        yseeley@gmail.com Yonik Seeley added a comment - committed.
        Hide
        yseeley@gmail.com Yonik Seeley added a comment -

        Here's a patch that changes the default for the parser and fixes the example config.
        We may need to fix other example configs.

        Q: is this really the default we want in the example config?
        "Optimized <stopword> High Volume Web Traffic" will match
        "Optimized High Volume Web Traffic" will not match.

        Show
        yseeley@gmail.com Yonik Seeley added a comment - Here's a patch that changes the default for the parser and fixes the example config. We may need to fix other example configs. Q: is this really the default we want in the example config? "Optimized <stopword> High Volume Web Traffic" will match "Optimized High Volume Web Traffic" will not match.
        Hide
        yseeley@gmail.com Yonik Seeley added a comment -

        The other problem is we never set QueryParser.setEnablePositionIncrements(true)
        This means that the indexed version will have gaps but the phrase query produced will not.

        You can see the problem with this query on the example data:
        http://localhost:8983/solr/select?q=features:%22Optimized%20High%20Volume%20Web%20Traffic%22

        Show
        yseeley@gmail.com Yonik Seeley added a comment - The other problem is we never set QueryParser.setEnablePositionIncrements(true) This means that the indexed version will have gaps but the phrase query produced will not. You can see the problem with this query on the example data: http://localhost:8983/solr/select?q=features:%22Optimized%20High%20Volume%20Web%20Traffic%22

          People

          • Assignee:
            Unassigned
            Reporter:
            yseeley@gmail.com Yonik Seeley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development