This may potentially be another thread, but I want to see if we can avoid
excess work/design discussions by utilizing an open policy engine rest api (
https://www.openpolicyagent.org/docs/latest/rest-api/
)that’s already defined and used in Trino now (
https://trino.io/docs/current/security/opa-acc
I still need to start a discussion thread on how to handle catalogs in 2.0
and forward. If there aren't many people using the Dynamo catalog, it still
makes sense to deprecate and remove it. Even if we move catalogs to a
separate repo, we don't want to support more of them than necessary.
On Tue,
Looks like Ajantha already reverted it now in
https://github.com/apache/iceberg/pull/9815 so let's just keep it as is for
1.5.
As I listed in the PR just now, I think there are 3 options:
1. Salesforce can move it to a Salesforce GitHub domain and own it
2. my team can potentially move it to an Am
I don't think we need to revert a deprecation. Deprecation gives people
time to move off of something that won't be supported in the future and it
doesn't make sense to me to delay letting people know that.
On Mon, Feb 26, 2024 at 11:34 PM Ajantha Bhat wrote:
> Looks like Salesforce is using the
Hi Everyone,
I propose that we release the following RC as the official Apache Iceberg
1.5.0 release.
The commit ID is e39ec185d7879c1a310769d33e0b1b6ad12486a9
* This corresponds to the tag: apache-iceberg-1.5.0-rc4
* https://github.com/apache/iceberg/commits/apache-iceberg-1.5.0-rc4
*
https://gi
