Refactor AwsProperties into separated properties classes
Open
not-stale
- Dominant language
- Java
- Stars
- 9.2k
- Forks
- 3.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 132
Description
### Feature Request / Improvement
As we briefly discussed in a previous community sync, the `AwsProperties` class is growing too big now. It was kind of an intentional design when we just get started with the `iceberg-aws` module to make people's life easy by just needing to use 1 class for all configs, but it seems to be not getting the effect we want. So my idea is to gradually move all client configs to separated classes and eventually deprecate `AwsProperties`.
@nastra @danielcweeks @amogh-jahagirdar @singhpk234 @rajarshisarkar do you have any thoughts or concerns about this?
### Query engine
None
Contributor guide
Assessment
This issue has not been assessed yet.