-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
query_id not work #164
Comments
I saw the #47 issue , it was cancelled, so why |
when I use |
FYI, this PR was managed by the previous owners of chproxy. |
Hello @ddddddcf , today it does not work because chproxy uses its own generated
In the issue you linked hagen proposed a solution to that:
would that work for you? It requires obviously code changes to chproxy, but it's the least impactful. |
I also need this function for using |
The way I solved this problem was, put a unique comment in the query, sql like:
I can query by sql : |
I use http protocol not tcp, query_id is valid, when pass chproxy. So can't filter with |
you can put a comment in SQL even with the http protocol |
I send request with params {"query_id":"xxxxx"},but it doesn't work ,it always use scope_id please give me help ! thank
you
The text was updated successfully, but these errors were encountered: