Technology Stack
| Area | Implementation |
|---|---|
| Server build | JDK 17 and Maven 3.9.x, enforced by the root build |
| Server frameworks | Managed Spring/Spring Security, Jetty, Jersey, Jakarta APIs, Guice, and EclipseLink dependencies |
| Agent and Server utilities | Python source minimum 3.9.2 with locked upstream dependencies and package-specific native ABI |
| Main Web UI | React, TypeScript, Vite, and Vitest under the latest frontend module |
| Administration UI | Separate React Admin module packaged with Ambari |
| Management persistence | Configured relational database and JDBC driver |
| Historical monitoring | Prometheus-compatible exporters/VMAGENT and VictoriaMetrics |
| Configuration and extension metadata | Stack/service XML and JSON, Themes, telemetry descriptors, JMX profiles, and View definitions |
The Java guide records effective framework versions and deferred major migrations. The Python guide explains why a higher interpreter version does not automatically satisfy a package built for another minor ABI.
Build Tools Versus Runtime
Maven and Node/npm belong in the build environment; they are not general prerequisites on every managed cluster node. Deploy the resulting reviewed packages, not a frontend development server or a mutable system-Python installation.
The default RPM target uses CPython 3.9 wheels. Architecture and alternative ABI profiles select separate artifacts. See RPM packaging and building from source.
Managed Services
The reviewed BIGTOP tree contains 3.2.0, 3.3.0, and 3.4.0 definitions with inheritance. Select the Stack and component versions qualified for the candidate. These directory names do not make the Ambari release 3.4.0, and the Ambari JDK does not override every service's JDK.
Stack-provided service metadata remains the authority for packages, configuration, dependencies, and lifecycle commands. Use Stack definitions and the Bigtop build guide when extending or rebuilding service packages.
Source References
The root build, managed dependency versions, and BIGTOP metadata provide the implementation references.