Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-4369

StringFields name is unintuitive and not helpful

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • New

    Description

      There's a huge difference between TextField and StringField, StringField screws up scoring and bypasses your Analyzer.

      (see java-user thread "Custom Analyzer Not Called When Indexing" as an example.)

      The name we use here is vital, otherwise people will get bad results.

      I think we should rename StringField to MatchOnlyField.

      Attachments

        1. LUCENE-4369.patch
          175 kB
          Robert Muir

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. LUCENE-1366 Rename Field.Index.UN_TOKENIZED/TOKENIZED/NO_NORMS

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          supercedes

          Task - A task that needs to be done. LUCENE-3792 Remove StringField

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              rcmuir Robert Muir
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: