akhilputhiry commented on issue #9174:
URL: https://github.com/apache/iceberg/issues/9174#issuecomment-2679112040
Found another active issue mentioning the same
https://github.com/apache/iceberg/issues/12059
--
This is an automated message from the Apache Git Service.
To respond to the
akhilputhiry commented on issue #9174:
URL: https://github.com/apache/iceberg/issues/9174#issuecomment-2679038286
@sungwy I am also facing this issue. Any suggestions
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
github-actions[bot] commented on issue #9174:
URL: https://github.com/apache/iceberg/issues/9174#issuecomment-2425313651
This issue has been closed because it has not received any activity in the
last 14 days since being marked as 'stale'
--
This is an automated message from the Apache Gi
github-actions[bot] closed issue #9174: Proxy support unavailable for iceberg
spark client
URL: https://github.com/apache/iceberg/issues/9174
--
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 spec
sravanscb commented on issue #9174:
URL: https://github.com/apache/iceberg/issues/9174#issuecomment-1993875583
Hi @syun64
Yes, there should be a way to properly pass the proxy configs to the iceberg
client and it be utilized by the code. I tried several ways - at the system
level and sp
syun64 commented on issue #9174:
URL: https://github.com/apache/iceberg/issues/9174#issuecomment-1992179279
Maybe having specific proxy configurations for the REST Catalog would be
better than relying on the SystemProperties?
It *looks* like the connection manager is taking the config
sravanscb opened a new issue, #9174:
URL: https://github.com/apache/iceberg/issues/9174
### Apache Iceberg version
1.3.1
### Query engine
Spark
### Please describe the bug 🐞
I am trying to use iceberg 1.3 jars in Spark 3.2 -
iceberg-spark-runtime-3.2_2.12-1
