-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#516] feat(doc): add Iceberg REST service document #538
Conversation
Code Coverage Report
|
docs/iceberg-rest-service.md
Outdated
| `gravitino.auxService.iceberg-rest.catalog-backend` | Catalog backend of Gravitino Iceberg REST server | `jdbc`| | ||
| `gravitino.auxService.iceberg-rest.uri` | The jdbc connection address | `jdbc:postgresql://127.0.0.1:5432/`| | ||
| `gravitino.auxService.iceberg-rest.warehouse ` | Warehouse directory of JdbcCatalog, you should set HDFS prefix explictly if using HDFS | `/user/hive/warehouse-jdbc/`| | ||
| `gravitino.auxService.iceberg-rest.jdbc.user` | The username of the Jdbc connection| `jdbc username`| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we align with gravitino iceberg catalog to use "jdbc-user" and "jdbc-password".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'd better not align with gravitino iceberg catalog. Gravitino configuration rule is somehow complex, introducing other rules like bypass
, it's hard for Iceberg REST configuration to follow Gravitino configuration completely and will introduce complexity for Iceberg REST server users (maybe not Gravitino Iceberg REST catalog users.)
What changes were proposed in this pull request?
add Iceberg REST service documnet
Why are the changes needed?
Fix: #516
Does this PR introduce any user-facing change?
No
How was this patch tested?
just document