2324 use post query params (draft)

[andris-rauda-sumsub]

Summary

Try implementing sending statement parameters via multipart/form-data to mitigate issues with too long url.

PR is a work in progress.

Tried to implement passing query parameters as Content-Type: multipart/form-data, got some ugly mockup (because of a streaming support), that kind of does work, however, it turns out, that when calling it with many parameters from local integration test, it starts failing with a weird server error even sooner, than the original application/x-www-form-urlencoded variant:

com.clickhouse.client.api.ServerException: Code: 1000. DB::Exception: <Unreadable error message> (transport error: 500)

So, seems, for now it is unfeasible to pursue this.

Closes

Checklist

Delete items not relevant to your PR:

• Closes Query parameters can't be sent through POST body #2324
• Unit and integration tests covering the common scenarios were added
• A human-readable description of the changes was provided to include in CHANGELOG
• For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[chernser]

Good day, @andris-rauda-sumsub!
Thank you for starting the contribution!

This may be would be easier to implement after we have organize a separate transport layer with multiple http client support.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.