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
Enable data generation to a topic from within the extension interface
Schema aware, or possible required, to enable relations between fields and realistic value attributions
Controls around the rate or duration of event generation
No code required for default usecase
[Idea] Enable test frameworks to utilize library for data gen?
[Idea] Enable rehydration of the same set of generated messages to a topic?
Non-Goals
Production data manipulation or population
Complex expressions of data artifacts (keep the builder patterns simple / within reason)
Background
Launching new topics for development often results in empty message queues that require creating a producer program or performing some sort of data sanitization and sync from real sources. Populating these automatically, especially from schema structures, would be tremendously valuable in project development initialization and testing.
Proposal
Ideally there would be a call to action on each topic row to generate data. The call to action could ask some basic questions around rate of messages, duration of bursts, schema to use (default to associated schemas when possible), etc. The sidecar should be the actor that runs the generation and population effort to keep the typescript UI management code simpler and to enable this for scenarios that require different API patterns or authentication. The sidecar would need to expose a datagen API that is populated by the aforementioned fields. This would likely be a fire-and-forget route given the nature of long generation requests. That would mean there would also need to be a generation halt route (perhaps just a general kill-all-generators for simplicity).
TBD on if API key management is required to achieve this effort.
TBD on exact tool used for the individual message generation (there's some tools already built by Confluent for customers and some in open source that could be utilized)
This is in scope for the Confluent team to explore in the near term.
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
-
Goals
Non-Goals
Background
Launching new topics for development often results in empty message queues that require creating a producer program or performing some sort of data sanitization and sync from real sources. Populating these automatically, especially from schema structures, would be tremendously valuable in project development initialization and testing.
Proposal
Ideally there would be a call to action on each topic row to generate data. The call to action could ask some basic questions around rate of messages, duration of bursts, schema to use (default to associated schemas when possible), etc. The sidecar should be the actor that runs the generation and population effort to keep the typescript UI management code simpler and to enable this for scenarios that require different API patterns or authentication. The sidecar would need to expose a datagen API that is populated by the aforementioned fields. This would likely be a fire-and-forget route given the nature of long generation requests. That would mean there would also need to be a generation halt route (perhaps just a general kill-all-generators for simplicity).
TBD on if API key management is required to achieve this effort.
TBD on exact tool used for the individual message generation (there's some tools already built by Confluent for customers and some in open source that could be utilized)
This is in scope for the Confluent team to explore in the near term.
Beta Was this translation helpful? Give feedback.
All reactions