rymurr commented on pull request #1783: URL: https://github.com/apache/iceberg/pull/1783#issuecomment-730431248
> Why not do something like the following, which can make the whole thing more backwards compatible: I was thinking similar but as per #1587 we don't want to hold catalog configs in the hadoop `Configuration`. Logically we would then put the catalog config into `option`s. To me this leads to verbose/repetitive `read`/`write` statements (see below). I am looking for a solution that still enables session wide catalog configs to be set and this [comment](https://github.com/apache/iceberg/pull/1587#discussion_r521614936) implied that it is technically possible. ``` df.write.format("iceberg") .mode("append") .option("catalog-impl", "com.my.own.CatalogImpl") .option("catalog-option1", "value1") .option("catalog-option2", "value2") ... .save("testing.foo") ``` ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
