WEBVTT

00:04.380 --> 00:10.970
We have just launched Gulf cocounsel producer connected to one of the servers in Gloucester, and they

00:10.980 --> 00:18.390
sent some messages to see this and hear what those messages and now this console producer is still up

00:18.390 --> 00:21.300
and running and we are able to send another messages.

00:21.660 --> 00:25.680
But no, let's try to consume messages from coffeecake last hour.

00:25.860 --> 00:31.520
And for that, we need to launch consumer that will consume messages from this topic.

00:31.800 --> 00:37.080
And luckily, there was a golf course or consumer available in Kafka out of the box.

00:37.320 --> 00:38.010
Let's use it.

00:38.370 --> 00:39.960
Let's open up a window.

00:41.480 --> 00:49.850
Let me make it smaller like so, and here go to scaffolder and lounge car consumer with the help of

00:49.850 --> 00:57.260
building script goldkamp, this council, this consumer, this one lisbeth's and usually know without

00:57.260 --> 00:58.040
any arguments.

00:59.730 --> 01:05.460
If you'll scroll up to the beginning of this options list, you'll find out that there was required

01:05.460 --> 01:11.260
argument called Bootstrap Celeron, this one and this argument is already familiar to you.

01:11.580 --> 01:14.920
It supplies a list of Kafka sellers we want to connect to.

01:15.120 --> 01:16.350
We have just single server.

01:16.390 --> 01:20.670
That's why we need to specify it like so localhost Cole, 1992.

01:21.060 --> 01:22.890
OK, let's copy this argument.

01:23.370 --> 01:27.390
Clear time and I'll go back to Kafka Council Consumer Base.

01:27.390 --> 01:32.490
This argument and type here localhost Cole in 1992 and press enter.

01:33.790 --> 01:40.090
And again, I see a list of health options, and that means that there is another argument that is required.

01:40.420 --> 01:42.610
Let's go back to the beginning of this output.

01:42.610 --> 01:48.580
And here you see this message, exactly one of why at least all topic is required.

01:49.000 --> 01:55.240
And that means that in order to successfully launch a console consumer, we need to specify either why

01:55.240 --> 01:57.820
at least argument or topic argument.

01:58.120 --> 02:04.660
Using wordlist argument, you are able to connect to a set of topics and read messages from multiple

02:04.660 --> 02:06.840
topics using wild card syntax.

02:07.090 --> 02:12.010
But our goal for now is to read messages just from single topic called c.D.

02:12.340 --> 02:15.940
That's why let's specify argument topic with name of the topic.

02:16.720 --> 02:22.780
OK, let's clear terminal again and go to this comment and add another argument topic.

02:22.960 --> 02:25.180
And here was the name of the topic cities.

02:25.420 --> 02:26.970
And now let's enter.

02:27.970 --> 02:34.450
And it seems that now Descript is up and running, but we don't see any messages in the council, let's

02:34.450 --> 02:41.800
before let's go to Kafka console producer and produce one more message and let's send another city name,

02:41.800 --> 02:43.540
for example, Delli like.

02:43.540 --> 02:44.980
So let's press enter.

02:46.100 --> 02:53.900
And now I'll get Daley here in the council consumer, and that is a good sign, it means that the consumer

02:53.900 --> 02:59.600
is running correctly and now it receives all messages that are being sent by a producer.

02:59.810 --> 03:01.970
Let's send another message, for example, Dubai.

03:03.230 --> 03:08.560
And this message was successfully received by consumer as well, but now you may ask me a question,

03:08.870 --> 03:15.130
but what about those messages that were sent by a producer here from New York to Sydney?

03:15.530 --> 03:18.290
Let me answer this question in the next lecture by by.