Github user Tagar commented on the issue:
https://github.com/apache/zeppelin/pull/2834
What happens when a notebook had code {something} and "something" doesn't
exist as a 'z' variable?
Would it be possible to review that comment I left earlier in
https://github.com/apache/zeppelin/pull/2502#issuecomment-324095161
Should we have a Zeppelin option that controls this behavior?
> Option 1 if used - it'll completely follow Jupyter bahavior (no error,
{..} block return unchanged).
> Option 2 - fail explicitly if variable in curly braces can't be found.
> That being said, I think most of folks may actually prefer option 1, as
introduction of { .. } may be a breaking change for some notebooks' code. So I
think Option 1 should be default.
Because this change may break code in some users' notebooks (if they had
curly braces), it would be nice to let users choose if they want to use Option
1 (so their code will be compatible / not broken by this PR), or Option 2 which
would tell them explicitly that variable isn't found.
---
