Google Git
Sign in
apache / zeppelin / master
commit8251dc4e013cde02879d186240155da8f996bdb7[log] [tgz]
authorSeungYoung Oh <seung-00@naver.com>Thu Jan 22 15:49:09 2026 +0900
committerGitHub <noreply@github.com>Thu Jan 22 15:49:09 2026 +0900
treea172af97f7144ae60e1ee9da41671fc1aeb192c2
parenta041703dd76d6cee15a8c9c4bc6ad6d0d4767ebf [diff]
[ZEPPELIN-6366] Separate WebSocket max message size into a dedicated REST API

### What is this PR for?
Currently, configuration data is fetched through both REST API and WebSocket channels. However, the WebSocket path does not perform permission checks, and the only required data from it is the WebSocket max message size. 

I extracted the websocket max message size field into a dedicated REST API, to improve security and simplify configuration handling.

### What type of PR is it?
Improvement

### Todos
* [ ] #5060

### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/6366

### How should this be tested?
- Check the configuration page (/configuration)
- Check the notebook page (/notebook/{notebook_id})

### Screenshots (if appropriate)

### Questions:
* Does the license files need to update? N
* Is there breaking changes for older versions? Y
* Does this needs documentation? N


Closes #5099 from seung-00/feature/ZEPPELIN-6366.

Signed-off-by: ChanHo Lee <chanholee@apache.org>
11 files changed
tree: a172af97f7144ae60e1ee9da41671fc1aeb192c2
  1. .github/
  2. .husky/
  3. .mvn/
  4. alluxio/
  5. angular/
  6. bigquery/
  7. bin/
  8. build-tools/
  9. cassandra/
  10. conf/
  11. dev/
  12. docs/
  13. elasticsearch/
  14. examples/
  15. file/
  16. flink/
  17. flink-cmd/
  18. groovy/
  19. hbase/
  20. helium-dev/
  21. influxdb/
  22. java/
  23. jdbc/
  24. k8s/
  25. licenses/
  26. livy/
  27. markdown/
  28. mongodb/
  29. neo4j/
  30. notebook/
  31. python/
  32. rlang/
  33. scripts/
  34. shell/
  35. spark/
  36. spark-submit/
  37. sparql/
  38. testing/
  39. zeppelin-client/
  40. zeppelin-client-examples/
  41. zeppelin-common/
  42. zeppelin-distribution/
  43. zeppelin-examples/
  44. zeppelin-integration/
  45. zeppelin-interpreter/
  46. zeppelin-interpreter-integration/
  47. zeppelin-interpreter-parent/
  48. zeppelin-interpreter-shaded/
  49. zeppelin-jupyter/
  50. zeppelin-jupyter-interpreter/
  51. zeppelin-jupyter-interpreter-shaded/
  52. zeppelin-plugins/
  53. zeppelin-server/
  54. zeppelin-test/
  55. zeppelin-web/
  56. zeppelin-web-angular/
  57. zeppelin-zengine/
  58. .asf.yaml
  59. .gitattributes
  60. .gitignore
  61. Dockerfile
  62. LICENSE
  63. mvnw
  64. mvnw.cmd
  65. NOTICE
  66. pom.xml
  67. README.md
  68. Roadmap.md
  69. SECURITY-README.md
  70. STYLE.md
README.md

Apache Zeppelin

Documentation: User Guide
Mailing Lists: User and Dev mailing list
Continuous Integration: core frontend rat
Contributing: Contribution Guide
Issue Tracker: Jira
License: Apache 2.0

Zeppelin, a web-based notebook that enables interactive data analytics. You can make beautiful data-driven, interactive and collaborative documents with SQL, Scala and more.

Core features:

  • Web based notebook style editor.
  • Built-in Apache Spark support

To know more about Zeppelin, visit our web site https://zeppelin.apache.org

Getting Started

Install binary package

Please go to install to install Apache Zeppelin from binary package.

Build from source

Please check Build from source to build Zeppelin from source.