Open amitds1997 opened 3 years ago
this is likely something https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html has described and you need to enable "Client protocol compatiblity" on the trino coordinator
We may consider adding dual HTTP header writes (if eitherX-Presto-...
or X-Trino-...
is set, both X-Presto-...
and X-Trino-...` headers would be send to the coordinators) in the future
For an incompatible client, Trino/Presto throw exception :
and sends no Query Id information.
We are currently submitting the query for addition to Query History without checking if the Query Id is
null
.https://github.com/lyft/presto-gateway/blob/39d7d5f3194265c688d4d5f01db1d64143fe284a/gateway-ha/src/main/java/com/lyft/data/gateway/ha/handler/QueryIdCachingProxyHandler.java#L258
which leads to an Exception