Hello,
Thank you for your opinion. Almost all opinions show that we'd better keep
Shell interpreter.
Following Apache rule, I'll make a vote in two days. Please leave your
various opinions.
Best regards,
Jongyoul Lee
2024년 4월 15일 (월) 오후 6:59, Danny Cranmer 님이 작성:
> +1 for keeping the interpret
Hello,
If I remember correctly, Zeppelin tried to keep backward compatibility for
0.X versions until 0.11.0. We made some break changes on 0.11.0 including
deprecating some interpreters[1] and this Shell interpreter issue.
By the way, we'd better explain which Zeppelin supports the specific
versi
+1 I think it would be good to have a clear expectation around the
backwards compatibility of upgrades in Zeppelin.
There needs to be some nuance here... Since the functionality surface area
around interpreters is relatively large, it might be hard to ensure all
features are available per interpre
Hello all,
I was reading the shell interpreter thread [1], and it made me wonder about
the backwards compatibility guarantees that Zeppelin offers. As a user, I
would expect to be able to upgrade from 0.11.0 > 0.11.1 without breaking
changes or losing functionality. I would not expect to lose an i
+1 for keeping the interpreter. It poses no additional security risk to any
interpreter that runs arbitrary code. For instance, it is equivalent to
running Python subprocess commands (unless I am missing something).
Thanks,
Danny
On Mon, Apr 15, 2024 at 9:57 AM Cheng Pan wrote:
> I think the re
I think the real issue here is that the user is logged in with a normal
account, but runs a shell script using the system account, which is an
escalation of privileges.
Considering the feature has existed for a long period, and the user knows the
behavior, it’s good to reserve it as long as the
