-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove schema.registry.name.strategy #2660
base: main
Are you sure you want to change the base?
Conversation
@@ -64,7 +58,6 @@ Syntax: | |||
FORMAT PLAIN | |||
ENCODE AVRO ( | |||
schema.registry = 'schema_registry_url [, ...]', | |||
[schema.registry.name.strategy = 'topic_name_strategy'], | |||
[message = 'main_message'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For avro (but not protobuf), message
is only useful when record_name_strategy
or topic_record_name_strategy
. It shall be removed as well.
@@ -96,7 +87,6 @@ FORMAT DEBEZIUM | |||
ENCODE AVRO ( | |||
message = 'main_message', | |||
schema.location = 'location' | schema.registry = 'schema_registry_url [, ...]', | |||
[schema.registry.name.strategy = 'topic_name_strategy'], | |||
[key.message = 'test_key'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here. Let's remove both message
and key.message
for Debezium Avro.
Btw schema.location
shall not be here for avro either. It has to be schema.registry
.
Syntax: | ||
|
||
```sql | ||
FORMAT UPSERT | ||
ENCODE AVRO ( | ||
schema.location = 'location' | schema.registry = 'schema_registry_url [, ...]', | ||
[schema.registry.name.strategy = 'topic_name_strategy'], | ||
[message = 'main_message'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
message
no longer useful
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since which version does this change apply to, 2.0 or 2.1? 🤔
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Description
we do not need
schema.registry.name.strategy
because now we no longer get key schema from schema registry.Keeping the default behavior to
<topic name>-value
as value schema subjectRelated code PR
Related doc issue
Resolve
Rendered preview
Checklist
emile-00
,hengm3467
, &WanYixian
).