[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Attachment: LuceneQueryTest.java LUCENE-7932 Search record with field value 'a' or 'A' returns all records along with one more field value.msg Please find attached mail and also test scenarios and queries I used to test scenarios. I am directly accession Lucene code. I am not using any third party tool/software. If any information required please let me know. > 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 > Attachments: LUCENE-7932 Search record with field value 'a' or 'A' > returns all records along with one more field value.msg, LuceneQueryTest.java > > > Hi Lucene Team, > Here I explained more about issue facing after querying using > org.apache.lucene.search.IndexSearcher 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 > I faced above issue in Lucene 5.3. > Later I found even Lucene 6.6 is also having same issue. -- 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Description: Hi Lucene Team, Here I explained more about issue facing after querying using org.apache.lucene.search.IndexSearcher 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 I faced above issue in Lucene 5.3. Later I found even Lucene 6.6 is also having same issue. was: Hi Lucene Team, Here I explained more 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. > 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, > Here I explained more about issue facing after querying using > org.apache.lucene.search.IndexSearcher 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 > I faced above issue in Lucene 5.3. > Later I found even Lucene 6.6 is also having same issue. -- 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Description: Hi Lucene Team, Here I explained more 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. was: 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. > 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, > Here I explained more 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Priority: Major (was: Critical) Component/s: (was: core/queryparser) core/search > 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Affects Version/s: 5.3 > 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/queryparser >Affects Versions: 5.3, 6.6 > Environment: Windows and Linux >Reporter: Rohit Balekundri >Priority: Critical > 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Description: 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. was: 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. Key fields: 1. LocationCode (DataType=long) 2. CollectionObjectID (DataType=long) Non-key fields Category (DataType=string) Steps we followed: 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 3. 1. I found all records are showing result if we pass value 'a' or 'A' as search value along with either LocationCode=1 OR CollectionObjectID=1. Only seems to be happening for the character a. I feel it's having similar issue in older Lucene version (Ex:5.3) as well. It's Lucene code after making query it's returning all records. 2. We have two solutions for above existing problem. a) Either to allow to show all records if user enters 'a' or 'A' in search field. Not correct. b) Set value to "null" if user enters 'a' or 'A' in search field value and don't show any records. Example: LocationCode=1 and Category='A' then it should not show any records. But this has side effect about if real record exist with same criteria then it will not show that record. c) Test with other new releases from Lucene and search. But later i found even Lucene 6.6 is also having same bug. This bug was found by our USA team. It's very urgent, needed to be fixed from Lucene team. Kindly consider this bug on top priority. > 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/queryparser >Affects Versions: 6.6 > Environment: Windows and Linux >Reporter: Rohit Balekundri >Priority: Critical > 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Description: 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. Key fields: 1. LocationCode (DataType=long) 2. CollectionObjectID (DataType=long) Non-key fields Category (DataType=string) Steps we followed: 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 3. 1. I found all records are showing result if we pass value 'a' or 'A' as search value along with either LocationCode=1 OR CollectionObjectID=1. Only seems to be happening for the character a. I feel it's having similar issue in older Lucene version (Ex:5.3) as well. It's Lucene code after making query it's returning all records. 2. We have two solutions for above existing problem. a) Either to allow to show all records if user enters 'a' or 'A' in search field. Not correct. b) Set value to "null" if user enters 'a' or 'A' in search field value and don't show any records. Example: LocationCode=1 and Category='A' then it should not show any records. But this has side effect about if real record exist with same criteria then it will not show that record. c) Test with other new releases from Lucene and search. But later i found even Lucene 6.6 is also having same bug. This bug was found by our USA team. It's very urgent, needed to be fixed from Lucene team. Kindly consider this bug on top priority. was: 1. I found all records are showing result if we pass value 'a' or 'A' as search value along with either LocationCode=1 OR CollectionObjectID=1. Only seems to be happening for the character a. I feel it's having similar issue in older Lucene version (Ex:5.3) as well. It's Lucene code after making query it's returning all records. 2. We have two solutions for above existing problem. a) Either to allow to show all records if user enters 'a' or 'A' in search field. Not correct. b) Set value to "null" if user enters 'a' or 'A' in search field value and don't show any records. Example: LocationCode=1 and Category='A' then it should not show any records. But this has side effect about if real record exist with same criteria then it will not show that record. c) Test with other new releases from Lucene and search. But later i found even Lucene 6.6 is also having same bug. This bug was found by our USA team. It's very urgent, needed to be fixed from Lucene team. Kindly consider this bug on top priority. > 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/queryparser >Affects Versions: 6.6 > Environment: Windows and Linux >Reporter: Rohit Balekundri >Priority: Critical > 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. > Key fields: > 1. LocationCode (DataType=long) > 2. CollectionObjectID (DataType=long) > Non-key fields > Category (DataType=string) > Steps we followed: > 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 > 3. > 1.I found all records are showing result if we pass value 'a' or 'A' as > search value along with either LocationCode=1 OR CollectionObjectID=1. Only > seems to be happening for the character a. I feel it's having similar issue > in older Lucene version (Ex:5.3) as well. It's Lucene code after making query > it's returning all records. > 2.We have two solutions for above existing problem. > a)Either to allow to show all records if user enters 'a' or 'A' in search > field. Not correct. > b)Set value to "null" if user enters 'a' or 'A' in search field value and > don't show any records. Example: LocationCode=1 and
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-7932: --- Fix Version/s: (was: 6.6) (was: trunk) (was: Positions Branch) > 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/queryparser >Affects Versions: 6.6 > Environment: Windows and Linux >Reporter: Rohit Balekundri >Priority: Critical > Labels: features > > 1.I found all records are showing result if we pass value 'a' or 'A' as > search value along with either LocationCode=1 OR CollectionObjectID=1. Only > seems to be happening for the character a. I feel it's having similar issue > in older Lucene version (Ex:5.3) as well. It's Lucene code after making query > it's returning all records. > 2.We have two solutions for above existing problem. > a)Either to allow to show all records if user enters 'a' or 'A' in search > field. Not correct. > b)Set value to "null" if user enters 'a' or 'A' in search field value and > don't show any records. Example: LocationCode=1 and Category='A' then it > should not show any records. > But this has side effect about if real record exist with same criteria then > it will not show that record. > c)Test with other new releases from Lucene and search. > But later i found even Lucene 6.6 is also having same bug. > This bug was found by our USA team. > It's very urgent, needed to be fixed from Lucene team. > 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Description: 1. I found all records are showing result if we pass value 'a' or 'A' as search value along with either LocationCode=1 OR CollectionObjectID=1. Only seems to be happening for the character a. I feel it's having similar issue in older Lucene version (Ex:5.3) as well. It's Lucene code after making query it's returning all records. 2. We have two solutions for above existing problem. a) Either to allow to show all records if user enters 'a' or 'A' in search field. Not correct. b) Set value to "null" if user enters 'a' or 'A' in search field value and don't show any records. Example: LocationCode=1 and Category='A' then it should not show any records. But this has side effect about if real record exist with same criteria then it will not show that record. c) Test with other new releases from Lucene and search. But later i found even Lucene 6.6 is also having same bug. This bug was found by our USA team. It's very urgent, needed to be fixed from Lucene team. Kindly consider this bug on top priority. was: 1. I found all records are showing result if we pass value 'a' or 'A' as search value along with either LocationCode=value OR CollectionObjectID=value. Only seems to be happening for the character a. I feel it's having similar issue in previous code as well. It's Lucene code after making query it's returning all records. 2. We have two solutions for above existing problem. a) Either to allow to show all records if user enters 'a' or 'A' in search field. b) Set value to "null" if user enters 'a' or 'A' in search field value and don't show any records. Example: LocationCode=1 and Category='A' then it should not show any records. But this has side effect about if real record exist with same criteria then it will not show that record. c) Test with other new releases from Lucene and search. Currently I am working on Lucene 6.6 to test search function. But later i found even Lucene 6.6 is also having same bug. This bug was found by onsite team. It's very urgent to be fixed from Lucene team. Kindly consider this bug on top priority. > 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/queryparser >Affects Versions: 6.6 > Environment: Windows and Linux >Reporter: Rohit Balekundri >Priority: Critical > Labels: features > Fix For: Positions Branch, trunk, 6.6 > > > 1.I found all records are showing result if we pass value 'a' or 'A' as > search value along with either LocationCode=1 OR CollectionObjectID=1. Only > seems to be happening for the character a. I feel it's having similar issue > in older Lucene version (Ex:5.3) as well. It's Lucene code after making query > it's returning all records. > 2.We have two solutions for above existing problem. > a)Either to allow to show all records if user enters 'a' or 'A' in search > field. Not correct. > b)Set value to "null" if user enters 'a' or 'A' in search field value and > don't show any records. Example: LocationCode=1 and Category='A' then it > should not show any records. > But this has side effect about if real record exist with same criteria then > it will not show that record. > c)Test with other new releases from Lucene and search. > But later i found even Lucene 6.6 is also having same bug. > This bug was found by our USA team. > It's very urgent, needed to be fixed from Lucene team. > 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
[jira] [Updated] (LUCENE-7932) Search record with field value='a' or 'A' returns all records along with one more field value
[ https://issues.apache.org/jira/browse/LUCENE-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Balekundri updated LUCENE-7932: - Priority: Critical (was: Major) > 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/queryparser >Affects Versions: 6.6 > Environment: Windows and Linux >Reporter: Rohit Balekundri >Priority: Critical > Labels: features > Fix For: Positions Branch, trunk, 6.6 > > > 1.I found all records are showing result if we pass value 'a' or 'A' as > search value along with either LocationCode=value OR > CollectionObjectID=value. Only seems to be happening for the character a. I > feel it's having similar issue in previous code as well. It's Lucene code > after making query it's returning all records. > 2.We have two solutions for above existing problem. > a)Either to allow to show all records if user enters 'a' or 'A' in search > field. > b)Set value to "null" if user enters 'a' or 'A' in search field value and > don't show any records. Example: LocationCode=1 and Category='A' then it > should not show any records. > But this has side effect about if real record exist with same criteria then > it will not show that record. > c)Test with other new releases from Lucene and search. Currently I am > working on Lucene 6.6 to test search function. > But later i found even Lucene 6.6 is also having same bug. > This bug was found by onsite team. > It's very urgent to be fixed from Lucene team. > 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
