[KAFKA-163] Improve infer schema usage in the real world. Created: 24/Sep/20 Updated: 28/Oct/23 Resolved: 24/Sep/20 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Source |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Support schema for Source connector |
| Description |
|
Because the initial implementation of inferred schema's doesn't mark schema's as optional any variation in the schema will break the default compatibility level when using Avro. By marking inferred schemas as optional then the default backwards compatibility can be honoured. As field order is also important and fixed with schema'd types, document field order should be alphabetically sorted to allow for best compatibility. |
| Comments |
| Comment by Githook User [ 24/Sep/20 ] |
|
Author: {'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}Message: Improve infer schema usability All fields are now optional
|