SpringCloud/spring-cloud-stream-samples
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix command by control center

Browse Source
This commit is contained in:
Christian Tzolov
2020-06-05 13:39:11 +02:00
parent bc2f2d4113
commit ec3361ba0e
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
schema-registry-samples/schema-registry-confluent-avro-serializer/README.adoc
View File

@@ -115,11 +115,11 @@ Once you are done with running the samples, stop the docker containers
`docker-compose down` `docker-compose down`
=== Using Confluent Command Center === Using Confluent Control Center
This test can be run with the [Confluent Command Center](https://docs.confluent.io/current/control-center/index.html) - a web-based tool for managing and monitoring Apache Kafka®. Control Center facilitates building and monitoring production data pipelines and streaming applications. This test can be run with the https://docs.confluent.io/current/control-center/index.html[Confluent Control Center] - a web-based tool for managing and monitoring Apache Kafka®. Control Center facilitates building and monitoring production data pipelines and streaming applications.
For a quick start you can install the command center with the help of the `docker-compose-control-center.yaml`: For a quick start you can install the control center with the help of the `docker-compose-control-center.yaml`:
[source,bash] [source,bash]
---- ----
@@ -132,7 +132,7 @@ The https://docs.confluent.io/current/control-center/topics/schema.html[Schema R
After you run the samples and post couple of messages as explained above. After you run the samples and post couple of messages as explained above.
1. Open the command center at `http://localhost:9021` and click on the provided cluster. 1. Open the control center at `http://localhost:9021` and click on the provided cluster.
2. From the vertical menu select `Topics` tab. 2. From the vertical menu select `Topics` tab.
3. From the list of topics select the `sensor-topic` - the topic created by the samples. 3. From the list of topics select the `sensor-topic` - the topic created by the samples.
4. Click on the `Schema` tab to see the `Sensors` schema. 4. Click on the `Schema` tab to see the `Sensors` schema.
@@ -180,7 +180,7 @@ spring:
strategy: io.confluent.kafka.serializers.subject.RecordNameStrategy strategy: io.confluent.kafka.serializers.subject.RecordNameStrategy
---- ----
Note that currently the Command Center seams to be recognizing only the subjects created with `TopicNameStrategy` . If you configure the `RecordNameStrategy` they schema will not appear in the UI. Note that currently the Control Center seams to be recognizing only the subjects created with `TopicNameStrategy` . If you configure the `RecordNameStrategy` they schema will not appear in the UI.

14
schema-registry-samples/schema-registry-confluent/README.adoc
View File

@@ -112,11 +112,11 @@ Once you are done with running the samples, stop the docker containers
and stop the Confluent Schema Registry server. and stop the Confluent Schema Registry server.
=== Using Confluent Command Center === Using Confluent Control Center
This test can be run with the [Confluent Command Center](https://docs.confluent.io/current/control-center/index.html) - a web-based tool for managing and monitoring Apache Kafka®. Control Center facilitates building and monitoring production data pipelines and streaming applications. This test can be run with the https://docs.confluent.io/current/control-center/index.html[Confluent Control Center] - a web-based tool for managing and monitoring Apache Kafka®. Control Center facilitates building and monitoring production data pipelines and streaming applications.
For a quick start you can install the command center with the help of the `docker-compose-control-center.yaml`: For a quick start you can install the control center with the help of the `docker-compose-control-center.yaml`:
[source,bash] [source,bash]
---- ----
@@ -128,7 +128,7 @@ The https://docs.confluent.io/current/control-center/topics/schema.html[Schema R
After you run the samples and post couple of messages as explained above. After you run the samples and post couple of messages as explained above.
1. Open the command center at `http://localhost:9021` and click on the provided cluster. 1. Open the control center at `http://localhost:9021` and click on the provided cluster.
2. From the vertical menu select `Topics` tab. 2. From the vertical menu select `Topics` tab.
3. From the list of topics select the `sensor-topic` - the topic created by the samples. 3. From the list of topics select the `sensor-topic` - the topic created by the samples.
4. Click on the `Schema` tab to see the `Sensors` schema. 4. Click on the `Schema` tab to see the `Sensors` schema.
@@ -138,11 +138,11 @@ After you have run the samples you should be able to see a schema subject name `
==== NOTE ==== NOTE
Note that currently the Command Center recognizes only schema subjects created with https://docs.confluent.io/current/schema-registry/serdes-develop/index.html[TopicNameStrategy]. Note that currently the Control Center recognizes only schema subjects created with https://docs.confluent.io/current/schema-registry/serdes-develop/index.html[TopicNameStrategy].
That means that the schema name (e.g. subject) must be named after your topic name (e.g. spring.cloud.stream.bindings.<channel>:destination) followed by `-value` suffix. That means that the schema name (e.g. subject) must be named after your topic name (e.g. spring.cloud.stream.bindings.<channel>:destination) followed by `-value` suffix.
In our sample the topic (e.g. destination) is called `sensor-topic`. Therefore the schema subject should be named `sensor-topic-value` to be recognizable by the Confluent command center. In our sample the topic (e.g. destination) is called `sensor-topic`. Therefore the schema subject should be named `sensor-topic-value` to be recognizable by the Confluent Control center.
Note that the confluent schema registry works fine with different subject naming strategies, only the command center visualization will not show them. Note that the confluent schema registry works fine with different subject naming strategies, only the control center visualization will not show them.
To configure a the schema name after the topic name yuo can use the `spring.cloud.schema.avro.subjectNamePrefix` To configure a the schema name after the topic name yuo can use the `spring.cloud.schema.avro.subjectNamePrefix`
and `spring.cloud.schema.avro.subjectNamePrefix.subjectNamingStrategy` properties as shown below (only available with 1.1.x onwards: and `spring.cloud.schema.avro.subjectNamePrefix.subjectNamingStrategy` properties as shown below (only available with 1.1.x onwards: