[jira] [Created] (ZEPPELIN-4328) DockerInterpreterLauncher can not run
Xun Liu created ZEPPELIN-4328: - Summary: DockerInterpreterLauncher can not run Key: ZEPPELIN-4328 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4328 Project: Zeppelin Issue Type: Sub-task Reporter: Xun Liu Fix For: 0.9.0 I found DockerInterpreterLauncher can't run. Because DockerInterpreterLauncher needs to support Standard Interpreter and spark interpreter, Rely on StandardInterpreterLauncher and SparkInterpreterLauncher. However, the StandardInterpreterLauncher and SparkInterpreterLauncher are moved to the zeppelin-zengine module in -ZEPPELIN-4227(https://issues.apache.org/jira/browse/ZEPPELIN-4227)-, and the DockerInterpreterLauncher is dynamically loaded by the classloader, so the DockerInterpreterLauncher cannot call functions in the StandardInterpreterLauncher and SparkInterpreterLauncher in different classloads.. I don't know how to solve this problem. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (ZEPPELIN-4327) Chrome autofills user name in notebook filter
Maziyar PANAHI created ZEPPELIN-4327: Summary: Chrome autofills user name in notebook filter Key: ZEPPELIN-4327 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4327 Project: Zeppelin Issue Type: Bug Components: front-end Affects Versions: 0.8.1, 0.8.0, 0.8.2 Reporter: Maziyar PANAHI If you have your username and password saved on Chrome it will keep autofill the Filter box with your username. This results of not seeing any notebook and manually has to be cleared from time to time. This won't affect if you are not saving your username password. I have found an identical issue with Hue which was reported here and it was fixed too if it helps: [https://issues.cloudera.org/browse/HUE-8727] -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: [DISCUSS] Drop Scala 2.10 support
Thanks Alex Alex Ott 于2019年9月12日周四 下午4:59写道： > I'll create a JIRA to track it, and then we can look how we can make it... > > On Tue, Sep 10, 2019 at 3:31 PM Jeff Zhang wrote: > > > Thanks for raising this discussion, @Alex. I agree to drop supporting of > > scala 2.10. > > But I will prefer to make scala 2.11 as default. Because most of the > > interpreter depends on scala 2.11. Although some interpreters support > scala > > 2.12 too, but scala 2.11 is still the most popular one I believe. Take > > spark as example, spark 2.4.4 is the latest release of spark, its default > > scala is still 2.11. > > > > One concern of dropping scala 2.10 is that it might break some > interpreter, > > such as beam, scalding, scio, I am not sure how much work needs to be > done > > to support scala 2.11 for these interpreters. And I am afraid the > > maintainer of these interpreters are not active in community now. > > > > > > > > > > > > > > Alex Ott 于2019年9月10日周二 下午7:47写道： > > > > > Hi all > > > > > > Scala 2.10 was released ~7 years ago, and latest release in that series > > was > > > ~2 years ago. > > > Right now most of the new products are built only for 2.11 & 2.12, so > > maybe > > > it makes sense to remove support of Scala 2.10 in Zeppelin 0.9? > > > > > > Also, giving the fact that 2.11 was released almost 5 years ago - > should > > be > > > 2.12 a default target? > > > > > > -- > > > With best wishes,Alex Ott > > > http://alexott.net/ > > > Twitter: alexott_en (English), alexott (Russian) > > > > > > > > > -- > > Best Regards > > > > Jeff Zhang > > > > > -- > With best wishes,Alex Ott > http://alexott.net/ > Twitter: alexott_en (English), alexott (Russian) > -- Best Regards Jeff Zhang
Re: [DISCUSS] Drop Scala 2.10 support
I'll create a JIRA to track it, and then we can look how we can make it... On Tue, Sep 10, 2019 at 3:31 PM Jeff Zhang wrote: > Thanks for raising this discussion, @Alex. I agree to drop supporting of > scala 2.10. > But I will prefer to make scala 2.11 as default. Because most of the > interpreter depends on scala 2.11. Although some interpreters support scala > 2.12 too, but scala 2.11 is still the most popular one I believe. Take > spark as example, spark 2.4.4 is the latest release of spark, its default > scala is still 2.11. > > One concern of dropping scala 2.10 is that it might break some interpreter, > such as beam, scalding, scio, I am not sure how much work needs to be done > to support scala 2.11 for these interpreters. And I am afraid the > maintainer of these interpreters are not active in community now. > > > > > > > Alex Ott 于2019年9月10日周二 下午7:47写道： > > > Hi all > > > > Scala 2.10 was released ~7 years ago, and latest release in that series > was > > ~2 years ago. > > Right now most of the new products are built only for 2.11 & 2.12, so > maybe > > it makes sense to remove support of Scala 2.10 in Zeppelin 0.9? > > > > Also, giving the fact that 2.11 was released almost 5 years ago - should > be > > 2.12 a default target? > > > > -- > > With best wishes,Alex Ott > > http://alexott.net/ > > Twitter: alexott_en (English), alexott (Russian) > > > > > -- > Best Regards > > Jeff Zhang > -- With best wishes,Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian)
[GitHub] [zeppelin] f7753 commented on issue #3422: [ZEPPELIN-4273] Support Flink 1.9 for Flink Interpreter
f7753 commented on issue #3422: [ZEPPELIN-4273] Support Flink 1.9 for Flink Interpreter URL: https://github.com/apache/zeppelin/pull/3422#issuecomment-530701802 Looking forward to this change. Any progress? 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 the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
