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: docs/kafka/getting-started-kafka/README.adoc
+22-7Lines changed: 22 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,11 +129,16 @@ endif::[]
129
129
.Procedure
130
130
. In the {product-kafka} {service-url-kafka}[web console^], select *Kafka Instances* and click *Create Kafka instance*.
131
131
+
132
+
ifdef::qs[]
133
+
The instance creation pane opens.
134
+
endif::[]
135
+
ifndef::qs[]
132
136
The instance creation pane opens, as shown in the figure.
133
137
+
134
138
[.screencapture]
135
139
.Kafka instance creation pane
136
140
image::sak-configure-kafka-instance.png[Image of Create Kafka instance pane]
141
+
endif::[]
137
142
138
143
. Enter a unique name for the Kafka instance, such as `my-first-kafka-instance`.
139
144
. In the *Cloud region* list, select the relevant option.
@@ -159,11 +164,15 @@ For more information about the support scope of Red Hat Technology Preview featu
159
164
--
160
165
The new Kafka instance is listed on the *Kafka Instances* page. Typically, you need to wait a few minutes for the instance creation process to finish.
161
166
167
+
ifdef::qs[]
168
+
When the instance has a status of *Ready*, you can start using the instance. You can click the options icon (three vertical dots) to view instance and connection details, change the instance owner, or delete the instance.
169
+
endif::[]
170
+
ifndef::qs[]
162
171
When the instance has a status of *Ready*, you can start using the instance. As shown in the following figure, you can click the options icon (three vertical dots) to view instance and connection details, change the instance owner, or delete the instance.
163
-
164
172
[.screencapture]
165
173
.Kafka instance options menu
166
174
image::sak-kafka-instance-options.png[Image of Kafka instance options menu]
175
+
endif::[]
167
176
168
177
NOTE: Although you can see Kafka instances created by other users in your organization, you might not be able to manage or connect to those instances. Only the instance owner or users with permissions to access the instance can edit or delete the instance, access the associated service account and topics, or connect to the instance.
169
178
--
@@ -307,13 +316,18 @@ After you create a Kafka instance, you can create Kafka topics to start producin
307
316
308
317
. In the {product-long-kafka} {service-url-kafka}[web console^], select *Kafka Instances* and then click the name of the Kafka instance that you want to add a topic to.
309
318
. Select the *Topics* tab.
319
+
ifdef::qs[]
320
+
. Click *Create topic* and follow the guided steps to define the topic details.
321
+
endif::[]
322
+
ifndef::qs[]
310
323
. Click *Create topic* and follow the guided steps to define the topic details, as shown in the figure.
311
324
+
312
-
--
313
325
[.screencapture]
314
326
.Guided steps to define topic details
315
327
image::sak-create-topic.png[Image of wizard to create a topic]
316
-
328
+
endif::[]
329
+
+
330
+
--
317
331
You must specify the following topic properties:
318
332
319
333
* *Topic name*: Enter a unique topic name, such as `my-first-kafka-topic`.
@@ -330,11 +344,12 @@ endif::[]
330
344
NOTE: If the topic creation is unsuccessful and you see a `400 Bad Request` error message, try to create your topic again later. This situation might occur, for example, if your selected cloud provider has a temporary availability problem that affects your Kafka instance.
331
345
--
332
346
347
+
ifdef::qs[]
348
+
. (Optional) To edit or delete the topic, click the options icon (three vertical dots) next to the topic name.
349
+
endif::[]
350
+
ifndef::qs[]
333
351
. (Optional) To edit or delete the topic, click the options icon (three vertical dots) next to the topic name, as shown in the figure.
334
-
+
335
-
[.screencapture]
336
-
.Edit or delete Kafka topic
337
-
image::sak-edit-topic.png[Image of topic options to edit or delete]
Copy file name to clipboardExpand all lines: docs/kafka/nodejs-kafka/README.adoc
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -205,20 +205,18 @@ The Node.js application in this quick start uses a Kafka topic called `countries
205
205
.Procedure
206
206
. In the {product-kafka} {service-url-kafka}[web console^], select *Kafka Instances* and then click the name of the Kafka instance that you want to add a topic to.
207
207
. Select the *Topics* tab.
208
-
. Click *Create topic* and follow the guided steps to define the topic details, as shown in the figure.
209
-
+
210
-
[.screencapture]
211
-
.Guided steps to define topic details
212
-
image::sak-create-countries-topic.png[Image of wizard to create a topic]
208
+
. Click *Create topic* and follow the guided steps to define the topic details.
213
209
+
210
+
--
214
211
You must specify the following topic properties:
215
212
216
-
* *Topic name*: Enter `countries` as the topic name.
217
-
* *Partitions*: Set the number of partitions for this topic. This example sets the partitions value to `1`. Partitions are distinct lists of messages within a topic and enable parts of a topic to be distributed over multiple brokers in the cluster. A topic can contain one or more partitions, enabling producer and consumer loads to be scaled.
218
-
* *Message retention*: Set the message retention time and size to the relevant value and increment. This example sets the retention time to `A week` and the retention size to `Unlimited`. Message retention time is the amount of time that messages are retained in a topic before they are deleted or compacted, depending on the cleanup policy. Retention size is the maximum total size of all log segments in a partition before they are deleted or compacted.
219
-
* *Replicas*: Replicas are copies of partitions in a topic. For this release of {product-kafka}, the replica values are preconfigured. The number of partition replicas for the topic is set to `3` and the minimum number of follower replicas that must be in sync with a partition leader is set to `2`. For a trial Kafka instance, the number of replicas and the minimum in-sync replica factor are both set to `1`. Partition replicas are distributed over multiple brokers in the cluster to ensure topic availability if a broker fails. When a follower replica is in sync with a partition leader, the follower replica can become the new partition leader if needed.
220
-
+
213
+
* *Topic name*: For this quick start, enter `countries` as the topic name.
214
+
* *Partitions*: Set the number of partitions for the topic. For this quick start, set the value to `1`.
215
+
* *Message retention*: Set the message retention time and size. For this quick start, set the retention time to `A week` and the retention size to `Unlimited`.
216
+
* *Replicas*: For this release of {product-kafka}, the replica values are preconfigured. The number of partition replicas for the topic is set to `3` and the minimum number of follower replicas that must be in sync with a partition leader is set to `2`. For a trial Kafka instance, the number of replicas and the minimum in-sync replica factor are both set to `1`.
217
+
221
218
After you complete the setup, the new topic appears on the *Topics* page. You can now run the Node.js application to start producing and consuming messages.
Copy file name to clipboardExpand all lines: docs/kafka/quarkus-kafka/README.adoc
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,20 +189,18 @@ The Quarkus application in this quick start uses a Kafka topic called `prices` t
189
189
.Procedure
190
190
. In the {product-kafka} {service-url-kafka}[web console^], select *Kafka Instances* and then click the name of the Kafka instance that you want to add a topic to.
191
191
. Select the *Topics* tab.
192
-
. Click *Create topic* and follow the guided steps to define the topic details, as shown in the figure.
193
-
+
194
-
[.screencapture]
195
-
.Guided steps to define topic details
196
-
image::sak-create-topic.png[Image of wizard to create a topic]
192
+
. Click *Create topic* and follow the guided steps to define the topic details.
197
193
+
194
+
--
198
195
You must specify the following topic properties:
199
196
200
-
* *Topic name*: Enter `prices` as the topic name.
201
-
* *Partitions*: Set the number of partitions for this topic. This example sets the partitions value to `1`. Partitions are distinct lists of messages within a topic and enable parts of a topic to be distributed over multiple brokers in the cluster. A topic can contain one or more partitions, enabling producer and consumer loads to be scaled.
202
-
* *Message retention*: Set the message retention time and size to the relevant value and increment. This example sets the retention time to `A week` and the retention size to `Unlimited`. Message retention time is the amount of time that messages are retained in a topic before they are deleted or compacted, depending on the cleanup policy. Retention size is the maximum total size of all log segments in a partition before they are deleted or compacted.
203
-
* *Replicas*: Replicas are copies of partitions in a topic. For this release of {product-kafka}, the replica values are preconfigured. The number of partition replicas for the topic is set to `3` and the minimum number of follower replicas that must be in sync with a partition leader is set to `2`. For a trial Kafka instance, the number of replicas and the minimum in-sync replica factor are both set to `1`. Partition replicas are distributed over multiple brokers in the cluster to ensure topic availability if a broker fails. When a follower replica is in sync with a partition leader, the follower replica can become the new partition leader if needed.
204
-
+
197
+
* *Topic name*: For this quick start, enter `prices` as the topic name.
198
+
* *Partitions*: Set the number of partitions for the topic. For this quick start, set the value to `1`.
199
+
* *Message retention*: Set the message retention time and size. For this quick start, set the retention time to `A week` and the retention size to `Unlimited`.
200
+
* *Replicas*: For this release of {product-kafka}, the replica values are preconfigured. The number of partition replicas for the topic is set to `3` and the minimum number of follower replicas that must be in sync with a partition leader is set to `2`. For a trial Kafka instance, the number of replicas and the minimum in-sync replica factor are both set to `1`.
201
+
205
202
After you complete the setup, the new topic appears on the *Topics* page. You can now run the Quarkus application to start producing and consuming messages to and from this topic.
Copy file name to clipboardExpand all lines: docs/rhoas/rhoas-produce-consume/README.adoc
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,14 +128,16 @@ In this task, you'll create a new topic in your Kafka instance. You'll use this
128
128
. Select the *Topics* tab.
129
129
. Click *Create topic* and follow the guided steps to define the topic details.
130
130
+
131
+
--
131
132
You must specify the following topic properties:
132
133
133
134
* *Topic name*: For this quick start, enter `test-topic` as the topic name.
134
135
* *Partitions*: Set the number of partitions for the topic. For this quick start, set the value to `2`.
135
136
* *Message retention*: Set the message retention time and size. For this quick start, set the retention time to `A week` and the retention size to `Unlimited`.
136
-
* *Replicas*: For this release of {product-kafka}, replica values are preconfigured. The number of partition replicas and the minimum number of follower replicas that must be in sync with a partition leader are both set to `1`.
137
-
+
137
+
* *Replicas*: For this release of {product-kafka}, replica values are preconfigured. The number of partition replicas for the topic is set to `3` and the minimum number of follower replicas that must be in sync with a partition leader is set to `2`. For a trial Kafka instance, the number of replicas and the minimum in-sync replica factor are both set to `1`.
138
+
138
139
After you complete the setup, the new topic appears on the *Topics* page.
0 commit comments