Hi there, Recently I had a chance to get to know the flink-table-store project. I was attracted by the idea behind it at first glance.
After reading the docs, I've got a question in my head for a while. It's about the design of the file storage. It looks like we can implement it based on the other popular open-source libraries other than creating a totally new component (lsm tree based). Hudi or iceburg looks like a good choice, since they both support change logs saving and querying. If we do it like this, there is no need to create a component for other related computation engines (spark, hive or trinno) since they are already supported by hudi or iceburg. It looks like a better solution for me instead of creating another wheel. So, here are my questions. Is there any issue not to write data as hudi or iceburg? Why don't we choose them in the first design decision? Looking forward to your answer! (Not knowing if it's a good way to ask questions here, but I didn't find another way yet. If it's not ok to ask in the mail, could someone please point the right direction for me?) Best regards, Bright.
