Closed FANNG1 closed 2 months ago
@FANNG1 - I am interested in this change and would like to read some background on it. Is there a dev@g.a.o thread to DISCUSS such a large change? A design doc or proposal in wiki? Can you update the PR template with some details of what this is doing and why?
@FANNG1 - I am interested in this change and would like to read some background on it. Is there a dev@g.a.o thread to DISCUSS such a large change? A design doc or proposal in wiki? Can you update the PR template with some details of what this is doing and why?
Hi, @lmccay , I have updated the doc in the PR template, you could refer to it.
@jerryshao @caican00 please help to review when you have time, thanks.
update Iceberg REST service document in https://github.com/apache/gravitino/pull/4113
I will take a try locally to take a deep look.
@jerryshao @yuqi1129 , all comments are addressed, please help to review again
iceberg-rest-server
and iceberg-common
are placed in iceberg
moduleiceberg-rest-server
is placed in the package, the corresponding bin and conf files are placed in bin
and conf
directly../bin/gravition.sh start
to start GravitinoServer with IcebergRESTService if corresponding config is enabled, ./bin/iceberg-rest-server start
to start IcebergRESTServer only.licence
readme
are placed in package@FANNG1 can you please rebase the code.
@FANNG1 can you please rebase the code.
done
@jerryshao , all comments are addressed, please help to review again.
@jerryshao , all comments are addressed, please help to review again
What changes were proposed in this pull request?
Split IcebergRESTService into one separate module, it could be managed with or without Gravitino server.
For user
iceberg-rest-server
which contains Iceberg REST server. They both contain isolated config files and start&stop script.gravitino.iceberg-rest.
are treated as Iceberg REST server configs. likegravitino.iceberg-rest.catalog-backend
,gravitino.iceberg-rest.httpPort
, etc. Configurations for Iceberg REST server are same in isolated package and Gravitino package.For developer
The core is
RESTService
which start JettyServer for Iceberg REST server,IcebergRESTServer
which provides configuration, metricsSystem forRESTService
.RESTService
is managed as a AuxiliaryService.Why are the changes needed?
Iceberg rest service is managed as an auxiliary service in Gravitino server , for the users who want to use Iceberg REST service only, it introduces an extra burden.
Fix: #2730
Does this PR introduce any user-facing change?
yes, will add document in https://github.com/apache/gravitino/pull/4113
How was this patch tested?
related docs
https://docs.google.com/document/d/1lyJwMaaJKfMqtnH9c7LwvnOHRKm7gh8Al4Sw3T1DFjM/edit