Skip to content
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

HTTP 400 unsupported path "/query" error with latest clickhouse-odbc #42

Closed
morokin opened this issue Mar 6, 2019 · 5 comments
Closed

Comments

@morokin
Copy link

morokin commented Mar 6, 2019

chproxy is not working with https://github.com/yandex/clickhouse-odbc/releases/tag/v1.0.0.20190201 driver

@valyala
Copy link
Contributor

valyala commented Mar 7, 2019

  • Did it work with the previous versions of clickhouse-odbc driver?
  • Which error does chproxy log on clickhouse-odbc access?
  • Which error does clickhouse-odbc driver return on error?

@morokin
Copy link
Author

morokin commented Mar 7, 2019

It works with the previous release without issues.

Which error does clickhouse-odbc driver return on error?
I apologize, seems I wasn't clear enough, I posted exact error in head of issue, so here it is error returned from odbc driver:

HTTP 400 unsupported path "/query"

I will post debug output from chproxy soon

@morokin
Copy link
Author

morokin commented Mar 8, 2019

Mar 08 21:06:15 hostname chproxy[2766]: ERROR: 2019/03/08 21:06:15 main.go:246: "ip:51577": unsupported path: "/query"

This is only output I see in chproxy logs while I'm attempting to run any query from application using latest ODBC driver. Everything works fine with previous driver as I mentioned above

valyala added a commit that referenced this issue Mar 8, 2019
ClickHouse accepts requests on both `/` and `/query` paths. See ClickHouse/clickhouse-odbc@8fcd279 .
@valyala
Copy link
Contributor

valyala commented Mar 8, 2019

The issue should be fixed starting from v1.13.1.

@valyala valyala closed this as completed Mar 8, 2019
@morokin
Copy link
Author

morokin commented Mar 8, 2019

It works, appreciate your quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants