search

redpanda-data / console

Redpanda Console is a developer-friendly UI for managing your Kafka/Redpanda workloads. Console gives you a simple, interactive approach for gaining visibility into your topics, masking data, managing consumer groups, and exploring real-time data with time-travel debugging.
https://redpanda.com
3.76k stars 346 forks source link

Produce proto messages #476

Open cipriansofronia opened 1 year ago

cipriansofronia commented 1 year ago

A nice addition would be to be able to produce proto messages with the schema provided by either when producing the message or by selecting/providing the schemaId from schema-registry, more or less how kafka-rest can produce.

OuesFa commented 1 year ago

It would be super helpful if the same could be applied to Avro. I hope I haven't overlooked any existing features that already provide this.

twmb commented 11 months ago

Incoming in next release, closing for now

pantaoran commented 9 months ago

Hi @twmb , could you link to a specific commit or PR that I could look at?

I'm wondering if this will include only the Protobuf option like first requested or also the Avro option. And is there any information about when the 2.4 release might happen?

weeco commented 9 months ago

This was semi-complete (producing Avro and Protobuf messages), but the flow to produce typed messages (due to a missing example/schema information) was too confusing, which is why decided to hide this functionality in the UI at the moment. We will get back to this very soon

Petkomat commented 1 month ago

Almost a year later, I cannot find the option to produce Avro messages. Is this option expected to appear in the near future?

weeco commented 1 month ago

It's currently not planned for the next few months, but there's no reason not to add it. We are working on other things, but we haven't forgotten about producing typed messages. It's a good chunk of work to do this properly.

twmb commented 1 month ago

@Petkomat when I mentioned this was incoming in the next release, it was before we really planned what the full quarter of work would look like, and we thought this would be a smaller task. We scheduled a bunch of time for all things schema registry with this item included, but unfortunately, this one item actually ended up being more work than we anticipated.