RE: highlighting not working as expected
Hi Edwin,
Thanks for your explanation, makes sense now.
Best regards
Martin
Internal - KMD A/S
-Original Message-
From: Zheng Lin Edwin Yeo
Sent: 30. juni 2019 01:57
To: solr-user@lucene.apache.org
Subject: Re: highlighting not working as expected
Hi,
If you are using the type "string", it will require exact match, including
space and upper/lower case.
You can use the type "text" for a start, but further down the road it will be
good to have your own custom fieldType with your own tokenizer and filter.
Regards,
Edwin
On Tue, 25 Jun 2019 at 14:52, Martin Frank Hansen (MHQ) wrote:
> Hi again,
>
> I have tested a bit and I was wondering if the highlighter requires a
> field to be of type "text"? Whenever I try highlighting on fields
> which are of type "string" nothing gets returned.
>
> Best regards
>
> Martin
>
>
> Internal - KMD A/S
>
> -Original Message-
> From: Jörn Franke
> Sent: 11. juni 2019 08:45
> To: solr-user@lucene.apache.org
> Subject: Re: highlighting not working as expected
>
> Could it be a stop word ? What is the exact type definition of those
> fields? Could this word be omitted or with wrong encoding during
> loading of the documents?
>
> > Am 03.06.2019 um 10:06 schrieb Martin Frank Hansen (MHQ) :
> >
> > Hi,
> >
> > I am having some difficulties making highlighting work. For some
> > reason
> the highlighting feature only works on some fields but not on other
> fields even though these fields are stored.
> >
> > An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagst
> itel=Sagstitel=%3C/b%3E=%3Cb%3E=
> on=rotte
> >
> > It simply returns an empty set, for all documents even though I can
> > see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
> >
> > I am using the standard highlighter as below.
> >
> >
> >
> >
> >
> >
> > > default="true"
> > class="solr.highlight.GapFragmenter">
> >
> > 100
> >
> >
> >
> >
> > > class="solr.highlight.RegexFragmenter">
> >
> >
> > 70
> >
> > 0.5
> >
> > [-\w
> ,/\n\]{20,200}
> >
> >
> >
> >
> > > default="true"
> > class="solr.highlight.HtmlFormatter">
> >
> > b
> > /b
> >
> >
> >
> >
> > > class="solr.highlight.HtmlEncoder" />
> >
> >
> > > class="solr.highlight.SimpleFragListBuilder"/>
> >
> >
> > > class="solr.highlight.SingleFragListBuilder"/>
> >
> >
> > > default="true"
> >
> > class="solr.highlight.WeightedFragListBuilder"/>
> >
> >
> > >default="true"
> >class="solr.highlight.ScoreOrderFragmentsBuilder">
> >
> >
> >
> >
> > >class="solr.highlight.ScoreOrderFragmentsBuilder">
> >
> >
> >
> >
> >
> >
> > > default="true"
> > class="solr.highlight.SimpleBoundaryScanner">
> >
> > 10
> > .,!?
> >
> >
> >
> > >
> class="solr.highlight.BreakIteratorBoundaryScanner">
> >
> >
> > WORD
> >
> >
> > da
> >
> >
> >
> >
> >
> > Hope that some one can help, thanks in advance.
> >
> > Best regards
> > Martin
> >
> >
> >
> > Internal - KMD A/S
> >
> > Beskyttelse af dine personlige oplysninger er vigtig for os. Her
> > finder
> du KMD’s Privatlivspolitik<http://www.kmd.dk/Privatlivspolitik>, der
> fortæller, hvordan vi behandler oplysninger om dig.
> >
> > Protection of your personal dat
Re: highlighting not working as expected
Hi,
If you are using the type "string", it will require exact match, including
space and upper/lower case.
You can use the type "text" for a start, but further down the road it will
be good to have your own custom fieldType with your own tokenizer and
filter.
Regards,
Edwin
On Tue, 25 Jun 2019 at 14:52, Martin Frank Hansen (MHQ) wrote:
> Hi again,
>
> I have tested a bit and I was wondering if the highlighter requires a
> field to be of type "text"? Whenever I try highlighting on fields which are
> of type "string" nothing gets returned.
>
> Best regards
>
> Martin
>
>
> Internal - KMD A/S
>
> -Original Message-
> From: Jörn Franke
> Sent: 11. juni 2019 08:45
> To: solr-user@lucene.apache.org
> Subject: Re: highlighting not working as expected
>
> Could it be a stop word ? What is the exact type definition of those
> fields? Could this word be omitted or with wrong encoding during loading of
> the documents?
>
> > Am 03.06.2019 um 10:06 schrieb Martin Frank Hansen (MHQ) :
> >
> > Hi,
> >
> > I am having some difficulties making highlighting work. For some reason
> the highlighting feature only works on some fields but not on other fields
> even though these fields are stored.
> >
> > An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
> >
> > It simply returns an empty set, for all documents even though I can see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
> >
> > I am using the standard highlighter as below.
> >
> >
> >
> >
> >
> >
> > > default="true"
> > class="solr.highlight.GapFragmenter">
> >
> > 100
> >
> >
> >
> >
> > > class="solr.highlight.RegexFragmenter">
> >
> >
> > 70
> >
> > 0.5
> >
> > [-\w
> ,/\n\]{20,200}
> >
> >
> >
> >
> > > default="true"
> > class="solr.highlight.HtmlFormatter">
> >
> > b
> > /b
> >
> >
> >
> >
> > > class="solr.highlight.HtmlEncoder" />
> >
> >
> > > class="solr.highlight.SimpleFragListBuilder"/>
> >
> >
> > > class="solr.highlight.SingleFragListBuilder"/>
> >
> >
> > > default="true"
> > class="solr.highlight.WeightedFragListBuilder"/>
> >
> >
> > >default="true"
> >class="solr.highlight.ScoreOrderFragmentsBuilder">
> >
> >
> >
> >
> > >class="solr.highlight.ScoreOrderFragmentsBuilder">
> >
> >
> >
> >
> >
> >
> > > default="true"
> > class="solr.highlight.SimpleBoundaryScanner">
> >
> > 10
> > .,!?
> >
> >
> >
> > >
> class="solr.highlight.BreakIteratorBoundaryScanner">
> >
> >
> > WORD
> >
> >
> > da
> >
> >
> >
> >
> >
> > Hope that some one can help, thanks in advance.
> >
> > Best regards
> > Martin
> >
> >
> >
> > Internal - KMD A/S
> >
> > Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder
> du KMD’s Privatlivspolitik<http://www.kmd.dk/Privatlivspolitik>, der
> fortæller, hvordan vi behandler oplysninger om dig.
> >
> > Protection of your personal data is important to us. Here you can read
> KMD’s Privacy Policy<http://www.kmd.net/Privacy-Policy> outlining how we
> process your personal data.
> >
> > Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig
> information. Hvis du ved en fejltagelse modtager e-mail
RE: highlighting not working as expected
Hi again,
I have tested a bit and I was wondering if the highlighter requires a field to
be of type "text"? Whenever I try highlighting on fields which are of type
"string" nothing gets returned.
Best regards
Martin
Internal - KMD A/S
-Original Message-
From: Jörn Franke
Sent: 11. juni 2019 08:45
To: solr-user@lucene.apache.org
Subject: Re: highlighting not working as expected
Could it be a stop word ? What is the exact type definition of those fields?
Could this word be omitted or with wrong encoding during loading of the
documents?
> Am 03.06.2019 um 10:06 schrieb Martin Frank Hansen (MHQ) :
>
> Hi,
>
> I am having some difficulties making highlighting work. For some reason the
> highlighting feature only works on some fields but not on other fields even
> though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
>
> It simply returns an empty set, for all documents even though I can see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
>default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
>class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.WeightedFragListBuilder"/>
>
>
> default="true"
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
> class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder du
> KMD’s Privatlivspolitik<http://www.kmd.dk/Privatlivspolitik>, der fortæller,
> hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read KMD’s
> Privacy Policy<http://www.kmd.net/Privacy-Policy> outlining how we process
> your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere
> afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi dig slette
> e-mailen i dit system uden at videresende eller kopiere den. Selvom e-mailen
> og ethvert vedhæftet bilag efter vores overbevisning er fri for virus og
> andre fejl, som kan påvirke computeren eller it-systemet, hvori den modtages
> og læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget
> ansvar for tab og skade, som er opstået i forbindelse med at modtage og bruge
> e-mailen.
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake by sending a reply, then delete the message from your system without
> making, distributing or retaining any copies of it. Although we believe that
> the message and any attachments are free from viruses and other errors that
> might affect the computer or it-system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of this
> message.
RE: highlighting not working as expected
Hi Edwin,
Yes the field is defined just like the other fields:
BR
Martin
Internal - KMD A/S
-Original Message-
From: Zheng Lin Edwin Yeo
Sent: 4. juni 2019 10:32
To: solr-user@lucene.apache.org
Subject: Re: highlighting not working as expected
Hi Martin,
What fieldType are you using for the field “Sagstitel”? Is it the same as other
fields?
Regards,
Edwin
On Mon, 3 Jun 2019 at 16:06, Martin Frank Hansen (MHQ) wrote:
> Hi,
>
> I am having some difficulties making highlighting work. For some
> reason the highlighting feature only works on some fields but not on
> other fields even though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagst
> itel=Sagstitel=%3C/b%3E=%3Cb%3E=
> on=rotte
>
> It simply returns an empty set, for all documents even though I can
> see several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
> default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
> class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w
> ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
> default="true"
>
> class="solr.highlight.WeightedFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
>class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her
> finder du KMD’s
> Privatlivspolitik<http://www.kmd.dk/Privatlivspolitik>, der fortæller,
> hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read
> KMD’s Privacy Policy<http://www.kmd.net/Privacy-Policy> outlining how
> we process your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst
> informere afsender om fejlen ved at bruge svarfunktionen. Samtidig
> beder vi dig slette e-mailen i dit system uden at videresende eller kopiere
> den.
> Selvom e-mailen og ethvert vedhæftet bilag efter vores overbevisning
> er fri for virus og andre fejl, som kan påvirke computeren eller
> it-systemet, hvori den modtages og læses, åbnes den på modtagerens
> eget ansvar. Vi påtager os ikke noget ansvar for tab og skade, som er
> opstået i forbindelse med at modtage og bruge e-mailen.
>
> Please note that this message may contain confidential information. If
> you have received this message by mistake, please inform the sender of
> the mistake by sending a reply, then delete the message from your
> system without making, distributing or retaining any copies of it.
> Although we believe that the message and any attachments are free from
> viruses and other errors that might affect the computer or it-system
> where it is received and read, the recipient opens the message at his or her
> own risk.
> We assume no responsibility for any loss or damage arising from the
> receipt or use of this message.
>
RE: highlighting not working as expected
Hi Jörn,
Thanks for your input!
I do not use stop-words, so that should not be the issue. The encoding of the
documents might be an issue, as they come in many different file formats. It
will however need to test this.
The field is defined as below:
BR
Martin
Internal - KMD A/S
-Original Message-
From: Jörn Franke
Sent: 11. juni 2019 08:45
To: solr-user@lucene.apache.org
Subject: Re: highlighting not working as expected
Could it be a stop word ? What is the exact type definition of those fields?
Could this word be omitted or with wrong encoding during loading of the
documents?
> Am 03.06.2019 um 10:06 schrieb Martin Frank Hansen (MHQ) :
>
> Hi,
>
> I am having some difficulties making highlighting work. For some reason the
> highlighting feature only works on some fields but not on other fields even
> though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
>
> It simply returns an empty set, for all documents even though I can see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
>default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
>class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.WeightedFragListBuilder"/>
>
>
> default="true"
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
> class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder du
> KMD’s Privatlivspolitik<http://www.kmd.dk/Privatlivspolitik>, der fortæller,
> hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read KMD’s
> Privacy Policy<http://www.kmd.net/Privacy-Policy> outlining how we process
> your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere
> afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi dig slette
> e-mailen i dit system uden at videresende eller kopiere den. Selvom e-mailen
> og ethvert vedhæftet bilag efter vores overbevisning er fri for virus og
> andre fejl, som kan påvirke computeren eller it-systemet, hvori den modtages
> og læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget
> ansvar for tab og skade, som er opstået i forbindelse med at modtage og bruge
> e-mailen.
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake by sending a reply, then delete the message from your system without
> making, distributing or retaining any copies of it. Although we believe that
> the message and any attachments are free from viruses and other errors that
> might affect the computer or it-system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of this
> message.
Re: highlighting not working as expected
Could it be a stop word ? What is the exact type definition of those fields?
Could this word be omitted or with wrong encoding during loading of the
documents?
> Am 03.06.2019 um 10:06 schrieb Martin Frank Hansen (MHQ) :
>
> Hi,
>
> I am having some difficulties making highlighting work. For some reason the
> highlighting feature only works on some fields but not on other fields even
> though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
>
> It simply returns an empty set, for all documents even though I can see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
>default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
>class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.WeightedFragListBuilder"/>
>
>
> default="true"
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
> class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder du
> KMD’s Privatlivspolitik, der fortæller,
> hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read KMD’s
> Privacy Policy outlining how we process
> your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere
> afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi dig slette
> e-mailen i dit system uden at videresende eller kopiere den. Selvom e-mailen
> og ethvert vedhæftet bilag efter vores overbevisning er fri for virus og
> andre fejl, som kan påvirke computeren eller it-systemet, hvori den modtages
> og læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget
> ansvar for tab og skade, som er opstået i forbindelse med at modtage og bruge
> e-mailen.
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake by sending a reply, then delete the message from your system without
> making, distributing or retaining any copies of it. Although we believe that
> the message and any attachments are free from viruses and other errors that
> might affect the computer or it-system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of this
> message.
RE: highlighting not working as expected
Hi David,
Thanks for your response and sorry my late reply.
Still the same result when using hl.method=unified.
Best regards
Martin
Internal - KMD A/S
-Original Message-
From: David Smiley
Sent: 10. juni 2019 16:48
To: solr-user
Subject: Re: highlighting not working as expected
Please try hl.method=unified and tell us if that helps.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Jun 3, 2019 at 4:06 AM Martin Frank Hansen (MHQ) wrote:
> Hi,
>
> I am having some difficulties making highlighting work. For some
> reason the highlighting feature only works on some fields but not on
> other fields even though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagst
> itel=Sagstitel=%3C/b%3E=%3Cb%3E=
> on=rotte
>
> It simply returns an empty set, for all documents even though I can
> see several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
> default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
> class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w
> ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
> default="true"
>
> class="solr.highlight.WeightedFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
>class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her
> finder du KMD’s
> Privatlivspolitik<http://www.kmd.dk/Privatlivspolitik>, der fortæller,
> hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read
> KMD’s Privacy Policy<http://www.kmd.net/Privacy-Policy> outlining how
> we process your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst
> informere afsender om fejlen ved at bruge svarfunktionen. Samtidig
> beder vi dig slette e-mailen i dit system uden at videresende eller kopiere
> den.
> Selvom e-mailen og ethvert vedhæftet bilag efter vores overbevisning
> er fri for virus og andre fejl, som kan påvirke computeren eller
> it-systemet, hvori den modtages og læses, åbnes den på modtagerens
> eget ansvar. Vi påtager os ikke noget ansvar for tab og skade, som er
> opstået i forbindelse med at modtage og bruge e-mailen.
>
> Please note that this message may contain confidential information. If
> you have received this message by mistake, please inform the sender of
> the mistake by sending a reply, then delete the message from your
> system without making, distributing or retaining any copies of it.
> Although we believe that the message and any attachments are free from
> viruses and other errors that might affect the computer or it-system
> where it is received and read, the recipient opens the message at his or her
> own risk.
> We assume no responsibility for any loss or damage arising from the
> receipt or use of this message.
>
Re: highlighting not working as expected
Please try hl.method=unified and tell us if that helps.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Jun 3, 2019 at 4:06 AM Martin Frank Hansen (MHQ) wrote:
> Hi,
>
> I am having some difficulties making highlighting work. For some reason
> the highlighting feature only works on some fields but not on other fields
> even though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
>
> It simply returns an empty set, for all documents even though I can see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
> default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
> class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w
> ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
> default="true"
>class="solr.highlight.WeightedFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
>class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder du
> KMD’s Privatlivspolitik, der
> fortæller, hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read
> KMD’s Privacy Policy outlining how we
> process your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst
> informere afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi
> dig slette e-mailen i dit system uden at videresende eller kopiere den.
> Selvom e-mailen og ethvert vedhæftet bilag efter vores overbevisning er fri
> for virus og andre fejl, som kan påvirke computeren eller it-systemet,
> hvori den modtages og læses, åbnes den på modtagerens eget ansvar. Vi
> påtager os ikke noget ansvar for tab og skade, som er opstået i forbindelse
> med at modtage og bruge e-mailen.
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake by sending a reply, then delete the message from your system
> without making, distributing or retaining any copies of it. Although we
> believe that the message and any attachments are free from viruses and
> other errors that might affect the computer or it-system where it is
> received and read, the recipient opens the message at his or her own risk.
> We assume no responsibility for any loss or damage arising from the receipt
> or use of this message.
>
Re: highlighting not working as expected
Hi Martin,
What fieldType are you using for the field “Sagstitel”? Is it the same as
other fields?
Regards,
Edwin
On Mon, 3 Jun 2019 at 16:06, Martin Frank Hansen (MHQ) wrote:
> Hi,
>
> I am having some difficulties making highlighting work. For some reason
> the highlighting feature only works on some fields but not on other fields
> even though these fields are stored.
>
> An example of a request looks like this:
> http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
>
> It simply returns an empty set, for all documents even though I can see
> several documents which have “Sagstitel” containing the word “rotte”
> (rotte=rat). What am I missing here?
>
> I am using the standard highlighter as below.
>
>
>
>
>
>
> default="true"
> class="solr.highlight.GapFragmenter">
>
> 100
>
>
>
>
> class="solr.highlight.RegexFragmenter">
>
>
> 70
>
> 0.5
>
> [-\w
> ,/\n\]{20,200}
>
>
>
>
> default="true"
> class="solr.highlight.HtmlFormatter">
>
> b
> /b
>
>
>
>
> class="solr.highlight.HtmlEncoder" />
>
>
> class="solr.highlight.SimpleFragListBuilder"/>
>
>
> class="solr.highlight.SingleFragListBuilder"/>
>
>
> default="true"
>class="solr.highlight.WeightedFragListBuilder"/>
>
>
>default="true"
> class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>class="solr.highlight.ScoreOrderFragmentsBuilder">
>
>
>
>
>
>
> default="true"
>class="solr.highlight.SimpleBoundaryScanner">
>
> 10
> .,!?
>
>
>
> class="solr.highlight.BreakIteratorBoundaryScanner">
>
>
> WORD
>
>
> da
>
>
>
>
>
> Hope that some one can help, thanks in advance.
>
> Best regards
> Martin
>
>
>
> Internal - KMD A/S
>
> Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder du
> KMD’s Privatlivspolitik, der
> fortæller, hvordan vi behandler oplysninger om dig.
>
> Protection of your personal data is important to us. Here you can read
> KMD’s Privacy Policy outlining how we
> process your personal data.
>
> Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information.
> Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst
> informere afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi
> dig slette e-mailen i dit system uden at videresende eller kopiere den.
> Selvom e-mailen og ethvert vedhæftet bilag efter vores overbevisning er fri
> for virus og andre fejl, som kan påvirke computeren eller it-systemet,
> hvori den modtages og læses, åbnes den på modtagerens eget ansvar. Vi
> påtager os ikke noget ansvar for tab og skade, som er opstået i forbindelse
> med at modtage og bruge e-mailen.
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake by sending a reply, then delete the message from your system
> without making, distributing or retaining any copies of it. Although we
> believe that the message and any attachments are free from viruses and
> other errors that might affect the computer or it-system where it is
> received and read, the recipient opens the message at his or her own risk.
> We assume no responsibility for any loss or damage arising from the receipt
> or use of this message.
>
highlighting not working as expected
Hi,
I am having some difficulties making highlighting work. For some reason the
highlighting feature only works on some fields but not on other fields even
though these fields are stored.
An example of a request looks like this:
http://localhost/solr/mytest/select?fl=id,doc.Type,Journalnummer,Sagstitel=Sagstitel=%3C/b%3E=%3Cb%3E=on=rotte
It simply returns an empty set, for all documents even though I can see several
documents which have “Sagstitel” containing the word “rotte” (rotte=rat). What
am I missing here?
I am using the standard highlighter as below.
100
70
0.5
[-\w ,/\n\]{20,200}
b
/b
10
.,!?
WORD
da
Hope that some one can help, thanks in advance.
Best regards
Martin
Internal - KMD A/S
Beskyttelse af dine personlige oplysninger er vigtig for os. Her finder du
KMD’s Privatlivspolitik, der fortæller,
hvordan vi behandler oplysninger om dig.
Protection of your personal data is important to us. Here you can read KMD’s
Privacy Policy outlining how we process your
personal data.
Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information. Hvis
du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere
afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi dig slette
e-mailen i dit system uden at videresende eller kopiere den. Selvom e-mailen og
ethvert vedhæftet bilag efter vores overbevisning er fri for virus og andre
fejl, som kan påvirke computeren eller it-systemet, hvori den modtages og
læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget ansvar
for tab og skade, som er opstået i forbindelse med at modtage og bruge e-mailen.
Please note that this message may contain confidential information. If you have
received this message by mistake, please inform the sender of the mistake by
sending a reply, then delete the message from your system without making,
distributing or retaining any copies of it. Although we believe that the
message and any attachments are free from viruses and other errors that might
affect the computer or it-system where it is received and read, the recipient
opens the message at his or her own risk. We assume no responsibility for any
loss or damage arising from the receipt or use of this message.
Re: Urgent! Highlighting not working as expected
copyField is a literal operation that happens at index time -- but it really has no bearing what so ever on highlighting done at query time. there is no memory of what source fields any values came from, so it doesn't affect things in any way. You haven't provided any details about your schema, but i suspect the reason you are only seeing highlights in the cr_name field (and not any other field containing the value) is because highlighting can only work if the field value is stored... http://wiki.apache.org/solr/FieldOptionsByUseCase ...if your text field is stored=false, then solr can't highlight it at all, so it is never even considered when you use hl.fl=* : I queried Solr (3.5) with this: q=text:G-Moneyhl=truehl.fl=*, where text : is a text field and all the other fields were copied to it. I got three : records returned, however, only one field (also text field) was : highlighted: : lst name=highlighting : lst name=cr_149107 : arr name=cr_name : stremG-MONEY/em HETZEL/str : /arr : /lst : lst name=cr_740953/ : lst name=cr_1055847/ : /lst : : But the other two also have matched fields (that is why they are returned), : but they are string field, they were not highlighted. Also, in the same : record cr_149107, the string field cr_firstname has exactly matched : string G-Money, but it was not highlighted. But if I search on this field: : q=cr_firstname:G-Moneyhl=truehl.fl=*, it will be highlighted. Any idea : what shall I do to let both text and string fields highlighted? -Hoss
Re: Urgent! Highlighting not working as expected
Hi Jack, Thanks for your reply. I did not specify dismax when query with highlighting enabled: q=text:G-Moneyhl=truehl.fl=*, that was the whole query string I sent. What puzzled me is that the string field cr_firstname was copied to text, but it was not highlighted. But if I use q=cr_fristname:G-Moneyhl=truehl.fl=*, it will be highlighted. I attached my solrconfig.xml here, could you please take a look? Thanks again! http://lucene.472066.n3.nabble.com/file/n3983883/solrconfig.xml solrconfig.xml -- View this message in context: http://lucene.472066.n3.nabble.com/Urgent-Highlighting-not-working-as-expected-tp3983755p3983883.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Urgent! Highlighting not working as expected
In the case of text:G-Money, the term is analyzed by Solr into the phrase g money, which matches in the text field, but will not match for a string field containing the literal text G-Money. But when you query cr_fristname:G-Money, the term is not tokenized by the Solr analyzer because it is a value for a string field, and a literal match occurs in the string field cr_fristname. I think that fully accounts for the behavior you see. You might consider having a cr_fristname_text field which is tokenized text with a copyField from cr_fristname that fully supports highlighting of text terms. BTW, I presume that should be first name, not frist name. -- Jack Krupansky -Original Message- From: TJ Tong Sent: Tuesday, May 15, 2012 11:15 AM To: solr-user@lucene.apache.org Subject: Re: Urgent! Highlighting not working as expected Hi Jack, Thanks for your reply. I did not specify dismax when query with highlighting enabled: q=text:G-Moneyhl=truehl.fl=*, that was the whole query string I sent. What puzzled me is that the string field cr_firstname was copied to text, but it was not highlighted. But if I use q=cr_fristname:G-Moneyhl=truehl.fl=*, it will be highlighted. I attached my solrconfig.xml here, could you please take a look? Thanks again! http://lucene.472066.n3.nabble.com/file/n3983883/solrconfig.xml solrconfig.xml -- View this message in context: http://lucene.472066.n3.nabble.com/Urgent-Highlighting-not-working-as-expected-tp3983755p3983883.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Urgent! Highlighting not working as expected
Thanks, Jack! I think you are right. But I also copied cr_firstname to text, I assumed Solr would highlight cr_firstname if there is a match. I guess the only solution is to copy all field to another field which is not tokenized. Yes, it is firstname, good catch! Thanks again! TJ -- View this message in context: http://lucene.472066.n3.nabble.com/Urgent-Highlighting-not-working-as-expected-tp3983755p3983907.html Sent from the Solr - User mailing list archive at Nabble.com.
Urgent! Highlighting not working as expected
Dear all, I queried Solr (3.5) with this: q=text:G-Moneyhl=truehl.fl=*, where text is a text field and all the other fields were copied to it. I got three records returned, however, only one field (also text field) was highlighted: lst name=highlighting lst name=cr_149107 arr name=cr_name stremG-MONEY/em HETZEL/str /arr /lst lst name=cr_740953/ lst name=cr_1055847/ /lst But the other two also have matched fields (that is why they are returned), but they are string field, they were not highlighted. Also, in the same record cr_149107, the string field cr_firstname has exactly matched string G-Money, but it was not highlighted. But if I search on this field: q=cr_firstname:G-Moneyhl=truehl.fl=*, it will be highlighted. Any idea what shall I do to let both text and string fields highlighted? Thanks in advance! -- View this message in context: http://lucene.472066.n3.nabble.com/Urgent-Highlighting-not-working-as-expected-tp3983755.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Urgent! Highlighting not working as expected
The highlighting will be based only on the fields in which matching occurred. Are you using edismax and with multiple fields in qf, or the traditional Solr (Lucene) query parser that only matches in the default field or an explicit field? -- Jack Krupansky -Original Message- From: TJ Tong Sent: Monday, May 14, 2012 4:44 PM To: solr-user@lucene.apache.org Subject: Urgent! Highlighting not working as expected Dear all, I queried Solr (3.5) with this: q=text:G-Moneyhl=truehl.fl=*, where text is a text field and all the other fields were copied to it. I got three records returned, however, only one field (also text field) was highlighted: lst name=highlighting lst name=cr_149107 arr name=cr_name stremG-MONEY/em HETZEL/str /arr /lst lst name=cr_740953/ lst name=cr_1055847/ /lst But the other two also have matched fields (that is why they are returned), but they are string field, they were not highlighted. Also, in the same record cr_149107, the string field cr_firstname has exactly matched string G-Money, but it was not highlighted. But if I search on this field: q=cr_firstname:G-Moneyhl=truehl.fl=*, it will be highlighted. Any idea what shall I do to let both text and string fields highlighted? Thanks in advance! -- View this message in context: http://lucene.472066.n3.nabble.com/Urgent-Highlighting-not-working-as-expected-tp3983755.html Sent from the Solr - User mailing list archive at Nabble.com.
