Hey Iceberg Community, I'm following-up on the previous discussion where we decided to re-consider deprecations in the core/ module to be dropped earlier than 2.0.0. The PR <https://github.com/apache/iceberg/pull/14392> for this is up for review, thank you for everyone who took a look!
This is the question that came up during review: Other than discussing earlier removals in core/, is there any official guidance documented somewhere that mention less strict guarantees in modules other than api/. I've checked the docs and haven't found any mention of this. Do you think we should document api guarantees for better transparency? If yes, I can take a look. Best Regards, Gabor Gábor Kaszab <[email protected]> ezt írta (időpont: 2025. okt. 21., K, 18:13): > Hi Iceberg Community, > > It came up on the last community sync that in the core module we might not > want to give guarantees for deprecations to be removed in 2.0.0 and we can > drop them more aggressively. I gathered all the ones marked for 2.0.0 and > the ones missing a target release into this PR > <https://github.com/apache/iceberg/pull/14392>. > > Let me know if there are occasions where we have to be more careful and > keep the 2.0.0 removal! > > In the meantime, I think that internal usage of such deprecations should > be removed as soon as possible in case there is a clear path to move away. > Hence, I prepared these 2 PRs to avoid using > TableProperties.MANIFEST_LISTS_ENABLED > <https://github.com/apache/iceberg/pull/14347> (only usage in tests) and > avro/DataReader <https://github.com/apache/iceberg/pull/14387>. > There are some other deprecations where we have internal usage (some in > TableProperties, MetricsConfig, ViewProperties, SystemConfig) but I think > these can only be removed together with the deprecated functionality. > > Any inputs are appreciated! > Best Regards, > Gabor >
