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
Copy file name to clipboardexpand all lines: README.md
+10
Original file line number
Diff line number
Diff line change
@@ -171,6 +171,16 @@ Because of that, if AsyncIO timer passes, Flink will throw TimeoutException whic
171
171
The HTTP request timeouts on the other hand will not cause Job restart. In that case, exception will be logged into application logs.
172
172
To avoid job restart on timeouts caused by Lookup queries, the value of `gid.connector.http.source.lookup.request.timeout` should be smaller than `table.exec.async-lookup.timeout`.
173
173
174
+
#### Lookup multiple results
175
+
176
+
Typically, join can return zero, one or more results. What is more, there are lots of possible REST API designs and
177
+
pagination methods. Currently, the connector supports only two simple approaches (`gid.connector.http.source.lookup.result-type`):
178
+
179
+
-`single-value` - REST API returns single object.
180
+
-`array` - REST API returns array of objects. Pagination is not supported yet.
181
+
182
+
Please be informed that the mechanism will be enhanced in the future. See [HTTP-118](https://github.com/getindata/flink-http-connector/issues/118).
183
+
174
184
### HTTP Sink
175
185
The following example shows the minimum Table API example to create a [HttpDynamicSink](src/main/java/com/getindata/connectors/http/internal/table/HttpDynamicSink.java) that writes JSON values to an HTTP endpoint using POST method, assuming Flink has JAR of [JSON serializer](https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/connectors/table/formats/json/) installed:
0 commit comments