[BUG] lte of text fields is broken

[roopeux]

Describe the bug

lte in queries like this matches any field that has any numbers

{
  "query": {
    "range": {
      "test": {
        "lte": 700
      }
    }
  }
}

Related component

Other

To Reproduce

# Delete test index
DELETE lte_test

# Create test documents
POST lte_test/_doc/1
{
  "test": "500"
}

POST lte_test/_doc/2
{
  "test": "1000" 
}

POST lte_test/_doc/3
{
  "test": "foo" 
}

POST lte_test/_doc/4
{
  "test": "1000 foo" 
}

# Force refresh
POST lte_test/_refresh

# Test range query
GET lte_test/_search
{
  "query": {
    "range": {
      "test": {
        "lte": 700
      }
    }
  }
}

This will match any test field that has any number

{
  "took": 463,
  "timed_out": false,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 3,
      "relation": "eq"
    },
    "max_score": 1,
    "hits": [
      {
        "_index": "date_test",
        "_id": "1",
        "_score": 1,
        "_source": {
          "test": "500"
        }
      },
      {
        "_index": "date_test",
        "_id": "2",
        "_score": 1,
        "_source": {
          "test": "1000"
        }
      },
      {
        "_index": "date_test",
        "_id": "4",
        "_score": 1,
        "_source": {
          "test": "1000 foo"
        }
      }
    ]
  }
}

Expected behavior

Return doc 1 since 500 is less 700.
Should not return doc 2 since 1000 is not less than 700.
Should not return doc 4, since 1000 is not less than 700 and maybe because of mixed content.

Additional Details

There is a similar bug in aggs, where range with lte or gte matches everything

[gaobinlong]

If you didn't set the mapping of the field test to numeric type like long or integer, then the field will be mapped into text type plus a keyword type subfield, so at this point, performing range query will check the lexicographic order.

Performing range query on text or keyword field is not recommended, you should explicitly set the mapping before indexing documents into OpenSearch:

PUT test1/_mapping
{
  "properties":{
    "test":{
      "type":"integer"
    }
  }
}