Stefan - I understand the motivation behind this feature. I totally am for introducing it. I just have a couple questions -
1. What is Cassandra's behavior when custom constraints are used but are missing on disk? I'm imagining a situation where someone failed to include the jar in their deployment? 2. I would really like the community to bring their custom constraints back to the project when possible. I imagine we could have a separate constraints repo that they can contribute their constraints creating an ecosystem for domain specific constraints that are reusable but we may not want to ship in Cassandra by default. Users could optionally load these into Cassandra if they'd like. None of these questions / suggestions are blockers to moving ahead with it. Thanks, Dinesh On Fri, Aug 15, 2025 at 8:53 AM Štefan Miklošovič <smikloso...@apache.org> wrote: > I do not see any more activity on this thread so I will proceed. This does > not seem to be controversial as there is already precedent in place and > nobody vehemently objects. > > Regards > > On Mon, Aug 11, 2025 at 7:57 PM Mick <m...@apache.org> wrote: > >> >> >> > >> > I have 0 issues with ServiceLoader, but I think the bigger question is >> “what is a public api”. >> >> >> >> Let's also please be clear in separating what are our public SPIs and our >> public APIs, as compatibility concerns are different for each. We >> typically refer to both when mentioning API, but in the code something that >> ends up being both can become unnecessarily painful. >> >