Ankur SAINI created ZEPPELIN-6232:
-------------------------------------
Summary: Two repositories with the name "central" appear in the
interpreter settings UI.
Key: ZEPPELIN-6232
URL: https://issues.apache.org/jira/browse/ZEPPELIN-6232
Project: Zeppelin
Issue Type: Bug
Reporter: Ankur SAINI
We are running Zeppelin on Kubernetes and aim to replace the default central
repository with an authenticated version. Upon reviewing the project's Java
code, we discovered that creating a new repository with the same name
effectively replaces the existing one
([AbstractDependencyResolver.java|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/dep/AbstractDependencyResolver.java#L81]),
and the updated configuration is correctly saved in the {{interpreter.json}}
file. However, in the Zeppelin UI, two repositories appear: one labeled
"central" (now configured with authentication) and another showing the local
default repositories.
However, upon restarting the Zeppelin server, the default central repository is
recreated, and the custom repository with the same name is added as a separate
entry instead of replacing the existing one (see
[InterpreterSettingManager.java|https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterSettingManager.java#L313]).
As a result, the {{interpreter.json}} file ends up containing three repository
entries: one for the default local repository and two entries with the ID
"central." Upon reviewing the source code, we observed that during server
startup, the default central repository is not overwritten in the same way it
is when a new repository is added through the UI or API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
