[ZEPPELIN-2910] Repository order is not respected and overridden when different from default

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.2
• Component/s: GUI, zeppelin-interpreter
• Assignee: Unassigned
• Reporter: Luca Falsina
• Created: 06/Sep/17 10:39
• Updated: 12/Dec/17 07:15

Description

I am using Zeppelin behind a corporate-proxy. For this purpose I edited the "conf/interpreter.json" file and added an extra repository "central-with-proxy" pointing to maven-central with extra proxy details. I took care to have this repository listed first in the config before the default "central" repo so that when I add an extra maven dependencies to my spark interpreter my repo should be contacted first. Still when I add the extra dependency, the order of repository is overridden every time and used in stead of my own one. This is a bug as every time I pull a dependency I have first to wait the request to time out against the "central" repo before being able to pull the dependency correctly from "central-with-proxy"

How to reproduce
1. Stop the Zeppelin service
2. Edit conf/interpreter.json and add a "test" repository before central, and local ("test", "central", "local")
3. Start the Zeppelin service, navigate to the "Interpreter" UI.
4. Edit the Spark interpreter and add a new dependency (e.g., joda-time:joda-time:2.9.9)

You will now see the conf/interpreter.json file being rewritten with the default repo order ("central", "local", "test"). In the logs there is a line on the property being updated:

 INFO [2017-09-06 12:16:49,863] ({qtp1624015642-14} InterpreterRestApi.java[updateSetting]:138) - Update interpreterSetting 2CS1Z6WDS

And the default order will wrongly be used for pulling dependencies.