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
I am doing an analysis on using kafka rest proxy via docker-compose.
In analyzing the documentation I came across the versioning of the V2 and V3 APIs.
Essentially in V2 there are the basic APIs for testing a simple process :
consumer instance -> create topic (single partition) -> subscribe to topic (/subscription or /assignement) -> create records -> consumer read records
I have a doubt though, not explicit, about V3 that goes beyond the concept of open-source.
I would like to understand the real goal of this new version. For example, I would have expected to find an updated version of the API /records which is not there. However, in this version there are also APIs that are complementary to those already present on V2 such as updating the partitions of a topic.
From what I noticed there is more reliance on the cluster part, so I ask what are the goals of the V3 and what will be the future improvements?
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
I am doing an analysis on using kafka rest proxy via docker-compose.
In analyzing the documentation I came across the versioning of the V2 and V3 APIs.
Essentially in V2 there are the basic APIs for testing a simple process :
I have a doubt though, not explicit, about V3 that goes beyond the concept of open-source.
I would like to understand the real goal of this new version. For example, I would have expected to find an updated version of the API /records which is not there. However, in this version there are also APIs that are complementary to those already present on V2 such as updating the partitions of a topic.
From what I noticed there is more reliance on the cluster part, so I ask what are the goals of the V3 and what will be the future improvements?
Thank you.
The text was updated successfully, but these errors were encountered: