lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luis Alves (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1823) QueryParser with new features for Lucene 3
Date Wed, 19 Aug 2009 00:02:14 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744790#action_12744790
] 

Luis Alves commented on LUCENE-1823:
------------------------------------

{quote}
2 Opaque terms
{quote}

I propose the following examples for the syntax

{code}
syntax1:
+a -b ::complexPhrase('other syntax') xml('/bookstore/book[price>35.00]') googlesyntax('2..20
doughnuts')

syntax2:
+a -b complexPhrase::'other syntax' xml::'/bookstore/book[price>35.00]' googlesyntax::'2..20
doughnuts'

syntax3:
+a -b complePhrase:'other syntax' xml:'/bookstore/book[price>35.00]' googlesyntax:'2..20
doughnuts'
{code}

We can also have a default SyntaxExtension to make the syntax easier, for example if complexPhrase
was the default Syntax Extension,
the queries above could be written like this:

{code}
syntax1:
+a -b ::('other syntax') ::xml('/bookstore/book[price>35.00]') ::googlesyntax('2..20 doughnuts')
syntax2:
+a -b ::'other syntax' xml::'/bookstore/book[price>35.00]' googlesyntax::'2..20 doughnuts'
syntax3:
+a -b 'other syntax' xml:'/bookstore/book[price>35.00]' googlesyntax:'2..20 doughnuts'
{code}

I would like to call it Query Parser Syntax extensions instead of Opaque Terms.

+ 1 for syntax 1



> QueryParser with new features for Lucene 3
> ------------------------------------------
>
>                 Key: LUCENE-1823
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1823
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: QueryParser
>            Reporter: Michael Busch
>            Assignee: Michael Busch
>            Priority: Minor
>             Fix For: 3.1
>
>
> I'd like to have a new QueryParser implementation in Lucene 3.1, ideally based on the
new QP framework in contrib. It should share as much code as possible with the current StandardQueryParser
implementation for easy maintainability.
> Wish list (feel free to extend):
> 1. *Operator precedence*: Support operator precedence for boolean operators
> 2. *Opaque terms*: Ability to plugin an external parser for certain syntax extensions,
e.g. XML query terms
> 3. *Improved RangeQuery syntax*: Use more intuitive <=, =, >= instead of [] and
{}
> 4. *Support for trierange queries*: See LUCENE-1768
> 5. *Complex phrases*: See LUCENE-1486
> 6. *ANY operator*: E.g. (a b c d) ANY 3 should match if 3 of the 4 terms occur in the
same document
> 7. *New syntax for Span queries*: I think the surround parser supports this?
> 8. *Escaped wildcards*: See LUCENE-588

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message