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: documentation/modules/con-requests-kafka-bridge.adoc
+6-3
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ API request and response bodies are always encoded as JSON.
19
19
Content-Type: application/vnd.kafka.v2+json
20
20
----
21
21
22
-
* When performing producer operations, `POST` requests must provide `Content-Type` headers specifying the _embedded data format_ of the messages produced. This can be either `json`or `binary`.
22
+
* When performing producer operations, `POST` requests must provide `Content-Type` headers specifying the _embedded data format_ of the messages produced. This can be either `json`, `binary` or `text`.
The embedded data format is set per consumer, as described in the next section.
@@ -42,9 +45,9 @@ An empty body can be used to create a consumer with the default values.
42
45
43
46
== Embedded data format
44
47
45
-
The embedded data format is the format of the Kafka messages that are transmitted, over HTTP, from a producer to a consumer using the Kafka Bridge. Two embedded data formats are supported: JSONand binary.
48
+
The embedded data format is the format of the Kafka messages that are transmitted, over HTTP, from a producer to a consumer using the Kafka Bridge. Three embedded data formats are supported: JSON, binary and text.
46
49
47
-
When creating a consumer using the `/consumers/_groupid_` endpoint, the `POST` request body must specify an embedded data format of either JSONor binary. This is specified in the `format` field, for example:
50
+
When creating a consumer using the `/consumers/_groupid_` endpoint, the `POST` request body must specify an embedded data format of either JSON, binary or text. This is specified in the `format` field, for example:
0 commit comments