Thanks Jigar :)
It's really helpful.
On Wednesday, 28 October 2015 12:05 AM, Jigar Shah
wrote:
Most probably LUCENE-6249 changes parser's behavior, for your case.
On Tue, Oct 27, 2015 at 5:33 AM, patel mrugesh
wrote:
Thanks for your reply Erick,
I have gone t
do strict Boolean logic, although it comes close. See:
https://lucidworks.com/blog/2011/12/28/why-not-and-or-and-not/
Best,
Erick
On Sun, Oct 25, 2015 at 11:18 PM, patel mrugesh
wrote:
> Hi All,
> We are using Lucene 4.10.3, one strange behavior we have observed when NOT
> operato
Hi All,
We are using Lucene 4.10.3, one strange behavior we have observed when NOT
operator is used with parenthesis around.
It looks like NOT operator is completely ignored and whatever boolean operator
was before parenthesis is applied.
For example, document text: "lottery ticket", query: "
Hi,
I am facing an issue with phrase query and increment Position. I have tried
following queries and although there were data, 0 result returned.
2) Search Query --> name:"at&t inc" Parsed Query --> +name:"at&t inc"
Result return = 0 Term Vector =
No.
Hi,
I am facing an issue with phrase query having special character (like &, dot,
comma, : etc). I have tried following queries and although there were data, 0
result returned.
1) Search Query --> name:"Pep:Trans vaccines, GSK" Parsed Query -->
+name:"pep:trans vaccines gsk"
Result r
era wrote:
Hi Mrugesh,
This is strange indeed, as the facets are ordered by count, and we use a facet
ordinal (integer code) as a tie breaker. What do you mean by "refreshed"? Do
you have a sample test that shows this behavior?
Shai
On Fri, Dec 12, 2014 at 8:37 AM, patel mrugesh
Hi All,
I am working on Lucene Facet now a day and facet seems working fine. Just one
thing that come to my attention is, order of facet results get changed if there
is same total count.
For example, for country facet following results have been noticed.
First time:
- USA(10)- India(9)- UK(9)
