Issue reports the issue also on PrestoHook.
Is there a fix for it?

Issue reports the issue also on PrestoHook. Is there a fix for it?

No, I've tested it with a local Trino deployment and the latest Presto Python client still has the old problematic behaviour.

Issue reports the issue also on PrestoHook. Is there a fix for it?

No, I've tested it with a local Trino deployment and the latest Presto Python client still has the old problematic behaviour.

Is there an open github issue we can track?

Issue reports the issue also on PrestoHook. Is there a fix for it?

No, I've tested it with a local Trino deployment and the latest Presto Python client still has the old problematic behaviour.

Is there an open github issue we can track?

Found this open issue since 2019: prestodb/presto-python-client#84
I could try to bring attention to it, but from the comments it doesn't look that they're considering implementing a fix.

Please run pre-commit locally to fix the static checks.

Should the Trino provider version be bumped to 4.1.1 in this PR?

Should the Trino provider version be bumped to 4.1.1 in this PR?

no. This action is done by release manager as only during release we know if it's patch/minor/major release