I think what we are trying to solve here are real pain points in the development process, where you have to release Sidecar in order to unblock a feature in Analytics, and you have to release Analytics in order to fix an issue in Sidecar. That's a real issue today, it has become a velocity issue too. We've seen PRs pile up, because a release of the other project is needed before the patch can be merged.
Analytics will still be released as its own artifact, and if you don't have a coupling to sidecar, you can just consume artifacts that do not have Sidecar dependencies. I think we can make a better effort of separating dependencies so that they can be used independently for specific use cases. Best, - Francisco On 2026/06/03 16:42:15 James Berragan 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 > > >
