hi,
When using AnalyzingInfixSuggestor, the suggest performance is faster than
the prefix query. How AnalyzingInfixSuggestor is faster than prefixQuery?
Is FST constructed in different way for AnalyzingInfixSuggestor? Or any
other reason?
Thanks.
Hi Sahil,
I just confirmed, and so did one of my colleagues, that the redirection is
actually taking the user to the 6.4.2's downloads page.
Do you think it could be a case of stale browser cache in your case? Can
you please try with a different browser, or use curl, to confirm?
Thanks,
Ishan
On W
Probably you can assign a reverse length weight?
On Wed, Mar 8, 2017 at 1:02 PM, Sidhant Aggarwal wrote:
> Hi,
>
> Im using analyzing infix suggestor. I have a use case for which i cant
> find a solution to so if anyone can help me out with that.
> Suppose i index two terms :-
> abc
> abc def
>
Hi,
Please find wdftypes.txt in the source tree for an example.
It is an argument of word delimiter filter factory.
Also see hashtag example: https://issues.apache.org/jira/browse/SOLR-2059
Ahmet
On Wednesday, March 8, 2017 6:22 AM, Yonghui Zhao wrote:
Hi Ahmet,
Thanks for your reply, but I
Seems it is related to an empty segment, all docs in this segment are
deleted before commit.
Any one can confirm it? Maybe I need upgrade my lucene version.
2017-03-03 10:19 GMT+08:00 Yonghui Zhao :
> Hi all,
>
> Anyone see this exception before? Is it a lucene bug or something wrong
> in my co
Thanks. I'll have a look.
-Original Message-
From: "Sahil Agarwal"
Sent: 3/8/2017 11:32 AM
To: "java-user@lucene.apache.org"
Subject: Re: [ANNOUNCE] Apache Solr 6.4.2 released
FYI, the http://lucene.apache.org/solr/mirrors-solr-latest-redir.html
link redirects to http://www.apache.
Hi,
Im using analyzing infix suggestor. I have a use case for which i cant find a
solution to so if anyone can help me out with that.
Suppose i index two terms :-
abc
abc def
And both these terms were indexed with the same weight.
Now suppose in my query i type abc i want the exact match to be
