[GitHub] zeppelin issue #3179: [ZEPPELIN-3773] - add check permission on write.
Github user Savalek commented on the issue: https://github.com/apache/zeppelin/pull/3179 Need someone else to check this PR. Because I could not reproduce this error. ---
[GitHub] zeppelin issue #3179: [ZEPPELIN-3773] - add check permission on write.
Github user deradam commented on the issue: https://github.com/apache/zeppelin/pull/3179 This seems to be the bug that we are also facing currently. I have a notebook with some users that only have read permissions. These users receive an error message that the do not have the update permission on the notebook and therefore cannot open it. Any estimate when this will be merged and released? ---
[GitHub] zeppelin issue #3179: [ZEPPELIN-3773] - add check permission on write.
Github user mebelousov commented on the issue: https://github.com/apache/zeppelin/pull/3179 @Savalek You're right. I fix my shiro.ini. But I still see a huge amount of background queries (up to 100 per second) connected with Helium. I can reproduce the issue in development mode. Tested on Ubuntu 16.04, Chromium (Version 69.0.3497.92) and Firefox Quantum 62.0 Check please. ---
[GitHub] zeppelin issue #3179: [ZEPPELIN-3773] - add check permission on write.
Github user Savalek commented on the issue: https://github.com/apache/zeppelin/pull/3179 @felixcheung, there is already a check on the server. Due to some errors, a commit of the paragraph went to the server and an error occurred. ---
[GitHub] zeppelin issue #3179: [ZEPPELIN-3773] - add check permission on write.
Github user Savalek commented on the issue: https://github.com/apache/zeppelin/pull/3179 @mebelousov, Perhaps you have incorrectly configured shiro.ini. ---
[GitHub] zeppelin issue #3179: [ZEPPELIN-3773] - add check permission on write.
Github user mebelousov commented on the issue: https://github.com/apache/zeppelin/pull/3179 @Savalek I see an infinite number of GET request like http://localhost:8080/api/helium/suggest/2DMKVSPYC/20180807-154514_2063688624 with response "401 Unauthorized" is case if user don't have permission for write. Could you fix? ---