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
ever
Has anyone ever been successful in processing 150M records using the
Suggester Component? The make of the component, please comment.
On Tue, Jun 26, 2018 at 1:37 AM, Ratnadeep Rakshit
wrote:
> The site_address field has all the address of United states. Idea is to
> build something similar to Go
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": {
"status": 0,
"QTime": 3125,
"par
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
Can anyone put some light on this?
On Tue, Jun 12, 2018 at 12:32 AM, Ratnadeep Rakshit
wrote:
> Here's the stack trace :
>
> 538 ERROR - 2018-06-07 09:07:36.030; [ x:addressbook]
> org.apache.solr.common.SolrException; null:java.lang.RuntimeException:
> java.lang.OutOfMemory
>
> Error: Java h
Here's the stack trace :
538 ERROR - 2018-06-07 09:07:36.030; [ x:addressbook]
org.apache.solr.common.SolrException; null:java.lang.RuntimeException:
java.lang.OutOfMemory
Error: Java heap space
539 at
org.apache.solr.servlet.HttpSolrCall.sendError(HttpSolrCall.java:607)
540
Ratnadeep,
On 6/11/18 12:25 PM, Ratnadeep Rakshit wrote:
> I am using the Solr Suggester component in Solr 5.5 with a lot of address
> data. My Machine has allotted 20Gb RAM for solr and the machine has 32GB
> RAM in total.
>
> I have an address book core with the following vitals -
>
> "numDocs
Here's a writeup on suggester:
https://lucidworks.com/blog/2015/03/04/solr-suggester/
The biggest difference is that spellcheck returns individual _terms_
whereas suggesters can return entire fields.
Neither are "a function of the UI" any more than searching is a
function of the UI. In both cases
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’’ isn’t
StandardTokenizer splits your text into tokens, and the suggester
suggests tokens independently. It sounds as if you want the suggestions
to be based on the entire text (not just the current word), and that
only adjacent words in the original should appear as suggestions.
Assuming that's what
Any idea?
> On 12 Şub 2015, at 11:12, Volkan Altan wrote:
>
> Hello Everyone,
>
> All I want to do with Solr suggester is obtaining the fact that the asserted
> suggestions for the second letter whose entry actualizes after the initial
> letter is actually related to initial letter, itself
I have added it and it didnt work. Still returning different result to 1=C
and q=c
On Tue, Sep 10, 2013 at 1:52 AM, Chris Hostetter
wrote:
>
> : This is probably because your dictionary is made up of all lower case
> tokens,
> : but when you query the spell-checker similar analysis doesnt happen
: This is probably because your dictionary is made up of all lower case tokens,
: but when you query the spell-checker similar analysis doesnt happen. Ideal
: case would be when you query the spellchecker you send lower case queries
You can init the SpellCheckComponent with a "queryAnalyzerFieldT
This is probably because your dictionary is made up of all lower case tokens,
but when you query the spell-checker similar analysis doesnt happen. Ideal
case would be when you query the spellchecker you send lower case queries
--
View this message in context:
http://lucene.472066.n3.nabble.com/
1 73 03 29 80
E-DEAL
Innover la Relation Client
-Message d'origine-
De : Tanguy Moal [mailto:tanguy.m...@gmail.com]
Envoyé : mercredi 3 juillet 2013 10:27
À : solr-user@lucene.apache.org
Objet : Re: Solr Suggest
Hello Adrien,
Looking quickly at your schema, I suspect tha
Hello Adrien,
Looking quickly at your schema, I suspect that the suggestions field isn't
populated, so the suggester dictionary is empty.
How is input sent to that field ? Providing a few sample documents you are
indexing could help understand what is going on.
If you intended to copy content
Hi Simon,
Good that it works.
The reason as far as I could make out is that by itself/ standalone the
SpellCheckComponent (used by the suggester) is not distributed. One way to
explicitly distribute the search is to provide the shards:
http://wiki.apache.org/solr/SpellCheckComponent#Distributed_S
Hi Aloke
Thanks for your reply. It works with the
http://url.com:8983/solr/mycore/suggest?q=bar&wt=json&distrib=true
parameter or when inserted into the defaults
true
default
suggest
false
10
Hi,
Check the obvious first, that you have rebuilt & reloaded the suggest
dictionary individually on all nodes. Also the other checks here:
http://stackoverflow.com/questions/6653186/solr-suggester-not-returning-any-results
Then, try with one of query component OR distrib=false setting:
http://l
24 matches
Mail list logo
