fixed elements in array of produced terms

[manonthemat]

No description provided.

[manonthemat]

While reading through https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-pattern-replace-charfilter.html, I found the claim that a filter

{
  "settings": {
    "analysis": {
      "analyzer": {
        "my_analyzer": {
          "tokenizer": "standard",
          "char_filter": [
            "my_char_filter"
          ]
        }
      },
      "char_filter": {
        "my_char_filter": {
          "type": "pattern_replace",
          "pattern": "(\\d+)-(?=\\d)",
          "replacement": "$1_"
        }
      }
    }
  }
}

with a document of

{
  "analyzer": "my_analyzer",
  "text": "My credit card is 123-456-789"
}

does in fact create these tokens:

{
    "tokens": [
        {
            "token": "My",
            "start_offset": 0,
            "end_offset": 2,
            "type": "<ALPHANUM>",
            "position": 0
        },
        {
            "token": "credit",
            "start_offset": 3,
            "end_offset": 9,
            "type": "<ALPHANUM>",
            "position": 1
        },
        {
            "token": "card",
            "start_offset": 10,
            "end_offset": 14,
            "type": "<ALPHANUM>",
            "position": 2
        },
        {
            "token": "is",
            "start_offset": 15,
            "end_offset": 17,
            "type": "<ALPHANUM>",
            "position": 3
        },
        {
            "token": "123_456_789",
            "start_offset": 18,
            "end_offset": 29,
            "type": "<NUM>",
            "position": 4
        }
    ]
}

As you can see "is" and "123_456_789" are separate terms, thus the small change of a added comma in the doc.

[elasticmachine]

Pinging @elastic/es-search-aggs

[dnhatn]

@elasticmachine test this please

[mayya-sharipova]

@manonthemat thanks for your PR! well noticed error!