[#321] feat(core): add auxiliary service support in Graviton

[FANNG1]

What changes were proposed in this pull request?

add a aux service to graviton to support Iceberg REST server

Why are the changes needed?

support Iceberg REST server

part: #321
will propose another PR to start Iceberg REST server.

Does this PR introduce any user-facing change?

add Iceberg REST server

How was this patch tested?

1. UT
2. start the Iceberg REST server in local env.

design docs

https://docs.google.com/document/d/1N_9NtaoHIeKQ36Q4fYZ9eGDotvjlB0-7lHKSoT76IZk/edit#heading=h.kbhoexq6d6ba

[github-actions]

Code Coverage Report

Overall Project	62.58% -0.76%	🟢
Files changed	50.95%	🔴

Module	Coverage
server	89.37%	🟢
core	71.51% -2.67%	🔴

Files

Module	File	Coverage
server	GravitonServer.java	57.96%	🟢
core	MapUtils.java	89.29% -10.71%	🟢
	CatalogManager.java	66.31% -0.33%	🔴
	AuxiliaryServiceManager.java	58.56% -41.44%	🔴
	IsolatedClassLoader.java	44.41% -17.82%	🔴
	Config.java	37.8%	🟢
	GravitonEnv.java	0% -18.24%	🔴

[xunliu]

Hi @sandflee
When the Integration Test fails in the GitHub Action.

• You can execute ./gradlew clean && ./gradlew build && ./gradle compileDistribution && ./gradle integrationTest in you local.
• Or click Print logs when Graviton integration tests failure section in the GitHub Action, It will print logs/graviton-server.log in the GitHub Action to help you see the error log.

[xunliu]

@sandflee Do you rebase your develop branch to the latest main branch?

Error: Exception in thread "main" java.lang.IllegalArgumentException: Invalid package path: catalogs/lakehouse/libs
	at com.datastrato.graviton.utils.IsolatedClassLoader.buildClassLoader(IsolatedClassLoader.java:82)
	at com.datastrato.graviton.aux.GravitonAuxServiceManager.registerAuxService(GravitonAuxServiceManager.java:56)
	at com.datastrato.graviton.aux.GravitonAuxServiceManager.lambda$registerAuxServices$2(GravitonAuxServiceManager.java:87)
	at java.util.Iterator.forEachRemaining(Iterator.java:116)
	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
	at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
	at com.datastrato.graviton.aux.GravitonAuxServiceManager.registerAuxServices(GravitonAuxServiceManager.java:85)
	at com.datastrato.graviton.aux.GravitonAuxServiceManager.serviceInit(GravitonAuxServiceManager.java:113)
	at com.datastrato.graviton.GravitonEnv.initialize(GravitonEnv.java:84)
	at com.datastrato.graviton.server.GravitonServer.initialize(GravitonServer.java:50)
	at com.datastrato.graviton.server.GravitonServer.main(GravitonServer.java:93)

[yuqi1129]

add a aux service to graviton to support Iceberg REST server

Can you provide a more detailed description of this PR?

[FANNG1]

add a aux service to graviton to support Iceberg REST server

Can you provide a more detailed description of this PR?

add design docs~

We do not have privileges to access this document.

[jerryshao]

How do you configure the "classpath" config, is it a relative path or a absolute path?

[FANNG1]

it supports both relative path and absolute path, if it's a relative path, it relative to gravitonHome

[FANNG1]

if tested in MiniGraviton, catalogs jars is placed in catalog-xx/build/libs/, will try to get aux test classpath in auxServiceTestClassPaths if in test mode

[jerryshao]

I think we can inject the configuration when running mini graviton mode, I don't think it is a good idea to hardcode here.