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

Steve Rowe edited comment on LUCENE-7932 at 8/21/17 1:33 PM:
-------------------------------------------------------------

bq. Do you still suggest me to use: 
http://lucene.apache.org/core/discussion.html

Yes.  You should always start there, and if you don't get a response in a day 
or two, or if someone requests you to do so, only then create a JIRA issue.

It's still the case that you haven't provided enough information.  You haven't 
provided any code, and you haven't shown what your actual queries are.  Are you 
using Lucene directly, or are you using some other project that depends on 
Lucene?


was (Author: steve_rowe):
bq. Do you still suggest me to use: 
http://lucene.apache.org/core/discussion.html

Yes.  You should always start there, and if you don't get a response, or if 
someone requests you to do so, only then create a JIRA issue.

It's still the case that you haven't provided enough information.  You haven't 
provided any code, and you haven't shown what your actual queries are.  Are you 
using Lucene directly, or are you using some other project that depends on 
Lucene?

> Search record with field value='a' or 'A' returns all records along with one 
> more field value
> ---------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-7932
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7932
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 5.3, 6.6
>         Environment: Windows and Linux
>            Reporter: Rohit Balekundri
>              Labels: features
>
> Hi Lucene Team,
> I would like to explain more on about issue facing after querying using 
> QueryParser API.
> Here I am just giving examples of our project with field names (Not related 
> with Lucene):
> In our document which needs to be archived having key fields and non-key 
> fields.
> A> Key fields: 
> 1. LocationCode (DataType=long)
> 2. CollectionObjectID (DataType=long)
> B> Non-key fields
> Category (DataType=string)
> Steps we followed:
> 1. Step 1: We stored multiple document records with category values as below 
> in index files.
>      LocationCode = 1  Category =b
>      LocationCode = 2  Category =BC
>      LocationCode =3  Category =bcd
> 2. In Step 2: we query for records and we pass query parameters as below.
>     a) LocationCode=1 and  Category =a  
>          Result= all records displayed
>     b) LocationCode=1 and  Category =A  result= all records displayed
>          Result= all records displayed
> I faced above issue in Lucene 5.3.
> Llater I found even Lucene 6.6 is also having same issue.
> Kindly consider this bug on top priority.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to