using latest trinodb/trino image leads to connection error

[Ognian]

using latest trinodb/trino image leads to connection error

[Ognian]

Looks like they changed all the headers from X-Presto* to X-Trino* and they are hard coded here

[Ognian]

Ups Sorry, as per https://trino.io/docs/current/admin/properties-general.html
it looks like there is a protocol.v1.alternate-header-name which can be set to Presto will test and report back...

[Ognian]

yes this works, so sorry for the noise;
I'll let this issue open since the setting is actually deprecated and you should decide the best way how you'll like to support it...

[frolovv]

tnx for reporting @Ognian !

we will handle it (probably via config toggle)

[frolovv]

there is a new config param called HTTP_HEADERS_PREFIX for presto/trino modules

it allows you to specify the desired prefix, use X-PRESTO- for presto or X-TRINO- for trino respectively.

here is .env file and presto example :
https://github.com/wix/quix/blob/20abcb75a5912fefc412ffe9bc900d87e2b9f540/env-example#L12