Currently the TopicDetails contains separate fields for various configs, ie. cleanupPolicy, retentionMs etc.
This should be a list of key -> value pairs so we can add as many as we need w/o modifying the model itself.
BTW what is size: Long ?
Also we should use a more like Resource based approach AddTopicRequest is not great naming, we should have a function addTopic which will receive a TopicDetails is a bit confusing because TopicDetails and AddTopicRequest should contain the same stuff (yes including clusterId)
We must do this unless we want UpdateTopicRequest, etc.
Currently the
TopicDetailscontains separate fields for various configs, ie.cleanupPolicy,retentionMsetc.This should be a list of
key -> valuepairs so we can add as many as we need w/o modifying the model itself.BTW what is
size: Long?Also we should use a more like
Resourcebased approachAddTopicRequestis not great naming, we should have a functionaddTopicwhich will receive aTopicDetailsis a bit confusing becauseTopicDetailsandAddTopicRequestshould contain the same stuff (yes includingclusterId)We must do this unless we want
UpdateTopicRequest, etc.