I agree that the analytics library will need to support vnodes. To be clear, there’s nothing preventing the solution from working with vnodes right now, and no assumptions about a 1:1 topology between a token and a node. However, we don’t, today, have the ability to test vnode support end-to-end. We are working towards that, however, and should be able to remove the caveat from the released analytics library once we can properly test vnode support. If it helps, I can update the CEP to say something more like “Caveat: Currently untested with vnodes - work is ongoing to remove this limitation” if that helps?
Doug > On Mar 24, 2023, at 11:43 AM, Brandon Williams <dri...@gmail.com> wrote: > > On Fri, Mar 24, 2023 at 10:39 AM Jeremiah D Jordan > <jeremiah.jor...@gmail.com> wrote: >> >> I have concerns with the majority of this being in the sidecar and not in >> the database itself. I think it would make sense for the server side of >> this to be a new service exposed by the database, not in the sidecar. That >> way it can be able to properly integrate with the authentication and >> authorization apis, and to make it a first class citizen in terms of having >> unit/integration tests in the main DB ensuring no one breaks it. > > I don't think this can/should happen until it supports the database's > default configuration with vnodes.
