GuoZhaoY commented on issue #7663:
URL: https://github.com/apache/gravitino/issues/7663#issuecomment-3083005812

   > > Hi [@lsyulong](https://github.com/lsyulong) , thanks for propose the 
degisn. I'm wondering if we can abstract the REST server interface, so that 
Paimon, Iceberg, or other engines like Lance can implement this interface. At 
the same time, we can perform auditing, metadata management, and other tasks 
within the interface. However, currently, the REST specifications of various 
engines are different, so it may not be easy to achieve this.
   > 
   > [@neuyilan](https://github.com/neuyilan) teacher,Thank you for proposing 
the abstraction of REST server interfaces! This is indeed an architectural 
question worth deep discussion.
   > 
   > I think there are two feasible approaches:
   > 
   > Approach 1: Abstract Unified Interface
   > 
   > Advantages: Code reuse, unified management, good maintainability 
Challenges: May require refactoring the existing Iceberg REST server, designing 
an abstraction layer for REST servers Approach 2: Independent REST Server 
Implementation
   > 
   > Advantages: Simple implementation, high flexibility, risk isolation 
Challenges: Code duplication, maintenance costs Considering Gravitino's current 
development stage and community resources, I suggest we start with Approach 2 
for the following reasons:
   > 
   > Incremental Development: We can get the Paimon REST server up and running 
quickly to gain experience Risk Reduction: Avoid refactoring that could impact 
the existing stable Iceberg REST server - would we need additional testing for 
the current Iceberg REST server? Requirements Validation: Implement multiple 
REST servers first, then abstract a better, more flexible abstraction layer 
that fits Gravitino's architecture, allowing us to better validate and test 
based on actual experience Of course, these are just my personal thoughts. If 
you have better ideas or designs for the abstract unified interface, we can 
discuss them together - I'd love to learn from you!
   
   Whether using Plan 1 or Plan 2, if manpower is needed, I am more than happy 
to participate in the improvement of this feature


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