you're mis-using suggester. It’s purpose is to return the entire contents of the “document”, to handle, specifically, multi-word suggestions, typically just a few words, often 2-4. Putting a large text field instead is outside the design.
Also remember that the suggester is looking for the _indexed_ values to return best match. So stemming etc. are in the part that matches, and the stored portion (which is a big, unanalyzed bunch of text) is all that’s available to be returned. How would suggester know which parts of a large text field to return? Perhaps you can extract “important” short phrases from the text and put those in the suggester as separate documents, but I admit that’s very hand-wavy. This is where Named Entity Recognition etc. are sometimes used, but that’s not something you get OOB, usually it’s done during the ETL process. You really have to re-think your expectations about what OOB suggester is good for. Best, Erick > On Jun 19, 2019, at 11:58 AM, ppunet <ppu...@gmail.com> wrote: > > Here is my problem statement and I would really appreciate for your feedback. > > Solr version 7.6.0 > > 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 suggestions. How is it possible to have Suggester to return only part of > the content of the field, instead of the entire content, which in my > scenario quite long? > > > Thanks in advance. > > PD > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
