Lucene - Core
  1. Lucene - Core
  2. LUCENE-2604 add regexpquery to queryparser
  3. LUCENE-3982

regex support in queryparser needs documented, and called out in CHANGES.txt

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA
    • Component/s: core/queryparser
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Spun off of LUCENE-2604 where everyone agreed this needed done, but no one has done it yet, and rmuir didn't want to leave the issue open...

      some issues were pointed out in a recent mailing list thread that definitely seem like they should be addressed before this is officially released...

      • queryparsersyntax.xml doesn't mention this feature at all – as major new syntax is should really get it's own section with an example showing the syntax
      • queryparsersyntax.xml's section on "Escaping Special Characters" needs to mention that '/' is a special character

      Also: Given that Yury encountered some real world situations in which the new syntax caused problems with existing queries, it seems like we should definitely make a note about this possibility more promonient ... i'm not sure if it makes sense in MIGRATE.txt but at a minimum it seems like the existing CHANGES.txt entry should mention it, maybe something like...

      * LUCENE-2604: Added RegexpQuery support to QueryParser. Regular expressions
        are now directly supported by the standard queryparser using the syntax... 
           fieldName:/expression/ OR /expression against default field/
        Users who wish to search for literal "/" characters are advised to 
        backslash-escape or quote those characters as needed. 
        (Simon Willnauer, Robert Muir)
      

        Activity

        Hide
        Robert Muir added a comment -

        thanks Hoss

        Show
        Robert Muir added a comment - thanks Hoss
        Hide
        Hoss Man added a comment -

        Not: set to blocker so we don't release 4.0 with this change in syntax w/o documenting

        Show
        Hoss Man added a comment - Not: set to blocker so we don't release 4.0 with this change in syntax w/o documenting

          People

          • Assignee:
            Unassigned
            Reporter:
            Hoss Man
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development