Plain Highlighter using document-defined analyzer

We have recently encountered a problem with item highlighting when we
changed the way we define analysers.

In short, the problem boiled down to PlainHighlighter using analyser for
the document type. while we
specify analyser on per-document basis. '_analyzer' field is not used (or,
from my debugging, even visible) in the highlighter context. As a temporary
solution, I made highlighter use the field to which '_analyzer' points
to(via path) in the mappings we use,

My attempt at it is over here:

There are a couple of issues that I am seeking help with:

  1. Does this seem like an about - right approach to dealing with the
    situation?
  2. Analyzer field name is hardcoded, as I was unable to figure out how to
    get it from the document in the correct way (again, the right field is
    pointed to in '_analyzer' via path). Any suggestions how to do it properly?

Regards,
Mateusz Kaczyński

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7bbf3576-5fb1-44d1-badd-90f6b6cdf2d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Any thoughts on this?

On Tuesday, 13 May 2014 16:22:13 UTC, Mateusz Kaczynski wrote:

We have recently encountered a problem with item highlighting when we
changed the way we define analysers.

In short, the problem boiled down to PlainHighlighter using analyser for
the document type. while we
specify analyser on per-document basis. '_analyzer' field is not used (or,
from my debugging, even visible) in the highlighter context. As a temporary
solution, I made highlighter use the field to which '_analyzer' points
to(via path) in the mappings we use,

My attempt at it is over here:

Plain highlighter should use document 'language_analyzer' field to de… · arachnys/elasticsearch@8082fca · GitHub

There are a couple of issues that I am seeking help with:

  1. Does this seem like an about - right approach to dealing with the
    situation?
  2. Analyzer field name is hardcoded, as I was unable to figure out how to
    get it from the document in the correct way (again, the right field is
    pointed to in '_analyzer' via path). Any suggestions how to do it properly?

Regards,
Mateusz Kaczyński

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d2962d64-26d6-4984-835a-e6b3bee7731c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.