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
+49-24Lines changed: 49 additions & 24 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Please use [releases](https://github.com/getindata/flink-http-connector/releases
10
10
11
11
The goal for HTTP TableLookup connector was to use it in Flink SQL statement as a standard table that can be later joined with other stream using pure SQL Flink.
12
12
13
-
Currently, HTTP TableLookup connector supports only Lookup Joins [1]and expects JSON as a response body. It also supports only the STRING types.
`HttpSink` supports both Streaming API (when using [HttpSink](src/main/java/com/getindata/connectors/http/internal/sink/HttpSink.java) built using [HttpSinkBuilder](src/main/java/com/getindata/connectors/http/internal/sink/HttpSinkBuilder.java)) and the Table API (using connector created in [HttpDynamicTableSinkFactory](src/main/java/com/getindata/connectors/http/internal/table/HttpDynamicTableSinkFactory.java)).
15
15
16
16
## Prerequisites
@@ -23,7 +23,6 @@ This connector has few Flink's runtime dependencies, that are expected to be pro
23
23
*`org.apache.flink.flink-java`
24
24
*`org.apache.flink.flink-clients`
25
25
*`org.apache.flink.flink-connector-base`
26
-
*`org.apache.flink.flink-java`
27
26
28
27
## Installation
29
28
@@ -38,23 +37,41 @@ You can read the official JavaDoc documentation of the latest release at [https:
| connector | required | The Value should be set to _rest-lookup_|
159
-
| url | required | The base URL that should be use for GET requests. For example _http://localhost:8080/client_|
160
-
| asyncPolling | optional | true/false - determines whether Async Pooling should be used. Mechanism is based on Flink's Async I/O. |
161
-
| root | optional | Sets the json root node for entire table. The value should be presented as Json Path [5], for example `$.details`. |
162
-
| field.#.path | optional | The Json Path from response model that should be use for given `#` field. If `root` option was defined it will be added to field path. The value must be presented in Json Path format [5], for example `$.details.nestedDetails.balance`|
0 commit comments