This is an automated email from the ASF dual-hosted git repository.
jshao pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/gravitino.git
The following commit(s) were added to refs/heads/main by this push:
new d1ec005064 [MINOR] docs: polish Iceberg REST server document (#6444)
d1ec005064 is described below
commit d1ec00506448500f25382cbd92430c02f0369ab3
Author: FANNG <xiaoj...@datastrato.com>
AuthorDate: Thu Feb 13 12:14:14 2025 +0800
[MINOR] docs: polish Iceberg REST server document (#6444)
### What changes were proposed in this pull request?
multi catalog and view operation should shown in document side bars.
### Why are the changes needed?
User could find multi catalog configuration easily
### Does this PR introduce _any_ user-facing change?
no
### How was this patch tested?
just document
---
docs/iceberg-rest-service.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/iceberg-rest-service.md b/docs/iceberg-rest-service.md
index f89b6f2672..823ae5b03a 100644
--- a/docs/iceberg-rest-service.md
+++ b/docs/iceberg-rest-service.md
@@ -242,7 +242,7 @@ You must download the corresponding JDBC driver to the
`iceberg-rest-server/libs
If you want to use a custom Iceberg Catalog as `catalog-backend`, you can add
a corresponding jar file to the classpath and load a custom Iceberg Catalog
implementation by specifying the `catalog-backend-impl` property.
-#### View support
+### View support
You could access the view interface if using JDBC backend and enable
`jdbc.schema-version` property.
@@ -250,7 +250,7 @@ You could access the view interface if using JDBC backend
and enable `jdbc.schem
|----------------------------------------------|--------------------------------------------------------------------------------------------|---------------|----------|------------------|
| `gravitino.iceberg-rest.jdbc.schema-version` | The schema version of JDBC
catalog backend, setting to `V1` if supporting view operations. | (none)
| NO | 0.7.0-incubating |
-#### Multi catalog support
+### Multi catalog support
The Gravitino Iceberg REST server supports multiple catalogs, and you could
manage the catalog by different ways.
@@ -258,7 +258,7 @@ The Gravitino Iceberg REST server supports multiple
catalogs, and you could mana
|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------|------------------|
| `gravitino.iceberg-rest.catalog-config-provider` | The className of catalog
configuration provider, Gravitino provides build-in `static-config-provider`
and `dynamic-config-provider`, you could also develop a custom class that
implements `apache.gravitino.iceberg.service.provider.IcebergConfigProvider`
and add the corresponding jar file to the Iceberg REST service classpath
directory. | `static-config-provider` | No | 0.7.0-incubating |
-##### Static catalog configuration provider
+#### Static catalog configuration provider
The static catalog configuration provider retrieves the catalog configuration
from the configuration file of the Gravitino Iceberg REST server. You could
configure the default catalog with `gravitino.iceberg-rest.<param
name>=<value>`. For specific catalogs, use the format
`gravitino.iceberg-rest.catalog.<catalog name>.<param name>=<value>`.
@@ -297,7 +297,7 @@ You can access different catalogs by setting the `prefix`
to the specific catalo
...
```
-##### Dynamic catalog configuration provider
+#### Dynamic catalog configuration provider
The dynamic catalog configuration provider retrieves the catalog configuration
from the Gravitino server.
