Hey folks Option 4.1 is what was posted as the proposed solution for "early access" in the 3.6 release email thread earlier in the day today. Please refer to the document attached to that email thread: https://lists.apache.org/thread/9chh6h52xf2p6fdsqojy25w7k6jqlrkj and leave your thoughts on that thread.
-- Divij Vaidya On Fri, Aug 4, 2023 at 6:03 PM Andrew Schofield <andrew_schofield_j...@outlook.com> wrote: > > Hi Christo, > I agree with you. > > Option 4.1 without a KIP seems like an acceptable starting point for something > which will be relatively rare, provided that it’s easy for the user to get a > list of the > topics that have to be deleted before they can successfully start the broker > with > TS turned off. > > Option 4.2 in the future with a KIP improves things later on. > > Thanks, > Andrew > > > On 4 Aug 2023, at 16:12, Christo Lolov <christolo...@gmail.com> wrote: > > > > Hello all! > > > > I wanted to gather more opinions for > > https://issues.apache.org/jira/browse/KAFKA-15267 > > > > In summary, the problem which I would like to solve is disabling TS (and > > freeing the resources used by RemoteLog*Manager) because I have decided I > > no longer want to use it without having to provision a whole new cluster > > which just doesn't have it enabled. > > > > My preference would be for option 4.1 without a KIP followed by option 4.2 > > in the future with a KIP once KIP-950 makes it in. > > > > Please let me know your thoughts! > > > > Best, > > Christo >
