gary created FLINK-32434:
----------------------------
Summary: missing s3 config by catalog
Key: FLINK-32434
URL: https://issues.apache.org/jira/browse/FLINK-32434
Project: Flink
Issue Type: Bug
Components: FileSystems
Affects Versions: 1.17.0
Reporter: gary
After FLINK-30704, s3 config (s3 prefix) by catalog doesn't work. It works fine
in Flink 1.16.
example: [https://paimon.apache.org/docs/master/filesystems/s3/]
{code:java}
CREATE CATALOG my_catalog WITH (
'type' = 'paimon',
'warehouse' = 's3://path/to/warehouse',
's3.endpoint' = 'your-endpoint-hostname',
's3.access-key' = 'correct-user',
's3.secret-key' = 'yyy'
); {code}
exception:
{code:java}
Caused by: org.apache.flink.table.api.ValidationException: Unable to create
catalog 'xxx'
Catalog options are:
's3.access-key'='correct-user'
's3.endpoint'= http://x.x.x.x:xx/'
's3.secret-key'='*******
'type'='paimon'
'warehouse'='s3://xxx/'
at
org.apache.flink.table.factories.Factoryutil.createcataalog(FactoryUtil.java:439)
at
org.apache.flink.table.api.internal.TableEnvironmentImpl.creat::Catalog(TableEnvironmentimpl.java:1466)
at
org.apache.flink.table.api.internal.TableEnvironmentImpl.executeInter:nal(TableEnvironmentImpl.java:1212)
at
org.apache.flink.table.gateway.service.operation.OperationExecutor.callOperation(OperationExecutor.java:541)
at
org.apache.flink.table.gateway.service.operation.OperationExecutor.executeOperation(OperationExecutor.java:440)
at
org.apache.flink.table.gateway.service.operation.OperationExecutor.executeStatement(OperationExecutor.java:195)
at
org.apache.flink.table.gateway.service.SqlGatewayServiceImpl.lambda$executeStatement$1(SqlGatewayServiceImpl.java:212)
at
org.apache.flink.table.gateway.service.operation.OperationManager.lambda$submitoperation$1(OperationManager.java:119)
at
org.apache.flink.table.gateway.service.operation.OperattionManager$Operation.lambda$run$0(OperationManager.java:258)
... 7 more
Caused by: java.lang.RuntimeException: java.nio.file.AccessDeniedException:
s3://xxx/default.db: getFileStatus on s3://xxx/default.db:
com.amazonaws.services.s3.model.AmazonS3Exception: Forbidden (Service: Amazon
S3; Status Code: 403; Error Code: 403 Forbidden; Req
uest ID: 176A9F853B408F0E; S3 Extended Request ID:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855; Proxy: nul1),
S3 Extended Request ID:
e3b8c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855:403 Forbidden
at org.apache.paimon.catalog.FileSystemCatalog.uncheck(FilLeSystemCatalog.
java:207)
at ofg.apache:paimon.catatog.FitesystemCatalog.createpatabase(FitesystemCa
at org.apache.paimon.flink.FlinkCatalog.<init>(FlinkCatalog.java:112)
at
org.apache.paimon.flink.FlinkCatalogFactory.createCatalog(FlinkCatalogFactory.java:70)
at
org.apache.paimon.flink.FlinkCatalogFactory.createCatalog(FlinkCatalogFactory.
java:58)
at
org.apache.paimon.flink.FlinkCatalogFactory.createCatalog(FlinkCatalogFactory.
java:32)
at org.apache.flink.table.factories.Factoryutil.createcataalog(FactoryUtil.
java:436)
... 15 more {code}
Flink access s3 by user defined in flink-conf.yaml, not 'correct-user' in
catalog, causes Forbidden.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
