Jongyoul Lee
Jongyoul Lee
@dependabot rebase it
By the way, I assume we can deploy two versions of Apache Zeppelin with current and new UI in some ways like setting parameters when packaging them and so on....
>We have the 'web-angular' profile, which builds the new user interface. This should definitely be switched on by default when the default interface is changed. As far as I can...
I have a question. In this PR, will we permanently change the default web to a new one? I intended to release two versions with an old and new UI...
> @jongyoul The current release bundles both classic and new UI, and allows users to switch to each other by clicking a button, the proposed approach "change new UI to...
Yes, I hope so. For the release project, we can edit the release script to release two versions but we still need to change some code in ZeppelinServer and so...
Thank you for checking it. By the way, I'm still worried about providing the new UI as a default for the next release but let's see how's going. I suggest...
As Cheng said, I thought we would have a configuration storing the type of UI and the Zeppelin server uses it. But, we don't have that kind of configuration yet...
> I would like to see the actual benefits before pushing this change. for now, I only see breaking changes. We need to mitigate `zeppelin-interpreter` dependency. Currently, `zeppelin-interpreter` is quite...
> To address the above issue, I think we should separate the optional dependencies into individual modules, then we can eliminate them in some interpreters, but is zeppelin-protocol that case?...