Thanks Greg!
I think sorting results (at least w/r/t pagination) is only valuable if
it's part of a formal contract; otherwise, a REST extension wouldn't really
be able to take advantage of that behavior without becoming brittle across
non-major version changes. I'd opt on the side of leaving it o
Hey Chris,
Thanks for your quick reply!
Design 1:
I think this is a completely reasonable way to implement a V1, without any
more complicated pagination.
I had not considered that a REST extension would be able to add pagination,
but upon reflection that makes a lot of sense.
I like the best-ef
Hi Greg,
Thanks for your thoughts.
RE your design questions:
1. The responses in the REST API may grow fairly large for sink connectors
that consume from a large number of Kafka topic partitions, and source
connectors that store a wide range of source partitions. If there is a
large amount of da
Hey Chris,
Thanks for the KIP!
I think this is an important feature for both development and operations
use-cases, and it's an obvious gap in the REST feature set.
I also appreciate the incremental nature of the KIP and the future
extensions that will now be possible.
I had a couple of questions
