trino table column is case Insensetive for elasticsearch connector

[waitingF]

While using trino to perform sql base on Elasticsearch cluster, I found presto is NOT case sensetive for columns. For Example, I have an Index in elasticsearch with mapping like(with fields[age, Age, name, Name]):

{
  "myindex" : {
    "mappings" : {
      "properties" : {
        "Age" : {
          "type" : "long"
        },
        "Name" : {
          "type" : "keyword"
        },
        "age" : {
          "type" : "long"
        },
        "name" : {
          "type" : "keyword"
        }
      }
    }
  }
}

When use "DESC myindex" in trino-cli, it shows nothing:

Then, I dive into elasticsearch connector plugin, I found the following code which cause "DESC myindex" shows no rows.

Then, I remove the toLowCase function with the thought trino might show the correct columns:

But I was wrong. This time, trino show below. All column are lower case:

And, I could not select any data from elasticsearch.

below is the Exeption stack:

In my case, I need trino to treat columns like age & Age. Could anyone tell me how to make trino case sensetive? THANKS~

[hashhar]

Requires #17 to fix correctly. The optimizer normalizes every input to lowercase today. We do support case-insensitive name matching as long as there are no collisions - which is not true in your case.

You can try once using the query passthrough feature of the ElasticSearch connector (but I don't think it would work since the query is embedded in the table name which itself would be lowercased). See https://trino.io/docs/current/connector/elasticsearch.html#pass-through-queries.

[findepi]

You can try once using the query passthrough feature of the ElasticSearch connector (but I don't think it would work since the query is embedded in the table name which itself would be lowercased). See https://trino.io/docs/current/connector/elasticsearch.html#pass-through-queries.

Note that (from the docs):

The Elasticsearch query string es-query is base32-encoded to avoid having to deal with escaping quotes and case sensitivity issues in table identifiers.