Hello,
I can't find anything in the docs to understand how Solr sorts suggest results
when the weight is the same (0 in my case).
Here is my suggester config:
---
mySuggester
AnalyzingInfixLookupFactory
DocumentDictionaryFactory
autocomplete
pa
Hello,
I can't find anything in the
docs<https://lucene.apache.org/solr/guide/7_2/suggester.html> to understand how
Solr sorts suggest results when the weight is the same (0 in my case).
Here is my suggester config:
---
mySuggester
AnalyzingInfixLo
I wrote some Python for updating a collection config. An optional part of that
is to go to each replica and start a suggester build.
If your collection is sharded and you load from a dictionary, you’ll also need
to add distrib=false to the queries, otherwise you’ll get suggest results from
Hello,
I want to use solr suggest
(https://lucene.apache.org/solr/guide/8_2/suggester.html) in a solr cloud with
replication.
We are using solr cloud with 2 nodes.
To build up the suggest I have to call "suggest.buildAll=true".
I do it this way:
- Ask Zookeeper for a Solr Nod
Hi Buddy,
We have built Auto-Suggest over Solr with EdgeNGrams, Custom Spellcheck
Factory and Synonyms (for spelling mistakes). This solves for most cases.
If you have the dictionary for spelling mistakes, EdneNGrams after
Synonym factory will do the job.
On Thu, 16 Apr 2020 at 13:35, aTan
Hello.
I'm new to Solr and would be thankful for advice for the following case:
We have Suggest API running on production using Solr 6, which currently
prevent changes in the response and query parameters. That's why SpellCheck
component can't be used (parameter is custom, not
Hello.
I'm new to Solr and would be thankful for advice for the following case:
We have Suggest API running on production using Solr 6, which currently
prevent changes in the response and query parameters. That's why SpellCheck
component can't be used (parameter is custom, not
requests per keystroke. Do let me know for any other queries.
:)
On Mon, 3 Feb 2020 at 22:10, Moyer, Brett wrote:
> Hello,
>
> Looking to see how others accomplished this goal. We have a 3 Tier
> architecture, Solr is down deep in T3 far from the end user. How do you
> ma
Hello,
Looking to see how others accomplished this goal. We have a 3 Tier
architecture, Solr is down deep in T3 far from the end user. How do you make
Auto-Suggest calls from the Internet Browser through the Tiers down to Solr in
T3? We essentially created steps down each tier, but I&#
Hey Artur,
If I have understood correctly, you want to suggest terms related to the
query. It would be helpful if you describe the use case as well. Anyways,
please go through this once:
1. Keep different form of words as different documents so that they
could be suggested ("c
Hi,
I am quite new to solr and I am interested in implementing a sort of auto terms
suggest (not auto complete) feature based on the user query.
Users builds some query (on multiple fields) and I am trying to help him
refining his query by suggesting to add more terms based on his current query
Hello Team,
I am not able to get highlighted terms from the Suggest component when
using a context filter query. My definition of the suggest search component
looks as follows.
mySuggester
BlendedInfixLookupFactory
position_linear
DocumentDictionaryFactory
Right.
On Wed, May 8, 2019 at 11:49 PM Shawn Heisey wrote:
> On 5/8/2019 2:34 PM, Mikhail Khludnev wrote:
> > It reminds me
> https://lucene.apache.org/solr/guide/7_6/blob-store-api.html but
> > I don't think it's already integrated with suggester.
>
> I'm having one of of those days where I can
On 5/8/2019 2:34 PM, Mikhail Khludnev wrote:
It reminds me https://lucene.apache.org/solr/guide/7_6/blob-store-api.html but
I don't think it's already integrated with suggester.
I'm having one of of those days where I can't seem to recall things easily.
With the blob store, the blobs are in t
It reminds me https://lucene.apache.org/solr/guide/7_6/blob-store-api.html but
I don't think it's already integrated with suggester.
On Wed, May 8, 2019 at 11:26 PM Shawn Heisey wrote:
> On 5/8/2019 1:59 PM, Walter Underwood wrote:
> > Our suggest dictionary is too big
...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On May 8, 2019, at 1:26 PM, Shawn Heisey wrote:
>
> On 5/8/2019 1:59 PM, Walter Underwood wrote:
>> Our suggest dictionary is too big for Zookeeper. I’m trying to load it from
>> an absolute path, but the
On 5/8/2019 1:59 PM, Walter Underwood wrote:
Our suggest dictionary is too big for Zookeeper. I’m trying to load it from an
absolute path, but the Solr 6.6.1 insists on interpreting that as a Zookeeper
path. Any way to disable that?
I wouldn't be surprised to learn it's not possi
Our suggest dictionary is too big for Zookeeper. I’m trying to load it from an
absolute path, but the Solr 6.6.1 insists on interpreting that as a Zookeeper
path. Any way to disable that?
java.lang.IllegalArgumentException: Invalid path string
"/configs/questions-suggest//solr/suggest
On 2019-02-18T18:12:44, David '-1' Schmid wrote:
> Will report back if that's working out.
It's working!
If anybody want's to replicate, here's what I ended up with.
.. managed-schema:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Hello again!
After playing around with more simple solutions, I gather the suggester
cannot do this.
I've found a resource (namely 'Solr in Action'), they use a
combination of
- two copyFields:
- solr.TextField with simple whitespace tokenizer (field:'words')
- as above, but with added EdgeNG
ggestion query does not support boolean logic. I'm
not sure, but the query pulls up tokens matching "and":
.. curl 'http://localhost:8983/solr/dblp/authors?suggest.q=Diep%20AND%20Stef'
.
. "suggest":{"default":{
. "Diep AND Stef&q
.
.
After building with
curl 'http://localhost:8983/solr/dblp/authors?suggest.build=true'
this will yield someting along the lines of
.. curl 'http://localhost:8983/solr/dblp/authors?suggest.q=Diepen'
. {
. "suggest":{"defau
February 15, 2019 10:23 AM
To: solr-user@lucene.apache.org
Subject: Suggest Component, prefix match (sur-)name
Hello solr-users!
I'm a bit stumped and after some days of trial-and-error, I've come to the
conclusion that I cannot figure this out by myself.
Where I'm at:
Solr 7.7
.
.
After building with
curl 'http://localhost:8983/solr/dblp/authors?suggest.build=true'
this will yield someting along the lines of
.. curl 'http://localhost:8983/solr/dblp/authors?suggest.q=Diepen'
. {
. "suggest":{"defau
On 8/6/2018 11:18 AM, Steve Pruitt wrote:
> Changing the request handler to /suggest in the Admin Console Query panel
> doesn't work. It was a guess on my part to see if it would.
>
> Is the way to do this, or do I need to always use browser, postman, etc. for
> debugging?
Changing the request handler to /suggest in the Admin Console Query panel
doesn't work. It was a guess on my part to see if it would.
Is the way to do this, or do I need to always use browser, postman, etc. for
debugging?
Thanks.
-Steve
I am having difficulty getting Solr's Suggest Component to work with a weight
expression. I have tried to match the format of the example in the
documentation (see related code from schema.xml and solrconfig.xml below) but
no results are found when I request suggestions from this dictionar
_6/suggester.html
>
> Cheers,
> Peter.
>
> -Original Message-
> From: Arunan Sugunakumar [mailto:arunans...@cse.mrt.ac.lk]
> Sent: 03 July 2018 12:17
> To: solr-user@lucene.apache.org
> Subject: Filtering solr suggest results
>
> Hi,
>
> I would like
solr suggest results
Hi,
I would like to know whether it is possible to filter the suggestions returned
by the suggest component according to a field. For example I have a list of
books published by different publications. I want to show suggestions for a
book title under a specific publication
Hi,
I would like to know whether it is possible to filter the suggestions
returned by the suggest component according to a field. For example I have
a list of books published by different publications. I want to show
suggestions for a book title under a specific publication.
Thanks in Advance
lar to Google Places autosuggest.
>
> Here's an example query: curl "http://localhost/solr/
> addressbook/suggest?suggest.q=1054%20club&wt=json"
>
> Response:
>
> {
> "responseHeader": {
> "status": 0,
> "QTime"
The site_address field has all the address of United states. Idea is to
build something similar to Google Places autosuggest.
Here's an example query: curl "
http://localhost/solr/addressbook/suggest?suggest.q=1054%20club&wt=json";
Response:
{
"responseHeader":
I didn't get any answer to my questions ( unless you meant you have 25
millions of different values for those fields ...)
Please read again my answer and elaborate further.
Do you problem happen for the 2 different suggesters ?
Cheers
-
---
Alessandro Benedetti
Search Consultant
Anyone from the Solr team who can shed some more light?
On Tue, Jun 12, 2018 at 8:13 PM, Ratnadeep Rakshit
wrote:
> I observed that the build works if the data size is below 25M. The moment
> the records go beyond that, this OOM error shows up. Solar itself shows 56%
> usage of 20GB space during
I observed that the build works if the data size is below 25M. The moment
the records go beyond that, this OOM error shows up. Solar itself shows 56%
usage of 20GB space during the build. So, is there some settings I need to
change to handle larger data size?
On Tue, Jun 12, 2018 at 3:17 PM, Aless
Hi,
first of all the two different suggesters you are using are based on
different data structures ( with different memory utilisation) :
- FuzzyLookupFactory -> FST ( in memory and stored binary on disk)
- AnalyzingInfixLookupFactory -> Auxiliary Lucene Index
Both the data structures should be v
y.security.SecurityHandler.handle(
> SecurityHandler.java:577)
>
>591 at org.eclipse.jetty.server.session.SessionHandler.
> doHandle(SessionHandler.java:223)
>
>592 at org.eclipse.jetty.server.handler.ContextHandler.
> doHandle(ContextHandler.java:1127)
>
>593
sbook]
org.eclipse.jetty.servlet.ServletHandler; Error for
/solr/addressbook/suggest
598 java.lang.OutOfMemoryError: Java heap space
599 at
org.apache.lucene.util.packed.Packed64.(Packed64.java:73)
600 at
org.apache.lucene.util.packed.PackedInts.getMutable(PackedInts.java:1009)
601
adata
> false
> false
>
>
>
> The handler is defined like so -
>
>
>
> true
> 10
> mySuggester1
> mySuggester2
> false
> explicit
>
>
> suggest
>
>
>
> *Problem Statement*
>
> Every time I try to buil
ryFactory
site_address_other
suggestType
property_metadata
false
false
The handler is defined like so -
true
10
mySuggester1
mySuggester2
false
explicit
suggest
*Problem Statement*
Every time I try to build the suggest index using the suggest.build=true
u
In addition to what Erick and Walter correctly mentioned :
"heap usage varies from 5 gb to 12 gb . Initially it was 5 gb then increased
to 12 gb gradually and decreasing to 5 gb again. (may be because of garbage
collection)
10-12 GB maximum heap uses, allocated is 50 GB. "
Did I read it right
Yes, why are you doing this? A suggester is designed to have a smaller set of
terms than the entire index.
I would never expect a 130 million term suggester to work. I’m astonished that
it works with 50 million terms.
We typically have about 50 thousand terms in a suggester.
Also, you haven’t
bq. I have 130 million documents and each document has unique document id. I
want to build suggester on document id.
Why do it this way? I'm supposing you want to have someone start
typing in the doc ID
then do autocomplete on it. For such a simple operation, it would be
far easier and
pretty cert
I sent log of node to which i sent the request. need to check other nodes
log
>>In SolrCloud an investigation does not isolate to a single Solr log : you
>>see a timeout, i would recommend to check both the nodes involved.
monitored from admin UI, could not find any clue at the time of failure.
Hi Yogendra,
you mentioned you are using SolrCloud.
In SolrCloud an investigation does not isolate to a single Solr log : you
see a timeout, i would recommend to check both the nodes involved.
When you say : " heap usage is around 10 GB - 12 GB per node.", do you refer
to the effective usage by th
I have 130 million documents and each document has unique document id. I
want to build suggester on document id. suggest dictionary building is
failing for 130 millions. while testing it was successful with 50 million
documents.
8 nodes with 50 GB head for each node and total 600 gb ram
heap
gt;
>> I got a NullPointer-Exception running a select-SearchHandler with a
>> suggest component on multiple shards (cloud mode).
>> It does work in the same configuration with a single shard (or non-cloud
>> setup).
>> The suggest requestHandler
unsubscribe
On Tue, Oct 24, 2017 at 9:48 PM, wrote:
> Hello everyone,
>
> I got a NullPointer-Exception running a select-SearchHandler with a
> suggest component on multiple shards (cloud mode).
> It does work in the same configuration with a single shard (or non-cloud
> set
Hello everyone,
I got a NullPointer-Exception running a select-SearchHandler with a suggest
component on multiple shards (cloud mode).
It does work in the same configuration with a single shard (or non-cloud setup).
The suggest requestHandler does work in both setups.
Exception:
true
500
Hello, Georg!
Have you seen
http://blog.mikemccandless.com/2014/01/finding-long-tail-suggestions-using.html
?
On Sun, Mar 5, 2017 at 11:43 PM, Georg Sorst wrote:
> Hi all,
>
> is there a way to get the suggester to autocomplete words and suggest
> co-occurences instead of suggest
://joelsolr.blogspot.com/
On Sun, Mar 5, 2017 at 3:43 PM, Georg Sorst wrote:
> Hi all,
>
> is there a way to get the suggester to autocomplete words and suggest
> co-occurences instead of suggesting complete field values? The behavior I'm
> looking for is quite similar to G
Hi all,
is there a way to get the suggester to autocomplete words and suggest
co-occurences instead of suggesting complete field values? The behavior I'm
looking for is quite similar to Google, only based on index values not
actual queries.
Let's say there are two items in the in
st.Suggester
org.apache.solr.spelling.suggest.fst.AnalyzingLookupFactory
suggest_ja
true
true
freq
suggest
text_ja_romaji
true
text_ja_romaji
true
suggest_ja
false
10
true
true
false
suggest
ght now !
Cheers
On Sat, Jun 11, 2016 at 1:11 AM, khawar yunus wrote:
> I am in the same boat as you. did you figure out why it does that?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/solr-spellcheck-suggest-correct-word-when-FileBasedSpe
I am in the same boat as you. did you figure out why it does that?
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-spellcheck-suggest-correct-word-when-FileBasedSpellChecker-tp4138769p4281821.html
Sent from the Solr - User mailing list archive at Nabble.com.
ext.
> > > >>
> > > >> 2. Use copy fields to put all possible suggestions into same field
> > name,
> > > >> so
> > > >> no more dynamic field settings, with another field defining whatever
> > the
> > >
stions into same field
> name,
> > >> so
> > >> no more dynamic field settings, with another field defining whatever
> the
> > >> option would be for that document out of the combo box and use context
> > >> filters which can be passed at query time
display/solr/Suggester#Suggester-ContextFiltering
> >>
> >> Hope this helps a bit
> >>
> >> Nick
> >>
> >> On Wed, May 11, 2016 at 7:05 AM, Lasitha Wattaladeniya <
> watt...@gmail.com
> >> >
> >> wrote:
> >>
> &
6 at 7:05 AM, Lasitha Wattaladeniya > >
>> wrote:
>>
>> > Hello devs,
>> >
>> > I'm trying to implement auto complete text suggestions using solr. I
>> have a
>> > text box and next to that there's a combo box. So the auto compl
gt; > I'm trying to implement auto complete text suggestions using solr. I
> have a
> > text box and next to that there's a combo box. So the auto complete
> should
> > suggest based on the value selected in the combo box.
> >
> > Basically I should be abl
-ContextFiltering
Hope this helps a bit
Nick
On Wed, May 11, 2016 at 7:05 AM, Lasitha Wattaladeniya
wrote:
> Hello devs,
>
> I'm trying to implement auto complete text suggestions using solr. I have a
> text box and next to that there's a combo box. So the auto complete should
Hello devs,
I'm trying to implement auto complete text suggestions using solr. I have a
text box and next to that there's a combo box. So the auto complete should
suggest based on the value selected in the combo box.
Basically I should be able to change the suggest field based on
the UI. In both cases you have to do something
user-friendly with the return.
Best,
Erick
On Mon, Jan 4, 2016 at 2:06 PM, Steven White wrote:
> Hi,
>
> I'm trying to understand what are the differences between Solr suggest,
> auto complete & spellcheck? Isn't each a function
Hi,
I'm trying to understand what are the differences between Solr suggest,
auto complete & spellcheck? Isn't each a function of the UI? If not, can
you provide me with links that show end-to-end example setting up Solr to
get all of the 3 features?
I'm on Solr 5.2.
Thanks
Steve
I am trying to figure out how to give weights to my suggestions but I can
find no documentation on how to do this correctly.
Here is my configuration:
solrconfig.xml
mySuggester
DocumentDictionaryFactory
FuzzyLookupFactory
suggest
popularity
textSuggest
:
http://lucene.472066.n3.nabble.com/suggest-tp4124963p4227196.html
Sent from the Solr - User mailing list archive at Nabble.com.
t; make
> >>>> the
> >>>>>>> dictionary. The default value is 2. Increasing this would mean you
> >>>> want
> >>>>>>> more than the previous 2 tokens to be taken into consideration when
> >>>> making
> >>>&g
ant
>>>>>>> more than the previous 2 tokens to be taken into consideration when
>>>> making
>>>>>>> the suggestions. "
>>>>>>
>>>>>>
>>>>>> This makes me confused, as I was not expecting this para
t;>>>> This makes me confused, as I was not expecting this param to affect the
>>>>> suggestion dictionary.
>>>>> So I would like a clarification here from our masters :)
>>>>> At this point let's see what happens at query time .
>>>>
gt;> >> As my understanding the ngrams params will consider the last N-1
>> tokens
>> >> the user put separated by the space separator.
>> >>
>> >> "Builds an ngram model from the text sent to {@link
>> >>> * #build} and predicts b
link
> >>> * #build} and predicts based on the last grams-1 tokens in
> >>> * the request sent to {@link #lookup}. This tries to
> >>> * handle the "long tail" of suggestions for when the
> >>> * incoming query is a never before seen qu
t;
>> Example , grams=3 should consider only the last 2 tokens
>>
>> special mp3 p -> mp3 p
>>
>> Then this query is analysed using the "suggestFreeTextAnalyzerFieldType" .
>> We produce 3 tokens :
>>
>>
>>
>>
>> A
gt;
>
>
> And we run the prefix matching on the FST .
>
> *Conclusion*
> My understanding is wrong for sure at some point, as the behaviour I get
> is different.
> Can we discuss this , clarify this and eventually put it in the official
> documentation ?
>
> Cheers
s://github.com/apache/jackrabbit-oak/blob/trunk/oak-solr-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/solr/query/SolrQueryIndex.java#L318
>>> [2] :
>>>
>>> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-solr-core/src/main/java/org/apache/jackrabbit/oak
318
>> [2] :
>>
>> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-solr-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/solr/query/SolrQueryIndex.java#L370
>>
>>
>>
>> >
>> > Cheers
>> >
>> > 2015-02-
uld consider only the last 2 tokens
>
> special mp3 p -> mp3 p
>
> Then this query is analysed using the "suggestFreeTextAnalyzerFieldType" .
> We produce 3 tokens :
>
>
>
>
> And we run the prefix matching on the FST .
>
> *Conclusion*
> My un
hould consider only the last 2 tokens
>
> special mp3 p -> mp3 p
>
> Then this query is analysed using the "suggestFreeTextAnalyzerFieldType" .
> We produce 3 tokens :
>
>
>
>
> And we run the prefix matching on the FST .
>
> *Conclusion*
> My unde
TextAnalyzerFieldType" .
We produce 3 tokens :
And we run the prefix matching on the FST .
*Conclusion*
My understanding is wrong for sure at some point, as the behaviour I get is
different.
Can we discuss this , clarify this and eventually put it in the official
documentation ?
Cheers
I'm implementing an auto-suggest feature in Solr, and I'll like to achieve
the follwing:
For example, if the user enters "mp3", Solr might suggest "mp3 player",
"mp3 nano" and "mp3 music".
When the user enters "mp3 p", the suggestion
318
> [2] :
>
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-solr-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/solr/query/SolrQueryIndex.java#L370
>
>
>
> >
> > Cheers
> >
> > 2015-02-02 12:17 GMT+00:00 Jan Høydahl :
> >
> &g
//github.com/apache/jackrabbit-oak/blob/trunk/oak-solr-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/solr/query/SolrQueryIndex.java#L370
>
> Cheers
>
> 2015-02-02 12:17 GMT+00:00 Jan Høydahl :
>
> > Using the /suggest handler wired to SuggestComponent, the
>
stions in SolrJ !
> I have to go with manual Json parsing.
> Cheers
>
> 2015-02-02 12:17 GMT+00:00 Jan Høydahl :
>
>> Using the /suggest handler wired to SuggestComponent, the
>> SpellCheckResponse objects are not populated.
>> Reason is that QueryResponse lo
Just had the very same problem, and I confirm that currently is quite a
mess to manage suggestions in SolrJ !
I have to go with manual Json parsing.
Cheers
2015-02-02 12:17 GMT+00:00 Jan Høydahl :
> Using the /suggest handler wired to SuggestComponent, the
> SpellCheckResponse objects a
Yes. I did it. Bu it doesn’t work.
New Example;
TSTLookup
doc 1 : shoe adidas 2 hiking
doc 2 : galaxy samsung s5 phone
doc 3 : shakeology sample packets
http://localhost:8983/solr/solr/suggest?q=samsung+hi
0
1
2
0
7
samsung s5
samsung s5 phone
1
8
10
hiking
(samsung s5) hiking
0
On 02/17/2015 03:46 AM, Volkan Altan wrote:
First of all thank you for your answer.
You're welcome - thanks for sending a more complete example of your
problem and expected behavior.
I don’t want to use KeywordTokenizer. Because, as long as the compound words
written by the user are availabl
First of all thank you for your answer.
Example Url:
doc 1 suggest_field: galaxy samsung s5 phone
doc 2 suggest_field: shoe adidas 2 hiking
http://localhost:8983/solr/solr/suggest?q=galaxy+s
The result for which I am waiting is just like the one indicated below. But;
the ‘’Galaxy shoe
use KeywordTokenizer instead - this will
preserve the entire original text and suggest complete texts, rather
than words
2) maybe consider using a shingle filter along with standard tokenizer,
so that your tokens include multi-word shingles
3) Use a suggester with better support for a statistical l
ted to initial letter, itself. But; just like the
> initial letters, the second letters rotate independently, as well.
>
>
> Example;
> http://localhost:8983/solr/solr/suggest?q=facet_suggest_data:”adidas+s";
> <http://localhost:8983/solr/vitringez/suggest?q=facet_suggest_d
independently, as well.
Example;
http://localhost:8983/solr/solr/suggest?q=facet_suggest_data:”adidas+s";
<http://localhost:8983/solr/vitringez/suggest?q=facet_suggest_data:%22adidas+s%22>
adidas s
response>
0
4
1
27
28
samsung
facet_suggest_data:"adidas samsung"
0
a
Hi List,
For file based search suggest (
https://cwiki.apache.org/confluence/display/solr/Suggester), a file needs
to be provided. And I found managed resources (
https://cwiki.apache.org/confluence/display/solr/Managed+Resources) can let
user feed in data using rest services.
My question is
Using the /suggest handler wired to SuggestComponent, the SpellCheckResponse
objects are not populated.
Reason is that QueryResponse looks for a top-level element named "spellcheck"
else if ( "spellcheck".equals( n ) ) {
_spellInfo = (Name
10:56 PM, Michael Sokolov
wrote:
I believe the spellchecker component persists these indexes now and reloads
them on restart rather than rebuilding.
-Mike
On 11/13/14 7:40 PM, Walter Underwood wrote:
We have to manually rebuild the suggest dictionaries after a restart. This
seems odd, since s
alter Underwood
>> wun...@wunderwood.org
>> http://observer.wunderwood.org/
>>
>>
>> On Nov 13, 2014, at 10:56 PM, Michael Sokolov
>> wrote:
>>
>>> I believe the spellchecker component persists these indexes now and reloads
>>> them on restart rat
Sokolov
wrote:
I believe the spellchecker component persists these indexes now and reloads
them on restart rather than rebuilding.
-Mike
On 11/13/14 7:40 PM, Walter Underwood wrote:
We have to manually rebuild the suggest dictionaries after a restart. This
seems odd, since someone else had a
the spellchecker component persists these indexes now and reloads
> them on restart rather than rebuilding.
>
> -Mike
>
> On 11/13/14 7:40 PM, Walter Underwood wrote:
>> We have to manually rebuild the suggest dictionaries after a restart. This
>> seems odd, since some
I believe the spellchecker component persists these indexes now and
reloads them on restart rather than rebuilding.
-Mike
On 11/13/14 7:40 PM, Walter Underwood wrote:
We have to manually rebuild the suggest dictionaries after a restart. This
seems odd, since someone else had a problem
We have to manually rebuild the suggest dictionaries after a restart. This
seems odd, since someone else had a problem because they did rebuild after
restart.
We’re running 4.7 and our dictionaries are configured like this. We do this for
several fields.
fieldName
:
https://github.com/safarijv/ifpress-solr-plugin/blob/master/src/main/java/com/ifactory/press/db/solr/spelling/suggest/MultiSuggester.java
which merges the fields while building the suggester index, allowing us
to provide different weights for suggestions from different fields.
-Mike
On 11/11
EdgeNGrams from the left side (normal
priority)
- Lastly, single words or word parts (compound words) as EdgeNGrams
However, I was not very successful in supplying a single requestHandler
("/suggest") with data from multiple suggesters. I have also not been
able to find any sample of how thi
Thx to you two.
Just in case anybody else is trying to do "this". The following SolrJ code
corresponds to the http request
GET http://localhost:8983/solr/solrpedia/suggest?q=atmo
of "Solr in Action" (chapter 10):
...
SolrServer server = new HttpSolrServer("http://loca
1 - 100 of 380 matches
Mail list logo
