Skip to content

Commit 055fd15

Browse files
doc: updated docs for the new format
1 parent 4c73499 commit 055fd15

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

documentation/modules/con-requests-kafka-bridge.adoc

+6-3
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ API request and response bodies are always encoded as JSON.
1919
Content-Type: application/vnd.kafka.v2+json
2020
----
2121

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`.
2323
+
2424
[cols="35,65",options="header",stripes="none",separator=¦]
2525
|===
@@ -33,6 +33,9 @@ m¦Content-Type: application/vnd.kafka.json.v2+json
3333
¦Binary
3434
m¦Content-Type: application/vnd.kafka.binary.v2+json
3535

36+
¦Text
37+
m¦Content-Type: application/vnd.kafka.text.v2+json
38+
3639
|===
3740

3841
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.
4245

4346
== Embedded data format
4447

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: JSON and 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.
4649

47-
When creating a consumer using the `/consumers/_groupid_` endpoint, the `POST` request body must specify an embedded data format of either JSON or 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:
4851

4952
[source,json,subs="attributes+"]
5053
----

0 commit comments

Comments
 (0)