qingwei727 opened a new issue, #9791:
URL: https://github.com/apache/gravitino/issues/9791
### What would you like to be improved?
### What would you like to be improved?
Gravitino Paimon catalog currently supports three backend types:
`filesystem`, `hive`, and `jdbc`. However, it does not support the `rest`
backend, which is an important feature in Apache Paimon for enabling REST
catalog service.
Apache Paimon supports REST catalog backend, which allows integration with
various REST catalog implementations such as Aliyun DLF (Data Lake Formation).
Without explicit support for REST backend properties in Gravitino, users have
to rely on the `gravitino.bypass.` prefix to pass REST-related configurations,
which is cumbersome and lacks proper validation.
### How should we improve?
Add first-class support for Paimon REST catalog backend in Gravitino by:
1. **Add explicit property definitions for REST backend**
- `token-provider`: Generic token provider type (e.g., `bearer`, `dlf`)
- REST backend specific properties with proper mapping to Paimon backend
2. **Support Aliyun DLF as the initial REST catalog implementation**
- `dlf-access-key-id` → `dlf.access-key-id`
- `dlf-access-key-secret` → `dlf.access-key-secret`
- `dlf-security-token` → `dlf.security-token`
- `dlf-token-path` → `dlf.token-path`
3. **Update documentation**
- Add REST backend section in Paimon catalog documentation
- Provide configuration examples for DLF
**Example Configuration:**
```json
{
"name": "dlf_paimon",
"type": "RELATIONAL",
"provider": "lakehouse-paimon",
"properties": {
"catalog-backend": "rest",
"uri": "https://cn-hangzhou-vpc.dlf.aliyuncs.com";,
"warehouse": "oss://bucket/path",
"token-provider": "dlf",
"dlf-access-key-id": "<ak>",
"dlf-access-key-secret": "<akSK>"
}
}
### How should we improve?
_No response_
--
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]
