Don't add this parameter to the searchComponent definition, because the
components where you've added it, GapFragmenter and RegexFragmenter, simply
don't use it.
Instead, add it to your request handler (/select etc.) if you've configured
highlighting in the handler or append it to your query:
*&hl.maxAnalzyedChars=<some_really_big_number>*.
Additionally also set the *hl.fragsize parameter to 0*, if your text is
larger than 51200 chars which it mostly is, in a similar fashion.
On Sun, Feb 14, 2016 at 9:02 PM Evert R. <evert.ra...@gmail.com> wrote:
> Hi Binoy,
>
> I could not find this option in my solrconfig.xml file. ]
>
> I tryied to add this setting and nothing changed...
>
> Here is the code, I might miss placed:
>
> <code>
> <searchComponent class="solr.HighlightComponent" name="highlight">
> <highlighting>
> <!-- Configure the standard fragmenter -->
> <!-- This could most likely be commented out in the "default" case
> -->
> <fragmenter name="gap"
> default="true"
> class="solr.highlight.GapFragmenter">
> <lst name="defaults">
> <int name="hl.fragsize">400</int>
> <int name="hl.maxAnalyzedChars">409600</int>
> </lst>
> </fragmenter>
>
> <!-- A regular-expression-based fragmenter
> (for sentence extraction)
> -->
> <fragmenter name="regex"
> class="solr.highlight.RegexFragmenter">
> <lst name="defaults">
> <!-- slightly smaller fragsizes work better because of slop -->
> <int name="hl.fragsize">200</int>
> <int name="hl.maxAnalyzedChars">409600</int>
> <!-- allow 50% slop on fragment sizes -->
> <float name="hl.regex.slop">0.5</float>
> <!-- a basic sentence pattern -->
> <str name="hl.regex.pattern">[-\w
> ,/\n\"']{20,200}</str>
> </lst>
> </fragmenter>
>
> </code>
>
> thanks!
>
>
> *--Evert*
>
> 2016-02-14 12:14 GMT-02:00 Binoy Dalal <binoydala...@gmail.com>:
>
> > From the solr wiki:
> > hl.maxAnalyzedChars
> >
> > How many characters into a document to look for suitable
> > snippets  Solr1.3. This parameter makes sense for the original
> Highlighter
> > only.
> >
> > The default value is "51200".
> >
> > You can assign a large value to this parameter and use hl.fragsize=0 to
> > return highlighting in large fields that have size greater than 51200
> > characters.
> >
> > I think this might be your hiccup.
> >
> > On Sun, 14 Feb 2016, 17:11 Evert R. <evert.ra...@gmail.com> wrote:
> >
> > > Hi Paul,
> > >
> > > Sorry my late reply.
> > >
> > > All the content is inside de docs. It brings the docs and the pdf file
> > that
> > > has the search word in it. But the highlight is not showing if the
> search
> > > word is after a few pages.
> > >
> > > Evert
> > >
> > >
> > > *--Evert*
> > >
> > > 2016-02-14 8:36 GMT-02:00 Paul Libbrecht <p...@hoplahup.net>:
> > >
> > > > This looks like the stored content is shortened. Can it be?
> > > > Can you see that inside the docs?
> > > >
> > > > paul
> > > >
> > > > > Evert R. <mailto:evert.ra...@gmail.com>
> > > > > 14 February 2016 at 11:26
> > > > > Hi There,
> > > > >
> > > > > I have a situation where started a techproducts, without any
> > > > modification,
> > > > > post a pdf file. When searching as:
> > > > >
> > > > > q=text:search_word
> > > > > hl=true
> > > > > hl.fl=content
> > > > >
> > > > > It show the highlight accordingly! =)
> > > > >
> > > > > BUT... *if the "search_word" is after the first pages* in my pdf
> > file,
> > > > > such
> > > > > as page 15...
> > > > >
> > > > > It simply *does not show* *the HIGHLIGHT*...
> > > > >
> > > > > Does anyone has faced this situation before?
> > > > >
> > > > >
> > > > > Thanks!
> > > > >
> > > > >
> > > > > *--Evert*
> > > > >
> > > >
> > > >
> > >
> > --
> > Regards,
> > Binoy Dalal
> >
>
--
Regards,
Binoy Dalal
