FANNG1 commented on code in PR #4631:
URL: https://github.com/apache/gravitino/pull/4631#discussion_r1727103974


##########
docs/iceberg-rest-service.md:
##########
@@ -117,7 +117,7 @@ Gravitino Iceberg REST service supports using static 
access-key-id and secret-ac
 For other Iceberg s3 properties not managed by Gravitino like `s3.sse.type`, 
you could config it directly by `gravitino.iceberg-rest.s3.sse.type`.
 
 :::info
-Please set `gravitino.iceberg-rest.warehouse` to 
`s3://{bucket_name}/${prefix_name}` for Jdbc catalog backend, 
`s3a://{bucket_name}/${prefix_name}` for Hive catalog backend.
+Please set `gravitino.iceberg-rest.warehouse` to 
`s3://{bucket_name}/${prefix_name}` for Jdbc catalog backend, 
`s3a://{bucket_name}/${prefix_name}` for Hive catalog backend and download 
[Iceberg AWS 
bundle](https://mvnrepository.com/artifact/org.apache.iceberg/iceberg-aws-bundle)
 and place it to the classpath of Iceberg REST server.

Review Comment:
   updated
   



##########
docs/lakehouse-iceberg-catalog.md:
##########
@@ -80,7 +80,7 @@ Supports using static access-key-id and secret-access-key to 
access S3 data.
 For other Iceberg s3 properties not managed by Gravitino like `s3.sse.type`, 
you could config it directly by `gravitino.bypass.s3.sse.type`.
 
 :::info
-Please set `gravitino.iceberg-rest.warehouse` to 
`s3://{bucket_name}/${prefix_name}` for JDBC catalog backend, 
`s3a://{bucket_name}/${prefix_name}` for Hive catalog backend.
+Please set `warehouse` to `s3://{bucket_name}/${prefix_name}` for JDBC catalog 
backend, `s3a://{bucket_name}/${prefix_name}` for Hive catalog backend and 
download [Iceberg AWS 
bundle](https://mvnrepository.com/artifact/org.apache.iceberg/iceberg-aws-bundle)
 and place it to `catalogs/lakehouse-iceberg/libs/`.

Review Comment:
   updated
   



-- 
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]

Reply via email to