mirror of
https://github.com/apache/zeppelin
synced 2026-05-24 09:38:26 +00:00
|
Some checks failed
core / core-modules (11) (push) Has been cancelled
core / interpreter-test-non-core (11) (push) Has been cancelled
core / interpreter-test-jupyter-python-rlang (11, 3.9) (push) Has been cancelled
core / zeppelin-integration-test (11) (push) Has been cancelled
core / flink-test-and-flink-integration-test (115, 3.8) (push) Has been cancelled
core / flink-test-and-flink-integration-test (116, 3.9) (push) Has been cancelled
core / flink-test-and-flink-integration-test (117, 3.9) (push) Has been cancelled
core / spark-integration-test (11) (push) Has been cancelled
core / spark-test (11, 3.9) (push) Has been cancelled
core / spark-test (17, 3.9) (push) Has been cancelled
core / livy-0-8-with-spark-3-2-under-python39 (push) Has been cancelled
core / default-build (11) (push) Has been cancelled
core / windows-build (11) (push) Has been cancelled
frontend / npm-audit (push) Has been cancelled
frontend / run-e2e-tests-in-zeppelin-web (push) Has been cancelled
frontend / run-playwright-e2e-tests (anonymous, 3.9) (push) Has been cancelled
frontend / run-playwright-e2e-tests (auth, 3.9) (push) Has been cancelled
frontend / test-selenium-with-spark-module-for-spark-3-5 (push) Has been cancelled
quick / license-check (push) Has been cancelled
quick / maven-validate (push) Has been cancelled
### What is this PR for? This PR merges the `zeppelin-zengine` module into `zeppelin-server` to simplify the project architecture. The zengine module contained core engine functionality for notebook management, paragraph execution, and interpreter management, which is tightly coupled with the server. This merge reduces build complexity while preserving all git history using `git mv` for file movements. **Note:** The previous blocker (maven-shade-plugin corrupting ZeppelinConfiguration string literals) has been resolved by [ZEPPELIN-6400](https://github.com/apache/zeppelin/pull/5167), which moved ZeppelinConfiguration out of `zeppelin-interpreter` into `zeppelin-zengine` and replaced interpreter-side usage with Properties-based configuration. ### What type of PR is it? Refactoring ### Todos * [x] Move all source files from zeppelin-zengine to zeppelin-server using git mv (192 files) * [x] Merge zengine dependencies into zeppelin-server pom.xml * [x] Update zeppelin-plugins to depend on zeppelin-server instead of zeppelin-zengine * [x] Update zeppelin-interpreter-integration dependencies * [x] Update zeppelin-integration dependencies * [x] Remove zeppelin-zengine module from root pom.xml * [x] Update shell scripts (bin/*.sh, bin/*.cmd) * [x] Update GitHub Actions workflows * [x] Remove zeppelin-zengine directory * [x] Update documentation and code references * [x] Add commons-logging exclusions (per reviewer feedback) * [ ] Verify CI passes ### What is the Jira issue? * ZEPPELIN-6355 ### How should this be tested? * CI ### Screenshots (if appropriate) ### Questions: * Does the license files need to update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Closes #5095 from jongyoul/ZEPPELIN-6345. Signed-off-by: Jongyoul Lee <jongyoul@gmail.com> |
||
|---|---|---|
| .. | ||
| contribution | ||
| helium | ||
| writing_zeppelin_interpreter.md | ||