You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Dmitri Bourlatchkov <di...@apache.org> on 2026/03/09 22:51:34 UTC
[DISCUSS] Invalid handling of headers in Iceberg 1.10.0 leading to incorrect Polaris Realm propagation to the credentials endpoint
Hi All,
Heads up: I've just run into an issue with Iceberg 1.10.0, where session
headers are not propagated to the `/credentials` endpoint calls.
Basically, if Spark has --conf
spark.sql.catalog.polaris.header.Polaris-Realm=MyRealms then loadTable
happens in the right reals, but if Spark has to refresh storage credentials
the call to /credentials does not have a Polaris-Realm header, resulting in
its executing in the *default* realm.
I was able to reproduce it locally.
The bug appears to be in the Iceberg java code. I believe 1.9.0 and later
versions are affected.
I'll keep investigating tomorrow.
Cheers,
Dmitri.
Re: [DISCUSS] Invalid handling of headers in Iceberg 1.10.0 leading to incorrect Polaris Realm propagation to the credentials endpoint
Posted by Dmitri Bourlatchkov <di...@apache.org>.
This appears to have been fixed by Iceberg PR [15110] (not released yet).
[15110] https://github.com/apache/iceberg/pull/15110
Cheers,
Dmitri.
On 2026/03/09 22:51:34 Dmitri Bourlatchkov wrote:
> Hi All,
>
> Heads up: I've just run into an issue with Iceberg 1.10.0, where session
> headers are not propagated to the `/credentials` endpoint calls.
>
> Basically, if Spark has --conf
> spark.sql.catalog.polaris.header.Polaris-Realm=MyRealms then loadTable
> happens in the right reals, but if Spark has to refresh storage credentials
> the call to /credentials does not have a Polaris-Realm header, resulting in
> its executing in the *default* realm.
>
> I was able to reproduce it locally.
>
> The bug appears to be in the Iceberg java code. I believe 1.9.0 and later
> versions are affected.
>
> I'll keep investigating tomorrow.
>
> Cheers,
> Dmitri.
>