Closed natalie-zamani closed 1 year ago
Right now, the client configuration only exposes a single timeout config, connectionTimeout. That is then used for both the connection and read timeout configs on the underlying OkHttp client: https://github.com/typesense/typesense-java/blob/master/src/main/java/org/typesense/api/ApiCall.java#L52-L53
connectionTimeout
There should be separate configs for these two values, so that we can more granularly control the behavior of the API client.
Not applicable.
The expectation would be to have two separate configuration values for the connection and read timeouts.
Fixed in v0.3.0
v0.3.0
Description
Right now, the client configuration only exposes a single timeout config,
connectionTimeout
. That is then used for both the connection and read timeout configs on the underlying OkHttp client: https://github.com/typesense/typesense-java/blob/master/src/main/java/org/typesense/api/ApiCall.java#L52-L53There should be separate configs for these two values, so that we can more granularly control the behavior of the API client.
Steps to reproduce
Not applicable.
Expected Behavior
The expectation would be to have two separate configuration values for the connection and read timeouts.
Actual Behavior