[GitHub] zeppelin pull request #3012: [SECURITY] Upgrade py4j version to 0.10.7

Github user jongyoul closed the pull request at: https://github.com/apache/zeppelin/pull/3012 ---

[GitHub] zeppelin issue #3012: [SECURITY] Upgrade py4j version to 0.10.7

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3012 @jongyoul There's more thing needs to be done for upgrading py4j to 0.10.7. py4j 0.10.7 introduce authentication mechanism for connecting gateway server, so we also need to update

[GitHub] zeppelin issue #3000: [ZEPPELIN-3467] two-step, atomic configuration file

Github user Tagar commented on the issue: https://github.com/apache/zeppelin/pull/3000 > The orphaned file will not be automatically overwritten later because File.createTempFile(...) will always attempt to create a new filename that is unused in the directory. That makes

All PySpark jobs are canceled when one user cancel his PySpark paragraph (job)

Dear community, Currently we are having problems with multiple users running paragraphs associated with pyspark jobs. The problem is that if an user aborts/cancels his pyspark paragraph (job), the active pyspark jobs of the other users are canceled too. Going into detail, I've seen that when

[jira] [Created] (ZEPPELIN-3535) Disable flaky tests

Jeff Zhang created ZEPPELIN-3535: Summary: Disable flaky tests Key: ZEPPELIN-3535 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3535 Project: Zeppelin Issue Type: Test