c form.
>
>
>
> *From: *Mohit Jaggi
> *Reply-To: *"users@zeppelin.apache.org"
> *Date: *Friday, November 3, 2017 at 5:20 PM
>
>
> *To: *"users@zeppelin.apache.org"
> *Subject: *Re: Livy interpreter Scala code string interpolation
>
>
>
&g
com>>
Reply-To: "users@zeppelin.apache.org<mailto:users@zeppelin.apache.org>"
mailto:users@zeppelin.apache.org>>
Date: Friday, November 3, 2017 at 4:48 PM
To: "users@zeppelin.apache.org<mailto:users@zeppelin.apache.org>"
mailto:users@zeppelin.apache.org
zeppelin.apache.org"
>> *Date: *Friday, November 3, 2017 at 4:48 PM
>> *To: *"users@zeppelin.apache.org"
>> *Subject: *Re: Livy interpreter Scala code string interpolation
>>
>>
>>
>>
>>
>> Yes, this is due to the dynamic forms of zep
t; *Reply-To: *"users@zeppelin.apache.org"
> *Date: *Friday, November 3, 2017 at 4:48 PM
> *To: *"users@zeppelin.apache.org"
> *Subject: *Re: Livy interpreter Scala code string interpolation
>
>
>
>
>
> Yes, this is due to the dynamic forms of zeppelin.
&g
But somehow Spark interpreter works without this problem. Why is that the case
if the problem is on Zeppelin UI side?
From: Jeff Zhang
Reply-To: "users@zeppelin.apache.org"
Date: Friday, November 3, 2017 at 4:48 PM
To: "users@zeppelin.apache.org"
Subject: Re: Livy in
Yes, this is due to the dynamic forms of zeppelin.
Mohit Jaggi 于2017年11月4日周六 上午2:28写道：
> I run into similar issues with shell scripts that use ${var}. Can we use a
> different magic notation for Z, one that has a lower chance of colliding
> with shell scripts and Scala code? This will be hard to
I run into similar issues with shell scripts that use ${var}. Can we use a
different magic notation for Z, one that has a lower chance of colliding
with shell scripts and Scala code? This will be hard to do due to the
variety of interpreters supported. Perhaps this can be made configurable?
On Fri
