laskoviymishka commented on PR #459:
URL: https://github.com/apache/iceberg-go/pull/459#issuecomment-2977630441
I think this is still a problem.
From what I see in other Glue clients, parameters are typically passed as
CLI flags instead of a JSON file.
CLI flags are more self-describing (you can view them directly with --help)
and much more convenient to use.
Currently, using a custom JSON schema adds an unnecessary layer of
complexity - it's less clear to the user and makes maintenance more cumbersome.
Could we consider following the pattern used by other tools in the ecosystem?
See for example Iceberg Catalog Migrator
```
java -jar iceberg-catalog-migrator-cli.jar migrate \
--source-catalog-type GLUE \
--source-catalog-properties
warehouse=s3a://example-bucket/gluecatalog/,io-impl=org.apache.iceberg.aws.s3.S3FileIO
\
--target-catalog-type NESSIE \
--target-catalog-properties uri=http://...,warehouse=s3a://...,io-impl=...
```
Another option is simply by-pass this as `AWS_*` env-vars, as it done in
https://py.iceberg.apache.org/cli/
--
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
