Re: Flink Interpreter for Java 1.8.0

2019-05-28 Thread Jeff Zhang
Hi Ravi, Thanks for the interest on flink on zeppelin. Currently it doesn't support flink 1.8, I am working on it, try to support flink 1.9 which is supposed to be released this summer. BTW, could you let me know what scenario do you use flink on zeppelin ? Thanks Ravi Pullareddy 于2019年5月28日周二

Re: Zeppelin log files in windows

2019-05-28 Thread Jeff Zhang
Hi Ravi, Sorry for the inconvenience. The community has no bandwidth to keep the stability of zeppelin on windows. I would recommend you to install zeppelin in linux if that works for you. Ravi Pullareddy 于2019年5月28日周二 上午9:24写道: > Hi Folks > > > > Windows version of Zeppelin 0.8.1 has a typo e

RE: 0.9 Zeppelin release schedule

2019-05-28 Thread Pastrana, Rodrigo (RIS-BCT)
Jeff, we were interested in the password input for forms, but found it wasn’t as secure as we hoped since it stores passwords in notebooks and made them accessible to all users. We’re looking for a mechanism to store custom credentials (our users will need to provide user/pass to access our back

RE: Flink Interpreter for Java 1.8.0

2019-05-28 Thread Ravi Pullareddy
Hi Jeff Thanks for your clarification. We currently use Kafka, ElasticSearch , MongoDb & SQL with our event store systems. Flink has been good framework to interact with these systems in realtime as it has various connectors. Zeppelin gives added advantage wherein we are able to use it for analy

Apache Zeppelin meetup. 2/June at Shanghai, China

2019-05-28 Thread Xun Liu
Hi folks, We're having an Apache Zeppelin meetup on 2/June at Shanghai, China. I will share here, the following new features: 1. Zeppelin distributed clustering feature 2. Zeppelin interpreter on yarn 3. Zeppelin interpreter on Docker 4. Zeppelin integration hadoop submarine for mach

Re: 0.9 Zeppelin release schedule

2019-05-28 Thread Jeff Zhang
Make sense, feel free to create a ticket for it. Pastrana, Rodrigo (RIS-BCT) 于2019年5月29日周三 上午2:04写道: > Jeff, we were interested in the password input for forms, but found it > wasn’t as secure as we hoped since it stores passwords in notebooks and > made them accessible to all users. We’re looki