Secure inter-cluster query execution (with initial_user as current query user) [v3]#13156
Secure inter-cluster query execution (with initial_user as current query user) [v3]#13156vitlibar merged 9 commits intoClickHouse:masterfrom
Conversation
70ba6c6 to
c75f974
Compare
test_cluster_copier - does not looks related |
e92d166 to
3e06b47
Compare
|
@vitlibar can you take a look please? |
fe05fb9 to
4e196fb
Compare
SELECT arrayJoin([[], []]), * FROM numbers(1) GROUP BY number WITH TOTALSFix - #13625 |
|
Can't reproduce the problem (tried to locate server log with brute force, no luck) |
Unrelated (fixed in #13746)
test_storage_rabbitmq - know flacky test
Known problem with arrayJoin GROUP BY WITH TOTALS (#13625) |
|
@akuzm looks like performance tests hanged, can you take a look please? |
They are waiting in queue (even now, 16 hour later...). I increased the priority. |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Secure inter-cluster query execution (with initial_user as current query user)
Detailed description / Documentation draft:
Implemented:
*_for_usersettings)Usage example:
remote_servers.$CLUSTER.secretto use initial_user as current query user (if omitted/empty then works as before)v1: #11391
v2: #11498
Fixes: #6843
Fixes: #9751
Cc: @filimonov
Cc: @vitlibar
P.S. Not sure that this should be
New Feature, marked it so to highlight thisDetails
HEAD archive:
HEAD pre-merge: