The first layer API/SPI seems like a no-brainer, the second layer seems more convoluted and not as general purpose as the first layer. It also seems that people could actually build their own history database tailored to their use-cases using the first layer to populate the database.
Laurent On Tue, Oct 29, 2024 at 10:58 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi folks, > > I would like to discuss a new proposal for a polling notification API. > The proposal actually contains two "layers": > - Entities change notification API (optionally with Java client to > poll): a client can receive notifications when an event happens on an > entity (containing the entity type, like table, view, namespace, > catalog, ...). Events can be entities created, modified, deleted. The > use case is basically to have both maintenance anticipation, > incremental index update, actions triggering. > - Entities change history: a client can get the list of all entities > changes in the past N duration (hours, minutes, seconds). It could be > an async or sync operation. The use case is about reconciliation and > auditing. > > Thoughts ? > > If there's no objections, I will work on a proposal document (with > much more details) that I will share on the dev mailing list (and also > create a GitHub Issue with "proposal" tag). > > Regards > JB >
