Here is my problem statement and I would really appreciate for your feedback.
1. There are 1000's of pdf's with large amount of content are indexed to
Solr.
2. Using AnalyzingInfixSuggester for the suggestions.
Q. As the SuggeterComponent provides the 'entire content' of the field in
the suggesti
I'm using the FreeTextLookupFactory in my implementation now.
Yes, now it can suggest part of the field from the middle of the content.
I read that this implementation is able to consider the previous tokens
when making the suggestions. However, when I try to enter a search phrase,
it seems that
Edwin,
The spellcheck is a thing, the Suggester is another.
If you need to provide auto suggestion to your users, the suggester is the
right thing to use.
But I really doubt to be useful to select as a suggester field the entire
content.
it is going to be quite expensive.
In the case I would agai
Yes I've looked at that before, but I was told that the newer version of
Solr has its own suggester, and does not need to use spellchecker anymore?
So it's not necessary to use the spellechecker inside suggester anymore?
Regards,
Edwin
On 17 June 2015 at 11:56, Erick Erickson wrote:
> Have yo
Have you looked at spellchecker? Because that sound much more like
what you're asking about than suggester.
Spell checking is more what you're asking for, have you even looked at that
after it was suggested?
bq: Also, when I do a search, it shouldn't be returning whole fields,
but just to return
The long content is from when I tried to index PDF files. As some PDF files
has alot of words in the content, it will lead to the *UTF8 encoding is
longer than the max length 32766 error.*
I think the problem is the content size of the PDF file exceed 32766
characters?
I'm trying to accomplish to
The suggesters are built to return whole fields. You _might_
be able to add multiple fragments to a multiValued
entry and get fragments, I haven't tried that though
and I suspect that actually you'd get the same thing..
This is an XY problem IMO. Please describe exactly what
you're trying to accom
in line :
2015-06-16 4:43 GMT+01:00 Zheng Lin Edwin Yeo :
> Thanks Benedetti,
>
> I've change to the AnalyzingInfixLookup approach, and it is able to start
> searching from the middle of the field.
>
> However, is it possible to make the suggester to show only part of the
> content of the field (
Also, is there a way to overcome the long content problem?
I'm getting this error when I've indexed large rich-text documents and
tried to build the suggester.
*{*
* "responseHeader":{*
*"status":500,*
*"QTime":47},*
* "error":{*
*"msg":"Document contains at least one immense term i
Thanks Benedetti,
I've change to the AnalyzingInfixLookup approach, and it is able to start
searching from the middle of the field.
However, is it possible to make the suggester to show only part of the
content of the field (like 2 or 3 fields after), instead of the entire
content/sentence, which
ehehe Edwin, I think you should read again the document I linked time ago :
http://lucidworks.com/blog/solr-suggester/
The suggester you used is not meant to provide infix suggestions.
The fuzzy suggester is working on a fuzzy basis , with the *starting* terms
of a field content.
What you are lo
I've indexed a rich-text documents with the following content:
This is a testing rich text documents to test the uploading of files to Solr
When I tried to use the suggestion, it return me the entire field in the
content once I enter suggest?q=t. However, when I tried to search for
q='rich', I d
12 matches
Mail list logo
