[BUG] `term_vector` does not work on `search_as_you_type` fields · opensearch-project/OpenSearch#1901

2022-01-14T01:57:47.000Z

**Describe the bug** TL;DR: same issue reported [here](https://github.com/elastic/elasticsearch/issues/66407). Per ElasticSearch's 7.10 [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/search-as-you-type.html#general-params) (which AFAICT should be compatible with OpenSearch 1.x), setting `term_vector` on a `search_as_you_type` field should only affect the shingle subfields, but not the index prefix subfield. However, when attempting to index documents with this mapping, an `illegal_argument_exception` is thrown. **To Reproduce** Steps to reproduce the behavior: 1. Create a new index with the following mapping: ```jsonc { // ... "my_field": "type": "search_as_you_type", "term_vector": "with_positions_offsets" // ... } ``` 2. Attempt to index a document containing a `my_field` field 3. Observe the following error: ```json { "type": "illegal_argument_exception", "reason": "cannot index term vector offsets when term vectors are not indexed (field=\"my_field._index_prefix\")" } ``` **Expected behavior** Documents should be indexed without issue. Only the `._2gram` and `._3gram` shingle subfields should have the `term_vector` set, and not the `._index_prefix` n-gram subfield. **Plugins** N/A **Screenshots** N/A **Host/Environment** - Version: 1.2.3 (opensearchproject/opensearch:latest)

(12 Kommentare) (3 Reaktionen) (1 zugewiesene Person)Java (1.505 Forks)batch import

Search:Relevancebuggood first issuehacktoberfest

Repository-Metriken

Stars: (8.123 Stars)
PR-Merge-Metriken: (Durchschn. Merge 5T 9h) (266 gemergte PRs in 30 T)

Beschreibung

Describe the bug TL;DR: same issue reported here.

Per ElasticSearch's 7.10 documentation (which AFAICT should be compatible with OpenSearch 1.x), setting term_vector on a search_as_you_type field should only affect the shingle subfields, but not the index prefix subfield. However, when attempting to index documents with this mapping, an illegal_argument_exception is thrown.

To Reproduce Steps to reproduce the behavior:

Create a new index with the following mapping:

{
  // ...
  "my_field":
    "type": "search_as_you_type",
    "term_vector": "with_positions_offsets"
  // ...
}

Attempt to index a document containing a my_field field
Observe the following error:

{
  "type": "illegal_argument_exception",
  "reason": "cannot index term vector offsets when term vectors are not indexed (field=\"my_field._index_prefix\")"
}

Expected behavior Documents should be indexed without issue. Only the ._2gram and ._3gram shingle subfields should have the term_vector set, and not the ._index_prefix n-gram subfield.

Plugins N/A

Screenshots N/A

Host/Environment

Version: 1.2.3 (opensearchproject/opensearch:latest)

Contributor Guide

Research-Richtung: Das Problem reproduziert einen Bug, bei dem term vector auf search as you type Feldern eine illegal argument exception auf dem index prefix Unterfeld verursacht. Das erwartete Verhalten ist, dass term vector nur auf shingle Unterfelder angewendet werden sollte. Untersuche den OpenSearch Mapping Code, wahrscheinlich in der Mapper oder SearchAsYouTypeFieldMapper Klasse. Siehe das verlinkte Elasticsearch Issue (elastic/elasticsearch#66407) für einen möglichen Fix. Überprüfe die Kommentare im Issue für Anleitungen der Maintainer. Die Lösung könnte das Ändern des Parsings von term vector beinhalten, um das index prefix Unterfeld in der Mapping Einrichtung auszuschließen.
Tech Stack: java
Domain: backendsearch
Issue Type: Fehler
Schwierigkeit: 3
Geschätzte Zeit: Halber Tag
Aktivitätsstatus: Aktiv
Klarheit: Klar
Voraussetzungen: JavaGit
Einsteigerfreundlichkeit: 70

Repository-Metriken

Beschreibung

Contributor Guide

Erhalte frische Easy Issues per E-Mail.