You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Digy (JIRA)" <ji...@apache.org> on 2008/11/15 01:00:44 UTC
[jira] Closed: (LUCENENET-161) RangeQuery
[ https://issues.apache.org/jira/browse/LUCENENET-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy closed LUCENENET-161.
--------------------------
Resolution: Invalid
Assignee: Digy
Not a bug
> RangeQuery
> ----------
>
> Key: LUCENENET-161
> URL: https://issues.apache.org/jira/browse/LUCENENET-161
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Dotnet 2.0
> Reporter: Gaëtan Kesteloot
> Assignee: Digy
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I create à range query on price.
> Datas:
> Document1 => Field name=Price Value=90.01
> Document2 => Field name=Price Value=91.98
> Document3 => Field name=Price Value=105.00
> Document4 => Field name=Price Value=121.00
> Document5 => Field name=Price Value=126.00
> When I create the range Query with name=Price LowerTerm=90.02 UpperTerm=120.00
> The result return no document
> IF i modify data and range Query
> Document1 => Field name=Price Value=090.01
> Document2 => Field name=Price Value=091.98
> Document3 => Field name=Price Value=105.00
> Document4 => Field name=Price Value=121.00
> Document5 => Field name=Price Value=126.00
> When I create the range Query with name=Price LowerTerm=090.02 UpperTerm=120.00
> The result return Document2 and Document3
> Why the range query class cannot accept lowerterm and upperterm with different length
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.