lsyulong opened a new issue, #7853:
URL: https://github.com/apache/gravitino/issues/7853

   ### Describe the proposal
   
   ## Overview  
   Implement a comprehensive Paimon REST server as an auxiliary service in 
Apache Gravitino, following the same architectural patterns as the existing 
Iceberg REST server. This will provide REST API endpoints for managing Paimon 
databases, tables, snapshots, branches, partitions, views, and functions.  
     
   ## Background  
   Apache Gravitino already has a Paimon catalog implementation and an Iceberg 
REST server. This epic aims to create a similar REST server for Paimon to 
provide direct REST API access to Paimon metadata operations.  
     
   ## Architecture  
   The implementation will follow the GravitinoAuxiliaryService pattern, 
similar to the existing IcebergRESTService, and integrate with the current 
Paimon catalog implementation.  
     
   ## Related Documentation  
   - [Paimon Catalog 
Documentation](https://gravitino.apache.org/docs/latest/lakehouse-paimon-catalog)
  
   - [Iceberg REST Server 
Implementation](https://github.com/apache/gravitino/tree/main/iceberg/iceberg-rest-server)
  
   
   ### Task list
   
   - [ ] #[SUBTASK_1] Core Infrastructure Setup  
   - [ ] #[SUBTASK_2] Configuration Management  
   - [ ] #[SUBTASK_3] Catalog Integration  
   - [ ] #[SUBTASK_4] Database Operations  
   - [ ] #[SUBTASK_5] Table Operations  
   - [ ] #[SUBTASK_6] Snapshot Management  
   - [ ] #[SUBTASK_7] Branch Management  
   - [ ] #[SUBTASK_8] Partition Management  
   - [ ] #[SUBTASK_9] View and Function Support  
   - [ ] #[SUBTASK_10] Configuration and Metrics  
   - [ ] #[SUBTASK_11] Exception Handling and Serialization  
   - [ ] #[SUBTASK_12] Integration Testing  
   - [ ] #[SUBTASK_13] Documentation and Configuration  


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