ajantha-bhat opened a new pull request, #6789: URL: https://github.com/apache/iceberg/pull/6789
Consider the scenario, a) client1 - java Nessie catalog client creates a table1 b) client2 - spark + iceberg+ Nessie creates a table2 c) client3 - another java Nessie catalog client creates a table3 where all the 3 clients are connected to the same Nessie server. Now for the first client (client1), list tables show only one table even though all 3 clients are connected to the same Nessie server. The reason is only the catalog APIs that involves table operations (like `loadTable()`, `commit()`, etc) refresh the `NessieIcebergClient`. The APIs like `listTables()`, `listNamespaces()` use the old state as it doesn't use table operations. Changes: - Pass null for the reference hash in api request for immutable references. So that server will use the latest hash Other scenarios can be two concurrent spark sessions. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
