You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we produce messages curren serialization logic looks like
receive input message (key+value) as a text
search for key & value schemas using TopicNameStrategy (-key, -value postfixes)
if schema(s) are found - we try to serialize key/value using it and throw error if it is not possible
if shema(s) not found - we treat input k/v as a string.
Problems:
schema search is done implicitly - we don't show in UI what schema will be used for serialization (of no schema will be used). It can cause problems for consumers and can break whobe downstream processing.
if user is using RecodNameStrategy or TopicRecordNameStrategy for subject naming he can't explicitly set desired subject name
Suggestions:
In produce page we should:
show subject that will be used for serializing both key and value. It can be a dropdown near key & value input area
by default we should show "Raw String"/ "No Schema" if no subject found for k/v using TopicNameStrategy. Or corresponding subject names found by TopicNameStrategy.
User should be able to override found subjects. (ex. using dropdown list with embedded search field).
Also, it can be useful if we will allow to chose version of chosen schema
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Current behavior:
When we produce messages curren serialization logic looks like
Problems:
Suggestions:
In produce page we should:
CC @germanosin @Haarolean
Beta Was this translation helpful? Give feedback.
All reactions