Blake-Guo commented on issue #6613: URL: https://github.com/apache/iceberg/issues/6613#issuecomment-1386108491
Thanks @RussellSpitzer . So depending on if the user accesses the Iceberg Table through `sparkSession.sql` or `sparkSession.read().*.load(*)`, Spark's CatalogManager might load the Spark conf at different stages, which results in the wired behavior in this post, in other words, some bugs in the Spark side, is that what you mean? -- 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]
