Is there a way to increase the 'len' of the suggester? The error says it
must be lesser than 32767 but my content has up to 35578.
It is working for fields that are shorter, but the content of my rich text
documents are very big, thus leading to the error above.
Regards,
Edwin
On 8 June 2015 at
I've set it to true already.
true
true
I got this error when I tried to run /suggesthandler?suggest.build=true
-
-
500
33
-
len must be <= 32767; got 35578
java.lang.IllegalArgumentException: len must be <= 32767;
got 35578 at
org.apache.lucene.util.OfflineSorter$ByteSequencesWriter.wri
Check your solrconfig.xml
false
false
if you set to false then the Lookup data structure will rebuilt after the
commit.
You need to invoke the build command to build data for the suggester using
the command
* /suggesthandler?suggest.build=true *
On Sun, Jun 7, 2015 at 7:49 PM, Zheng Lin Edwin
I've tried to use, and there's still no suggestions returned even when I
used suggest.q.
Here is the log:
INFO - 2015-06-07 22:18:24.195; [collection1 shard1 core_node1
collection1] org.apache.solr.handler.component.SuggestComponent;
SuggestComponent prepare with :
suggest.count=10&suggest=true&
Are you using the q param? You should use suggest.q if I remember well!
On 5 Jun 2015 18:02, "Zheng Lin Edwin Yeo" wrote:
> I've tried the queries and it is working fine, but I've found these in the
> logs.Not sure if the behavior is correct or not.
>
> INFO - 2015-06-05 18:06:28.437; [collecti
I've tried the queries and it is working fine, but I've found these in the
logs.Not sure if the behavior is correct or not.
INFO - 2015-06-05 18:06:28.437; [collection1 shard1 core_node1
collection1] org.apache.solr.handler.component.SuggestComponent;
SuggestComponent prepare with :
q=testin&sugg
To verify if you have valued stored, simply do some simple query.
But if was stored from the beginning , probably it is ok.
Please check the logs as well for anything.
If no problem there I can take a look better to the config.
Cheers
2015-06-05 11:07 GMT+01:00 Zheng Lin Edwin Yeo :
> If i've se
If i've set stored=true for that field, so it should be stored already? Or
do I have to verify using other means?
This field is stored from the beginning. I've also tried to index some new
documents in it, and have also set true for
now, but there's still no suggestions showed.
Regards,
Edwin
O
Have you verified that you actually have values stored for the field you
want to build suggestions from ?
Was the field stored from the beginning or you changed it ?
Have you re-indexed the content after you made the field stored ?
Cheers
2015-06-05 10:35 GMT+01:00 Zheng Lin Edwin Yeo :
> Hi Ben
Hi Benedetti,
I've set true in my solrconfig.xml
tentatively, and the field which I'm using for suggestion has been set
stored=true.
However, I still couldn't get any suggestions even after I restart my Solr.
Is there anything else I might have missed out?
In schema.xml
In solrconfig.xml
Thank you so much for your advice.
Regards,
Edwin
On 4 June 2015 at 22:30, Alessandro Benedetti
wrote:
> Please remember this :
>
> "to be used as the basis for a suggestion, the field must be stored"
>
> From the official guide.
>
> Cheers
>
> 2015-06-04 11:19 GMT+01:00 Alessandro Benedetti <
Please remember this :
"to be used as the basis for a suggestion, the field must be stored"
>From the official guide.
Cheers
2015-06-04 11:19 GMT+01:00 Alessandro Benedetti
:
> If you are using an existing indexed field to provide suggestions, you
> simply need to build the suggester and star
If you are using an existing indexed field to provide suggestions, you
simply need to build the suggester and start using it !
No re-indexing needed .
Cheers
2015-06-04 11:01 GMT+01:00 Zheng Lin Edwin Yeo :
> I think I'm confused with the old spellcheck approach that came out more
> frequently d
I think I'm confused with the old spellcheck approach that came out more
frequently during my research.
Just to confirm, do I need to re-index the data in order for this new
approach to work if I'm using an existing field?
Regards,
Edwin
On 4 June 2015 at 16:58, Alessandro Benedetti
wrote:
>
Let me try to clarify the things…
Because you are using solr 5.1 I can not see any reason to try to use the
old spellcheck approach.
If you take a look to the page me and Erick quoted there is a simple config
example :
>
> mySuggester
> FuzzyLookupFactory
> suggester_fuzzy_dir
>
> DocumentDicti
This is the result that I get from the query URL you mentioned. Still not
able to get any output.
0
0
true
mater
true
suggest
xml
Regards,
Edwin
On 4 June 2015 at 15:26, Dhanesh Radhakrishnan wrote:
> Try this
>
>
> http://localhost:8983/solr/collect
Try this
http://localhost:8983/solr/collection1/suggest?suggest=true&suggest.dictionary=suggest&suggest.build=true&wt=xml&suggest.q=mater
On Thu, Jun 4, 2015 at 11:53 AM, Zheng Lin Edwin Yeo
wrote:
> I've tried to use the solr.SuggestComponent as stated in the website, but
> it couldn't work.
>
I've tried to use the solr.SuggestComponent as stated in the website, but
it couldn't work.
When I change to using the suggest with the configuration below and go a
query like http://localhost:8983/solr/collection1/suggest?q=mater, it says
"The Webpage cannot be found"
suggest
This may be helpful: http://lucidworks.com/blog/solr-suggester/
Note that there are a series of fixes in various versions of Solr,
particularly buildOnStartup=false and working on multivalued fields.
Best,
Erick
On Wed, Jun 3, 2015 at 8:04 PM, Zheng Lin Edwin Yeo
wrote:
> My previous suggester
My previous suggester configuration is derived from this page:
https://wiki.apache.org/solr/Suggester
Does it mean that what is written there is outdated?
Regards,
Edwin
On 3 June 2015 at 23:44, Zheng Lin Edwin Yeo wrote:
> Thank you for your suggestions.
> Will try that out and update on th
Thank you for your suggestions.
Will try that out and update on the results again.
Regards,
Edwin
On 3 June 2015 at 21:13, Alessandro Benedetti
wrote:
> I can see a lot of confusion in the configuration!
>
> Few suggestions :
> - read carefully the document and try to apply the suggesting guid
I can see a lot of confusion in the configuration!
Few suggestions :
- read carefully the document and try to apply the suggesting guidance
- currently there is no need to use spellcheck for suggestions, now they
are separated things
- i see text used to derive suggestions, I would prefer there to
This is my suggester configuration:
suggest
org.apache.solr.spelling.suggest.Suggester
org.apache.solr.spelling.suggest.tst.TSTLookupFactory
text
0.005
true
explicit
edismax
10
json
true
text
true
Can you share you suggester configurations ?
Have you read the guide I linked ?
Has the suggestion index/fst has been built ? ( you need to build the
suggester)
Cheers
2015-06-03 4:07 GMT+01:00 Zheng Lin Edwin Yeo :
> Thank you for your explanation.
>
> I'll not need to care where the suggestion
Thank you for your explanation.
I'll not need to care where the suggestions are coming from. All the
suggestions from different fields can be consolidate and display together.
I've tried to put those field into a new Suggestion copy field, but no
suggestion is shown when I set:
Suggestion
Is t
Hi Edwin,
I have worked extensively recently in Suggester and the blog I feel to
suggest is Erick's one.
It's really detailed and good for a beginner and expert as well. [1]
Apart that let's see you particular use case :
1) Do you want to be able to get also where the suggestions are coming from
26 matches
Mail list logo
