@@ -85,7 +85,9 @@ $rk->addBrokers("10.0.0.1:9092,10.0.0.2:9092");
85
85
```
86
86
87
87
#### Producing messages
88
- :warning : Make sure that your producer follows proper shutdown (see below) to not lose messages.
88
+
89
+ > ** Warning** Make sure that your producer follows proper shutdown (see below) to not lose messages.
90
+
89
91
Next, we create a topic instance from the producer:
90
92
``` php
91
93
<?php
@@ -111,7 +113,8 @@ The message payload can be anything.
111
113
This should be done prior to destroying a producer instance
112
114
to make sure all queued and in-flight produce requests are completed
113
115
before terminating. Use a reasonable value for ` $timeout_ms ` .
114
- :warning : Not calling flush can lead to message loss!
116
+
117
+ > ** Warning** Not calling flush can lead to message loss!
115
118
116
119
``` php
117
120
$rk->flush($timeout_ms);
@@ -133,7 +136,7 @@ The RdKafka\KafkaConsumer class supports automatic partition assignment/revocati
133
136
134
137
### Low-level consuming (legacy)
135
138
136
- > : information_source : The low-level consumer is a legacy API, please prefer using the high-level consumer
139
+ > ** Note ** The low-level consumer is a legacy API, please prefer using the high-level consumer
137
140
138
141
We first need to create a low level consumer, and to add brokers (Kafka
139
142
servers) to it:
@@ -184,7 +187,7 @@ while (true) {
184
187
185
188
### Low-level consuming from multiple topics / partitions (legacy)
186
189
187
- > : information_source : The low-level consumer is a legacy API, please prefer using the high-level consumer
190
+ > ** Note ** The low-level consumer is a legacy API, please prefer using the high-level consumer
188
191
189
192
Consuming from multiple topics and/or partitions can be done by telling
190
193
librdkafka to forward all messages from these topics/partitions to an internal
0 commit comments