CreateIndexRequest with raw JSON and "limit token count token filter" fails if optional parameter is missing #313
Labels
Area: Specification
Related to the API spec used to generate client code
Comments
swallez
added
the
Area: Specification
|
Working around the |
|
Facing the same issue, and my workaround was to:
Subsequent GetIndex request via Java client no longer errors. |
|
This has been fixed in PR #344, which will be included in versions 8.4.0 and 7.17.6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Java API client version
7.17.4
Java version
1.8.0_332
Elasticsearch Version
7.17.4
Problem description
We have index mappings stored as JSON files and have successfully used
RestHighLevelClientlike this:We're now trying to migrate away from
RestHighLevelClientto something like this:But with the JSON below, we get an exception like this:
Even though the documentation on https://www.elastic.co/guide/en/elasticsearch/reference/7.17/analysis-limit-token-count-tokenfilter.html#analysis-limit-token-count-tokenfilter-configure-parms states that
consume_all_tokensis optional. It works fine if"consume_all_tokens": falseis added to theone_token_limitfilter.This is a stripped down mapping JSON that fails:
{ "mappings": { "properties": { "id": { "type": "keyword" } }, "dynamic_templates": [ { "metadata_title_en": { "path_match": "metadata.en.title", "mapping": { "type": "text", "fields": { "first_word": { "type": "text", "fielddata": true, "analyzer": "first_word", "search_analyzer": "standard" } } } } } ] }, "settings": { "index": { "analysis": { "analyzer": { "first_word": { "type": "custom", "tokenizer": "standard", "filter": [ "lowercase", "one_token_limit" ] } }, "normalizer": { "lowercase": { "type": "custom", "filter": [ "lowercase" ] } }, "filter": { "one_token_limit": { "type": "limit", "max_token_count": 1 } } } } } }The text was updated successfully, but these errors were encountered: