-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
I'm experiencing an issue with SeaTunnel's Iceberg connector when trying to specify a custom OAuth2 URI with REST catalog type. The connector doesn't appear to support custom OAuth2 URI configuration for Iceberg REST Catalog.
SeaTunnel Version
2.3.11
SeaTunnel Config
sink {
Iceberg {
catalog_name = "iceberg"
// Nessie catalog properties
iceberg.catalog.config = {
uri = "http://nessie:19120/iceberg/main"
catalog-impl = "org.apache.iceberg.rest.RESTCatalog"
warehouse = "s3://***/"
s3.endpoint="http://minio:9000"
s3.region="us-east-1"
s3.path-style-access=true
s3.aws-access-key="***"
s3.aws-secret-key="***"
// OAuth2 configuration attempts
rest.oauth2.token-uri = "https://my-custom-auth-server/oauth/token" // This doesn't work
rest.client.id = "my-client-id"
rest.client.secret = "my-client-secret"
}
namespace = "demo"
table = "fake_data_table"
}
}
Running Command
curl --location 'http://127.0.0.1:9090/submit-job/upload' --form 'config_file=@"/***/config/fake-to-iceberg-nessie.conf"'Error Exception
Try to connect to oauth/token with URI of Nessie Api.
Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct