[ 
https://issues.apache.org/jira/browse/SOLR-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alessandro Benedetti updated SOLR-13663:
----------------------------------------
    Description: 
Currently the XML Query Parser support a vast array of span queries, including 
the SpanFirstQuery, but it doesn't support the generic SpanPositionRangeQuery.

< SpanPositionRange start="2" end="3">
 <SpanTerm fieldName="title">prejudice</SpanTerm>
 </ SpanPositionRange>

 

Scope of this issue is to introduce the related builder and allow the 
possibility to build such queries.

 

  was:
Currently the XML Query Parser support a vast array of span queries, including 
the SpanFirstQuery, but it doesn't support the generic SpanPositionRangeQuery.

< SpanPositionRange start="2" end="3">
 <SpanTerm fieldName="title">prejudice</SpanTerm>
 </ SpanPositionRange>


> XML Query Parser to Support SpanPositionRangeQuery
> --------------------------------------------------
>
>                 Key: SOLR-13663
>                 URL: https://issues.apache.org/jira/browse/SOLR-13663
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: query parsers
>    Affects Versions: 8.2
>            Reporter: Alessandro Benedetti
>            Priority: Major
>         Attachments: SOLR-13663.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently the XML Query Parser support a vast array of span queries, 
> including the SpanFirstQuery, but it doesn't support the generic 
> SpanPositionRangeQuery.
> < SpanPositionRange start="2" end="3">
>  <SpanTerm fieldName="title">prejudice</SpanTerm>
>  </ SpanPositionRange>
>  
> Scope of this issue is to introduce the related builder and allow the 
> possibility to build such queries.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to