I will change my vote to -1, as I feel this is a very critical bug which cause bad user experience. User don't know what's wrong if interpreter fails to start unless checking log. But in enterprise usage, most likely user don't have permission to access log.
I created ticket https://issues.apache.org/jira/browse/ZEPPELIN-2294 Jeff Zhang <zjf...@gmail.com>于2017年3月22日周三 上午11:19写道： 0 1. Build it from source successfully 2. Run pig tutorial using tez successfully, and dynamic form works 3. Run livy interpreter via 2 users, 2 livy sessions are created, and restarting works in scoped per user mode 4. If interpreter fails to start, the exception in interpreter is not propagated to frontend. I believe this is a regression. I try it in both livy & spark interpreter. Here's the error I see in frontend. [image: pasted1] Mina Lee <mina...@apache.org>于2017年3月22日周三 上午9:51写道： I propose the following RC to be released for the Apache Zeppelin 0.7.1 release. The commit id is 22b299b5c17c0c9ad8e54ee15bb7fde645472c65 which is corresponds to the tag v0.7.1-rc1: https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=refs/tags/v0.7.1-rc1 The release archives (tgz), signature, and checksums are here https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc1/ The release candidate consists of the following source distribution archive zeppelin-0.7.1.tgz In addition, the following supplementary binary distributions are provided for user convenience at the same location zeppelin-0.7.1-bin-all.tgz zeppelin-0.7.1-bin-netinst.tgz The maven artifacts are here https://repository.apache.org/content/repositories/orgapachezeppelin-1033 You can find the KEYS file here: https://dist.apache.org/repos/dist/release/zeppelin/KEYS Release notes available at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12339166&projectId=12316221 Vote will be open for next 72 hours (close at 19:00 24/Mar PDT). [ ] +1 approve [ ] 0 no opinion [ ] -1 disapprove (and reason why)
