RussellSpitzer commented on issue #6725: URL: https://github.com/apache/iceberg/issues/6725#issuecomment-1414972569
That doesn't make sense to me. Would we add success on just the first time? What happens on subsequent modifications? It's way simpler to just use the Java api(if you don't want to use a full engine) to see if there are any files for a given partition. In Iceberg we also don't require files to be in any specific directory, so for example with object store location provider we end up with basically every file in its own path. Where would we keep the success file then? Again the source of truth for an iceberg table is only known by reading the current metadata.json so the Java APIs are the way to go if you don't want to use Spark or trino. Or if you want you can just listen for changes in the catalog, whenever metadata location properly has changed, you know the table has been committed to. -- 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
