set92 commented on issue #9960: URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2673967103
@nastra I don't know how to ask this without it sound wrong. But is Iceberg ready for production? Because I would say that `UPDATE` is a common command to run, and it has been broke almost 1 year. I'm using EMR, so for this issue seems my workaround is to do an INSERT, combine the previous column with the new one, and then delete the new one (basically doing an update manually). Because I can't go below EMR 7.0.0 that would be required to not have this bug. But is not the first issue that I find without many answers or acknowledgements, which lets me asking if Iceberg is ready for production. Again, I don't say it as an attack, but because I'm starting a big project on the company, implementing every table with Iceberg, and I'm concern about how the state of Iceberg. In my case, I'm running it from EMR Serverless 7.7.0, with S3 Tables. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
