Add schema evolution in doc #59
Conversation
| ---------------- | ||
|
|
||
| The JDBC connector supports schema evolution. When there is a change in a database table schema, | ||
| the JDBC connector can detect the change, create a new Kafka connect schema and try to register |
There was a problem hiding this comment.
Kafka Connect should be capitalized
|
@Ishiihara In addition to other comments, we should make sure capitalization of Schema Registry is consistent with the rest of the documentation. |
|
@ewencp Addressed the review comments and add more explanation on the complexity of getting the default table column values. |
Ishiihara
force-pushed
the
doc-schema-evolution
branch
from
9032de4
to
f22b33e
Compare
| Schema Evolution | ||
| ---------------- | ||
|
|
||
| The JDBC connector supports schema evolution. When there is a change in a database table schema, |
There was a problem hiding this comment.
Oh, one last point I realized -- do we want to mention that this is specific to using AvroConverter? If we're not using AvroConverter, then obviously a lot of this doesn't apply... The first set of statements up to the new Kafka Connect schema make sense, but everything after assumes AvroConverter.
|
@Ishiihara Left some follow up items, but LGTM. Feel free to merge once those issues are resolved. |
Ishiihara
force-pushed
the
doc-schema-evolution
branch
from
f22b33e
to
1ac742b
Compare
Ishiihara
force-pushed
the
doc-schema-evolution
branch
from
1ac742b
to
3496925
Compare
@ewencp @gwenshap @hachikuji