Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy Settings for catalog REST API client #12059

Open
1 of 3 tasks
sfc-gh-dtriana opened this issue Jan 22, 2025 · 1 comment
Open
1 of 3 tasks

Proxy Settings for catalog REST API client #12059

sfc-gh-dtriana opened this issue Jan 22, 2025 · 1 comment
Labels
improvement PR that improves existing functionality

Comments

@sfc-gh-dtriana
Copy link

Feature Request / Improvement

Despite configuring a proxy for the driver or executor

spark.driver.extraJavaOptions="-Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort="
spark.executor.extraJavaOptions="-Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort="

Calls made by the Spark engine using Iceberg REST API do not follow the above proxy configurations,

This is a feature request for the ability to configure proxy settings when connecting to an Iceberg Rest API Catalog via Spark. This is especially critical for organizations where network access to catalog services is restricted and must go through a corporate proxy.

Query engine

Spark

Willingness to contribute

  • I can contribute this improvement/feature independently
  • I would be willing to contribute this improvement/feature with guidance from the Iceberg community
  • I cannot contribute this improvement/feature at this time
@sfc-gh-dtriana sfc-gh-dtriana added the improvement PR that improves existing functionality label Jan 22, 2025
@flyrain
Copy link
Contributor

flyrain commented Jan 22, 2025

Thanks @sfc-gh-dtriana for raising it. We could enable this feature on Java REST clients(class RESTSessionCatalog), ensuring that all Java-based engines, including Spark, can benefit from it seamlessly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement PR that improves existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants