v1.5.0
SDK
Add more settings to configure timeout, max header bytes, and TLS for the HTTP server
--server-read-timeout=DURATION Maximum duration for reading the entire request, including the body. A zero or negative value means there will be no timeout
($HASURA_SERVER_READ_TIMEOUT)
--server-read-header-timeout=DURATION Amount of time allowed to read request headers. If zero, the value of ReadTimeout is used ($HASURA_SERVER_READ_HEADER_TIMEOUT)
--server-write-timeout=DURATION Maximum duration before timing out writes of the response. A zero or negative value means there will be no timeout
($HASURA_SERVER_WRITE_TIMEOUT)
--server-idle-timeout=DURATION Maximum amount of time to wait for the next request when keep-alives are enabled. If zero, the value of ReadTimeout is used
($HASURA_SERVER_IDLE_TIMEOUT)
--server-max-header-kilobytes=1024 Maximum number of kilobytes the server will read parsing the request header's keys and values, including the request line
($HASURA_SERVER_MAX_HEADER_KILOBYTES)
--server-tls-cert-file=STRING Path of the TLS certificate file ($HASURA_SERVER_TLS_CERT_FILE)
--server-tls-key-file=STRING Path of the TLS key file ($HASURA_SERVER_TLS_KEY_FILE)
Go Connector
Add concurrency settings to the Go connector that executes operations in parallel if the request has many variables (query) or operations (mutation).
Name | Description | Default Value |
---|---|---|
QUERY_CONCURRENCY |
The limit of concurrent query executions by name if there are many request variables in a single request wit h format <key1>=<value1>;<key2>=<value2> |
|
QUERY_CONCURRENCY_LIMIT |
The limit of concurrent query executions if there are many request variables in a single request | 1 |
MUTATION_CONCURRENCY_LIMIT |
The limit of concurrent mutation executions if there are many operations in a single request | 1 |
What's Changed
Full Changelog: v1.4.1...v1.5.0