> > I worry if we move into the Sidecar repo it's just going to become more > coupled and folks in the community are already using Analytics to read from > e.g. S3 buckets or other data sources. >
I have similar concerns. If we start releasing them in lockstep from the same repo, then I worry that people will start making breaking changes to sidecar APIs such that existing Analytics jars out in the wild will not work, without realizing it. Both cassandra-analytics and the cassandra-sidecar are starting to be used out in the world by people in production settings. My expectation for updates to the sidecar APIs is that anything done should not break existing clients, when the client and the server are in different repos, it is much cleaner and clearer to people that you are exposing an API surface which is being consumed externally, and you need to keep things like backwards compatibility in mind. If the client and the server live in the same repo, and are released together, I can see people just changing/refactoring both and not considering existing clients out in the wild. I think them being in separate repos makes that distinction clearer to someone working on a new feature that spans both code bases. Seems like many here want them in the same repo, so I won’t block that, but I have concerns. If we do decide to merge them, I think it should be in a new repo with a new name. I do not think the sidecar belongs in a repo names analytics, or the analytics library belongs in a repo named sidecar. They both have use cases that do not involved the other. -Jeremiah Jordan On Jun 3, 2026 at 11:42:15 AM, James Berragan <[email protected]> wrote: > Can we break down a bit more where the circular dependency lies, I'm not > against it, I just want to make sure we're solving the right problem here. > Analytics and CDC were always designed to be agnostic of the Sidecar. What > stops us moving just the Sidecar specific parts into the Sidecar repo? I > worry if we move into the Sidecar repo it's just going to become more > coupled and folks in the community are already using Analytics to read from > e.g. S3 buckets or other data sources. > > James. > > On Tue, 2 Jun 2026 at 13:20, Josh McKenzie <[email protected]> wrote: > >> I'd like to propose we merge the cassandra-sidecar >> <https://github.com/apache/cassandra-sidecar> and cassandra-analytics >> <https://github.com/apache/cassandra-analytics> repositories. I've >> shopped the idea around to some of you and gotten universally positive >> feedback with some questions about details we deferred to this discussion. >> >> *Reasons we should merge:* >> >> - Break circular dependencies between the 2 projects >> - Remove redundant copy/pasted code >> - Simplify build and CI >> - Reduce friction on changes that span both projects >> - Simplify the CDC implementation >> >> >> *Outstanding questions and observations that came up:* >> >> - Do we merge one repository into the other? Or do we create a new >> project and bring them both in? >> - What do we do about JIRA? Leave separate or combine? >> - What do we do with open issues and PR's in github? >> - We'll need to thoughtfully update CI (github + circle) since we're >> right at the limit on the free tier on both projects >> - What do we do about existing deprecated repositories >> (cassandra-analytics and/or cassandra-sidecar)? >> - We'll need to update our release process >> >> >> Other observations or questions welcome, as are thoughts on the entire >> process, on the outstanding questions, etc. >> >> Looking forward to the discussion everyone. >> >> ~Josh >> >
