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

Added small detail in README

Browse Source 
Added small detail in README wrt. extending existing schemes and the requirement to keep consumer up to date with most recent producer.
This commit is contained in:
Bart Blommaerts
2020-04-15 11:17:39 +02:00
committed by Christian Tzolov
parent ec3361ba0e
commit 03c18fd5da
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
schema-registry-samples/schema-registry-vanilla-rabbit-binder/README.adoc
View File

@@ -82,7 +82,7 @@ The `consumer` is coded against a base schema that include the split fields.
The `consumer` app can happily deserialize the payload with `internalTemperature` and `externalTemperature` fields. However, when
a `producer1` payload arrives (which includes `temperature` field), the schema evolution and compatibility check are automatically
applied.
applied. The `consumer` app doesn't need to contain all fields from the newest (`producer2`) schema, but it will obviously not be able to use them if they are missing. For example the `accelerometer` field is not present in the `consumer` app, but is in the `producer2` app.
Because each payload also includes the payload version in the header, Spring Cloud Stream with the help of Schema
Registry server and Avro, the schema evolution occurs behind the scenes. The automatic mapping of `temperature` to