- Correctly set maxRequests in okhttp dispatcher based on setMaxRequests TectonClient builder method.
- Properly specified okhttp3 as an api dependency.
- A user agent string is now included in all HTTP requests. It identifies the java client and version.
- Throw more informative exceptions for invalid data types, and parse more representations of doubles.
- Add handling of cached feature statuses.
- Fixed URL path encodings.
- Allow request context values to be null in
GetFeaturesRequestData.
-
Custom Exceptions in the Java Client that map to specific HTTP status codes.
BadRequestException- HTTP Status 400UnauthorizedException- HTTP Status 401ForbiddenException- HTTP Status 403ResourceNotFoundException- HTTP Status 404ResourceExhaustedException- HTTP Status 429InternalServerErrorException- HTTP Status 500ServiceUnavailableException- HTTP Status 503GatewayTimeoutException- HTTP Status 504
-
InvalidRequestParameterExceptionfor misconfigured requests such as missing workspace name, missing feature service name etc
- Make getters in
GetFeaturesRequestDatapublic for better debuggability
- Fix a typo in one of the error messages
- NullPointerException while fetching null feature values in Lists
- Support for
equals()andhashCode()for all Request and Response classes - Builders for all Request and Response classes
- Ability to bring in a custom OkHttp client instead of using the Tecton Client default.
- Allow Tecton API Key to be null during Tecton Client initialization so that it can be added to the header by request interceptors instead.
- Fixed parsing
effective_timeinGetFeaturesResponseandGetFeaturesBatchResponse
- Add comments to clarify supported data types for feature values in Tecton
- Allow join key values to be null in
GetFeaturesRequestData, for consistency with the REST API.