Elasticsearch array fields cause query failure even though array property is NOT selected

[StephenOTT]

Working on trino 453.

Consider a query such as:

select "@timestamp", "labels".some_prop from my_catalog.default.".apm.somelogs*" limit 5

the labels is an object.

One of the properties is the labels.process_command_args which is populated by OpenTelemetry and APM is an ArrayList.

But when the query above is run i get an error such as:

"Expect a string or numeric value for field 'labels.process_command_args` of type VARCHAR....".

My expectation is i would only need to set the array list support in the _meta when i actually need the property.

my some_prop is just a varchar.

Are we seeing that if a document contains an array list then you MUST apply the _meta configs even though we do NOT use the values in the query and response?

Thanks