asfgit closed pull request #3861:
URL: https://github.com/apache/zeppelin/pull/3861
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
asfgit closed pull request #3877:
URL: https://github.com/apache/zeppelin/pull/3877
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
Sure, I’ll share it.
2020년 8월 16일 (일) 23:12, Jeff Zhang 님이 작성:
> Hi Jongyoul,
>
> +1 for refactoring, could you provide more details about your plan of
> refactoring ?
>
> Jongyoul Lee 于2020年8月16日周日 下午3:55写道:
>
> > Hello,
> >
> > Recently, I'm checking the InterpreterSettingManager class deeply.
Jeff Zhang created ZEPPELIN-5000:
Summary: Enable user impersonation in both per user isolated and
per note isolated
Key: ZEPPELIN-5000
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5000
Project
Hi Jongyoul,
+1 for refactoring, could you provide more details about your plan of
refactoring ?
Jongyoul Lee 于2020年8月16日周日 下午3:55写道:
> Hello,
>
> Recently, I'm checking the InterpreterSettingManager class deeply.
>
> BTW, I would like to change some features including loading defaults
> interp
Hello,
Recently, I'm checking the InterpreterSettingManager class deeply.
BTW, I would like to change some features including loading defaults
interpreters.
Currently, when starting Zeppelin for the first time after downloading it,
Zeppelin checks if the file of interpreter.json onto the `conf`
Jongyoul Lee created ZEPPELIN-4999:
--
Summary: Simplify InterpreterSettingManager by dividing features
Key: ZEPPELIN-4999
URL: https://issues.apache.org/jira/browse/ZEPPELIN-4999
Project: Zeppelin
Jongyoul Lee created ZEPPELIN-4998:
--
Summary: Move to a new CI
Key: ZEPPELIN-4998
URL: https://issues.apache.org/jira/browse/ZEPPELIN-4998
Project: Zeppelin
Issue Type: Task
Repo
xiejiajun commented on pull request #3860:
URL: https://github.com/apache/zeppelin/pull/3860#issuecomment-674491597
> Sorry for late review @xiejiajun Does scala 2.12 also need the same change
?
@zjffdu , I read the code in the Scala 2.12.x branch, it seems to only
support `jvm-1.8`, a