Currently we always use the "standard" analyzer when mapping analyzed fields. It should be possible to apply specific analyzers defined in Elasticsearch for specific given fields.
See these resources:
* https://www.elastic.co/guide/en/elasticsearch/guide/current/mapping-intro.html#_analyzer
* https://www.elastic.co/guide/en/elasticsearch/guide/current/custom-analyzers.html
Being able to refer to built-in analyzers could be a first step, support for custom-defined ones a second step. AFAIU, analyzer definitions are bound to specific indexes, so we'd need a way to pass in analyzer definitions when creating an index for that (when letting HSEARCH deal with index creation). |
|