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

Mark Harwood commented on LUCENE-1486:
--------------------------------------

{quote}
query: '(john OR jonathon) smith~0.3 order*' order:sell "stock market"
{quote}
Would be parsed as follows (shown as equivalent XMLQueryParser syntax)
{code:xml} 
<BooleanQuery>
  <Clause occurs="should">
     <SpanNear >                
                        <SpanOr>
                                <SpanOrTerms>john jonathon </SpanOrTerms>
                        </SpanOr>
                        <SpanOr>
                                <SpanOrTerms> smith smyth</SpanOrTerms>
                        </SpanOr>
                        <SpanOr>
                                <SpanOrTerms> order orders</SpanOrTerms>
                        </SpanOr>
   </SpanNear>
 </Clause>
<Clause occurs="should">
     <TermQuery fieldName="order" >sell</TermQuery>             
 </Clause>
<Clause occurs="should">
     <UserQuery>"stock market"</UserQuery >             
 </Clause>
</BooleanQuery> 
{code}


> Wildcards, ORs etc inside Phrase queries
> ----------------------------------------
>
>                 Key: LUCENE-1486
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1486
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: QueryParser
>    Affects Versions: 2.4
>            Reporter: Mark Harwood
>            Assignee: Mark Harwood
>            Priority: Minor
>             Fix For: 2.9
>
>         Attachments: ComplexPhraseQueryParser.java, 
> junit_complex_phrase_qp_07_21_2009.patch, 
> junit_complex_phrase_qp_07_22_2009.patch, LUCENE-1486.patch, 
> LUCENE-1486.patch, LUCENE-1486.patch, LUCENE-1486.patch, 
> TestComplexPhraseQuery.java
>
>
> An extension to the default QueryParser that overrides the parsing of 
> PhraseQueries to allow more complex syntax e.g. wildcards in phrase queries.
> The implementation feels a little hacky - this is arguably better handled in 
> QueryParser itself. This works as a proof of concept  for much of the query 
> parser syntax. Examples from the Junit test include:
>               checkMatches("\"j*   smyth~\"", "1,2"); //wildcards and fuzzies 
> are OK in phrases
>               checkMatches("\"(jo* -john)  smith\"", "2"); // boolean logic 
> works
>               checkMatches("\"jo*  smith\"~2", "1,2,3"); // position logic 
> works.
>               
>               checkBadQuery("\"jo*  id:1 smith\""); //mixing fields in a 
> phrase is bad
>               checkBadQuery("\"jo* \"smith\" \""); //phrases inside phrases 
> is bad
>               checkBadQuery("\"jo* [sma TO smZ]\" \""); //range queries 
> inside phrases not supported
> Code plus Junit test to follow...

-- 
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to