You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2022/01/27 18:54:39 UTC

[GitHub] [iceberg] anuragmantri commented on issue #3994: Allow table properties defaults to be configured at catalog level

anuragmantri commented on issue #3994:
URL: https://github.com/apache/iceberg/issues/3994#issuecomment-1023540702


   +1 to this request. We also have some properties that we want to set as admins like `write.object-storage.enabled` that we don't want users to set or worry about. As @jackye1995 mentioned we could have three levels
   - default - users can override
   - required - users cannot override
   - Another category for anything that can be added to defaults. (In spark we do that for properties like `spark.executor.extraJavaOptions` etc. Not sure if Iceberg has such properties). 
   
   I can take a look at how this can be done. Any suggestions welcome.


-- 
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-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org