-
Notifications
You must be signed in to change notification settings - Fork 552
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
schema_registry/test: Support JSON custom attributes on fields #7330
schema_registry/test: Support JSON custom attributes on fields #7330
Conversation
Signed-off-by: Ben Pope <ben@redpanda.com>
Signed-off-by: Ben Pope <ben@redpanda.com>
pps::schema_type::avro}) | ||
.value(); | ||
pps::canonical_schema_definition expected{ | ||
R"({"type":"record","name":"foo","fields":[{"name":"bar","type":"float","extra_attr":true}]})", |
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.
So we drop the custom attribute on the schema (ignored_attr
) but not the one on the field (extra_attr
)?
This isn't a blocker but more of a Q as to why dropping one and not the other is OK.
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.
I'm just going by what's written here: apache/avro#1736
CI Failures:
They all seemed to fail at about 23:05:30 Debug seemed to fail similarly. |
/backport v22.3.x |
Cover letter
Test that #7274 is mitigated.
Signed-off-by: Ben Pope ben@redpanda.com
Backport Required
UX changes
Release notes
Improvements