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

Eliminate construction over readers for Tokenizer

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0, 6.0
    • Component/s: core/other
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      In the modern world, Tokenizers are intended to be reusable, with input supplied via #setReader. The constructors that take Reader are a vestige. Worse yet, they invite people to make mistakes in handling the reader that tangle them up with the state machine in Tokenizer. The sensible thing is to eliminate these ctors, and force setReader usage.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bmargulies Benson Margulies

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment