abhibhat98 edited a comment on issue #1675: URL: https://github.com/apache/hudi/issues/1675#issuecomment-635613375
Understood! Thanks Bhavani! I'd love to take this up. I'll research and get back to you on how to proceed. Follow up question on above. How'd a consumer know the timings of the changed records? It asking a simple question, what changed for key K over the period of time (to recompute or even rollback something looking at the history). Your explanation is absolutely perfect and I tried it too, with the different times(T1/T2/T3), it works seamlessly. So, should I consider it a feature that can be added(look at the history of a record) as its completely doable. Hudi has the history of everything, it can look up by times, why can't it look up by the key? Or, is it something by design that Hudi doesn't intend to do. Or even table history would be good. As an example, Databricks delta has something called 'Describe history' which can give you the full history of the table, what changed over time and then you can rollback/time travel from those specific commit ids. Thanks again, just trying to understand what questions are right in terms of Hudi design. ---------------------------------------------------------------- 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]
