snazy commented on PR #1844: URL: https://github.com/apache/polaris/pull/1844#issuecomment-2958845620
Thanks @adnanhemani for tackling the effort. It looks that this change introduces another serialization implementation, although we already have Jackson in place. Can you explain why that's needed? It's a bit unclear why these "buffers" are needed. Would you mind elaborating on this? I have some concerns around how the approach could be implemented in the NoSQL world, via #1189. There we already have a way to iterate over recent changes (aka: events). Do you have some idea around how both could live together? Would be nice to consider NoSQL in this new approach, because we already agreed that NoSQL will become part of Polaris. I think it's better to have a way that satisfies both persistence worlds. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
