Python client does not support SET ROLE
See original GitHub issueWhile using python client, it is not possible to enable admin
role by executing:
SET ROLE admin
However, everything works fine while using presto-cli
.
I am using Presto 329 and python-client 0.7.0.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Python client does not support SET ROLE · Issue #7 - GitHub
While using python client, it is not possible to enable admin role by executing: SET ROLE admin However, everything works fine while using ......
Read more >Getting an error of "Client does not support authentication ...
I've done pip freeze on both mentioned environments and both results are mysql-connector-python==8.0.19 which I find very strange. I've made ...
Read more >ssl — TLS/SSL wrapper for socket objects — Python 3.11.1 ...
The old wrap_socket() function is deprecated since it is both inefficient and has no support for server name indication (SNI) and hostname matching....
Read more >API Reference - discord.py
The following section outlines the API of discord.py. Note. This module uses the Python logging module to log diagnostic and errors in an...
Read more >Databases | Django documentation
Django attempts to support as many features as possible on all database backends. However, not all database backends are alike, and we've had...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree. I created an issue for it. https://github.com/trinodb/trino-python-client/issues/230
Is there any documentation now on how to properly set the role in the connection now? I previously used the work-around above using the http_header but that is not allowed now on this most recent version as it is a ‘reserved’ header. If I call ‘set role ROLE’ as a query it does not persist through into my queries and permission is denied.