mildbyte commented on issue #11608:
URL: https://github.com/apache/iceberg/issues/11608#issuecomment-3118038278
We have the same issue with Spark:
```
exec /opt/spark/sbin/start-connect-server.sh \
--packages
"org.apache.spark:spark-connect_2.12:3.5.3,io.delta:delta-spark_2.12:3.0.0,org.apache.iceberg:iceberg-spark-runtime-3.5_2.12:1.9.2,org.apache.iceberg:iceberg-gcp-bundle:1.9.2,org.apache.iceberg:iceberg-aws-bundle:1.9.2"
\
--conf "spark.driver.extraJavaOptions=-Divy.cache.dir=/tmp
-Divy.home=/tmp" \
--conf
"spark.sql.extensions=io.delta.sql.DeltaSparkSessionExtension,org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions"
\
--conf
"spark.sql.catalog.preexisting=org.apache.iceberg.spark.SparkCatalog" \
--conf "spark.sql.catalog.preexisting.type=rest" \
--conf "spark.sql.catalog.preexisting.uri=http://rest-catalog-1/catalog";
\
--conf "spark.sql.catalog.preexisting.warehouse=warehouse-1" \
--conf "spark.sql.catalog.preexisting.token=$access_token" \
"$@"
```
then, when I start a Spark Connect session that has a startup config to use
another catalog that supports S3 remote signing, and I query a table from that
second catalog, I see Spark sending requests to `/catalog/v1/aws/s3/sign` from
the _first_ catalog, which fails.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
