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

I use QueryContext to query a super long sql (13700 bytes). When there are args parameters, the error http2ErrCodeEnhanceYourCalm (11) will be reported. Has anyone encountered this? #123

Closed
KarelRoy opened this issue Sep 4, 2024 · 3 comments · Fixed by #128

Comments

@KarelRoy
Copy link

KarelRoy commented Sep 4, 2024

image

I use QueryContext to query a super long sql (13700 bytes). When there are args parameters, the error http2ErrCodeEnhanceYourCalm (11) will be reported. Has anyone encountered this?

@KarelRoy
Copy link
Author

KarelRoy commented Sep 5, 2024

I may have found the reason,
we will put prepare sql in the header with prepared statement method. If the sql is too long, there will be problems. Is it possible to consider a better way to achieve this, such as using "EXECUTE IMMEDIATE"

@nineinchnick
Copy link
Member

The JDBC client sends the query text in the request body, maybe we should also do it here: https://github.com/trinodb/trino/blob/master/client/trino-client/src/main/java/io/trino/client/StatementClientV1.java#L145

@KarelRoy
Copy link
Author

The JDBC client sends the query text in the request body, maybe we should also do it here: https://github.com/trinodb/trino/blob/master/client/trino-client/src/main/java/io/trino/client/StatementClientV1.java#L145

Map<String, String> statements = session.getPreparedStatements(); for (Entry<String, String> entry : statements.entrySet()) { builder.addHeader(TRINO_HEADERS.requestPreparedStatement(), urlEncode(entry.getKey()) + "=" + urlEncode(entry.getValue())); }
that seems to be placed in the header. Maybe there is no other way except to modify own ngnix configuration.

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

Successfully merging a pull request may close this issue.

2 participants