Messages produce: Support TopicRecordNameStrategy & RecordNameStrategy

[iliax]

Is your proposal related to a problem?

Currently when producing message only TopicNameStrategy used to search appropriate subjects. If subject is not found by this strategy message is written as raw text. If user uses TopicRecordNameStrategy or RecordNameStrategy text msg will be written which can break downstream consumption.

Describe the solution you'd like

• on "Produce Message" page we should show which schema will be used for serialization
• if no schema found by TopicNameStrategy for topic we should be able to specify schema explicitly - there should be a dropdown with all subject names
• if schema not found and not specified then message will be treated as a text

Implementation

Backend:

• add keySubject and valueSubject fields to produce endpoint

Frontend:

• TODO: discuss

--
More details: #3244

[iliax]

relates to ISSUE: #1356

[iliax]

@Haarolean I suggest to add this to next release worklog, since this already affected some users in a bad way

[Haarolean]

#2125

[Shawcs]

+1
This issue is only for producing a message with a different strategy but in the same time it will be also coherent to have it for the consumption (hense the deserialization).

[vsevel]

very important for us. thanks.

[cdia8890]

I would love to contribute to implementing this feature. This is an important feature we're looking forward to.

[SujithPS0604]

Hello folks! Is there any update on this issue? We are eagerly waiting for the feature.

[Haarolean]

@SujithPS0604 #4255 -> https://github.com/kafbat/kafka-ui