You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Santiago M. Mola (JIRA)" <ji...@apache.org> on 2010/07/29 14:52:16 UTC

[jira] Updated: (LUCENE-2577) SpanNearQuery inconsistency: should it accept less than 2 clauses or not?

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

Santiago M. Mola updated LUCENE-2577:
-------------------------------------

    Priority: Minor  (was: Major)

> SpanNearQuery inconsistency: should it accept less than 2 clauses or not?
> -------------------------------------------------------------------------
>
>                 Key: LUCENE-2577
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2577
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 3.0.2
>            Reporter: Santiago M. Mola
>            Priority: Minor
>
> NearSpansOrdered's constructor will throw an IllegalArgumentException
> if less than 2 clauses are given, while NearSpansOrdered won't.
> On the other hand, SpanNearQuery accepts less than 2 clauses and has explicit optimization for 0-caluse and 1-clause queries in getSpans() method.
> So, should SpanNearQuery accept less than 2 clauses or not?

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