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
We're having an issue with too big headers being passed between the client and the server when inserting bigger chunks of data. Namely, the X-Trino-Added-Prepare header (this has already been mentioned in trinodb/trino#8797). The way it's passed down and back to the server makes it very unwieldy to process queries with a large number of parameters (as is the case when inserting many values). It requires configuring all the proxies and clients (including monkey-patching the python HTTP client) along the way to values way beyond sensible.
It seems that the issue we're running into is that the inserts shouldn't have been prepared statements in the first place (especially since currently you cannot reuse them for uploading different chunks of data as they get deallocated immediately after the query has been executed).
As such, I think it would be good to have the option to skip using prepared statements which generate really bulky X-Trino-Added-Prepare headers (introduced in #41), in particular in the insert scenario.
The text was updated successfully, but these errors were encountered:
We're having an issue with too big headers being passed between the client and the server when inserting bigger chunks of data. Namely, the
X-Trino-Added-Prepare
header (this has already been mentioned in trinodb/trino#8797). The way it's passed down and back to the server makes it very unwieldy to process queries with a large number of parameters (as is the case when inserting many values). It requires configuring all the proxies and clients (including monkey-patching the python HTTP client) along the way to values way beyond sensible.It seems that the issue we're running into is that the inserts shouldn't have been prepared statements in the first place (especially since currently you cannot reuse them for uploading different chunks of data as they get deallocated immediately after the query has been executed).
As such, I think it would be good to have the option to skip using prepared statements which generate really bulky
X-Trino-Added-Prepare
headers (introduced in #41), in particular in the insert scenario.The text was updated successfully, but these errors were encountered: