yuqi1129 commented on code in PR #9243: URL: https://github.com/apache/gravitino/pull/9243#discussion_r2559842146
########## docs/fileset-catalog-with-s3.md: ########## @@ -121,7 +121,13 @@ s3_catalog = gravitino_client.create_catalog(name="test_catalog", </Tabs> :::note -When using S3, ensure that the location value starts with s3a:// (not s3://) for AWS S3. For example, use s3a://bucket/root, as the s3:// format is not supported by the hadoop-aws library. +- When using S3, ensure that the location value starts with s3a:// (not s3://) for AWS S3. For example, use s3a://bucket/root, as the s3:// format is not supported by the hadoop-aws library. +- When using MinIO or other S3-compatible storage services, make sure to set the `s3-endpoint` property to the appropriate endpoint URL. +- When using MinIO or other S3-compatible storage services, you may need to set additional properties such as `s3-path-style-access` to `true` depending on the storage service requirements. You can do this in Gravitino's `fileset.conf` file with the "gravitino.bypass." prefix: Review Comment: @shaofengshi > Setting "gravitino.bypass.fs.s3a.path.style.access=true" in the fileset catalog properties couldn't work. Does it not work if we put `gravitino.bypass.fs.s3a.path.style.access=true` in catalog properties? That is to say, setting `gravitino.bypass.fs.s3a.path.style.access = true` when creating the catalog can't let us connect to the MinIO filesystem successfully? -- 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]
