i did this as a workaround:

curl -XPUT " None " -H 'Content-Type: application/json' -d'
{
"properties": {
"metric": { "type": "text", "fielddata": true },
"variant": { "type": "text", "fielddata": true }
}
}'

but this workaround should not be needed ,right ? is this a compat issue ? or was my elasticsearch not properly initialized ?

on kubernetes

this is now in my python script:

its as if the line is not there

i'm still trying to understand why it was needed in our case. i have a nvidia gpu operator with mostly the default values installed on our on prem cluster. i found there is an option CONTAINERD_SET_AS_DEFAULT in the operator, which, when enabled, puts the runtime for all pods. we didn't enable that option, maybe if we had enabled it would have worked.

for comparison: this is when i use --output-uri

it was to test if reuse_last_task_id made any effect (i have the impression it doesn't)

(same for environment variable)