You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We're proxying the queries and want to pass extra context for the proxy so it can make decisions where to send a query, how to rate limit it. We don't want to mess up with ClickHouse, therefore i'd prefer to not add extra GET parameters, therefore the idea is to add extra HTTP headers: X-Example-Customer-Id: 12
You can add headers to the client directly that will be used on every request, by using the client.header dictionary (and in theory you could add and remove them from the client after each request.
I'd rather not add yet more parameters to the query methods, but if that solution doesn't work for you (maybe a client per customer?) I'll consider a PR and put some thought into the cleanest way to allow easy manipulation per query.
Is your feature request related to a problem? Please describe.
We're proxying the queries and want to pass extra context for the proxy so it can make decisions where to send a query, how to rate limit it. We don't want to mess up with ClickHouse, therefore i'd prefer to not add extra GET parameters, therefore the idea is to add extra HTTP headers:
X-Example-Customer-Id: 12
Describe the solution you'd like
Describe alternatives you've considered
This is a request for feedback, if you think it's a OK, i'm gonna implement it.
The text was updated successfully, but these errors were encountered: