datalake_agent: service framework (Java)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start in contrib/datalake_agent after verifying the B0 dependency, then run the planned Maven verification and review the in-process gRPC and Unix-socket test coverage. Done means the two-phase startup, transport security, version handshake, interceptors, configuration mapping, credential scrubbing, UNIMPLEMENTED business RPCs, catalog default, RAT headers, and stated CI acceptance checks all pass.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Part of #2008. Letters (A, B0–B7, C, D, E) are the PRs listed there; this is B1.
Scope
contrib/datalake_agent: JDK 17, Maven, Guice, Netty gRPC. No Iceberg in it yet.
- Two-phase startup: bind and serve health first, build the injector and flip to SERVING second.
- Transport: Unix socket by default with configured permissions; TCP only with TLS and a 0600 bearer-token file (current plus rotation-grace token).
- Interceptors: request context, exception → status with
BusinessErrorCode(no stack trace leaves the process), version handshake refusing an old client and naming both versions. - HOCON config for process concerns only; everything about a table travels in the request. One request mapper turns the fdw's options into Iceberg property maps.
- Credential scrubbing in logs; opt-in metrics.
- Every business RPC answers UNIMPLEMENTED naming the RPC. Catalog management present, off by default.
- In-process gRPC tests, a Unix-socket test, negative TLS/token tests; CI runs
mvn -B verify; RAT headers. The PostgreSQL build does not need Java.
Out of scope
Iceberg operations and catalogs (B3+), the proxy bgworker, installing the jar through make install.
Depends on
B0.
Acceptance
- Cold start to SERVING under 1.5 s in CI; health answers on the socket.
- Old client refused naming both versions; TCP without TLS refuses to start; bad token is UNAUTHENTICATED; business RPCs are UNIMPLEMENTED naming the RPC.
- A fake key in config and request never appears in DEBUG logs (asserted by test).
mvn -B verifyand RAT green in CI.
- Lenguaje dominante
- C
- Estrellas
- 1.4k
- Forks
- 248
- Merge medio
- 4 d 10 h
- PR fusionados (30 d)
- 40
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/cloudberry
-
type: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
apache/cloudberry#1885 · 2 reacciones ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
apache/cloudberry#1825 ·
-
type: Bug
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
apache/cloudberry#2048 · 1 reacción ·
-
type: Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 40/100
apache/cloudberry#2047 ·
-
type: Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
apache/cloudberry#2046 · 1 comentario ·
Todos los issues de apache/cloudberry
Issues similares
-
task
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
vsanthanam/JBird#429 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
bug documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
es-ude/OnDeviceTraining#459 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
bilelmoussaoui/gobject-linter#199 · 1 comentario ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
bradcypert/plum#53 ·