RonBarabash commented on issue #131: Add the ability to update event by item id URL: https://github.com/apache/unomi/pull/131#issuecomment-590799967 Hey all, Firstly, Thank you for your responses. Our use case with Unomi is as follows: We want to build a user profile based on Internal System events that are transported through Kafka, for example When a user submits a new purchase, an event is being fired to the "OrderCreated/Updated" topic with the purchase details (Email, OrderAmount etc.). At some point in time let's say we want to add a new property to the purchase details and send it to all past events as well (for instance: OrderCurrency). We have the ability to stream all of the events from beginning time and the relevant consumers should be able to update past events with the new property. This scenario is something we already encountered several times and we build our systems in a way that entities can be updated at their persistent target. Again, if there is a way we can achieve this by not changing the core Unomi entities i would be more than happy to hear. In the way we architect our system, Unomi is not accessible from the outside (i.e the internet) of our systems, hence we do not have any security considerations. @sergehuber What do u mean by secondary id? Should we add a new property to Event and that would act as our id for updating? @sigdestad I agree with you, Can u elaborate on how would u implement this without breaking event immutability? Looking forward for your responses, 10x Ron
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
