Hi Arun,
Do you mind to create a ticket for this kind of bug ?
Jeff Zhang 于2017年3月16日周四 下午12:23写道：
> Actually this is a bug, most of enviroment variable in interpreter-setting
> doesn't work. So try to use property instead of enviroment variable.
>
>
> Arun Khetarpal 于2017年3月16日周四 上午12:40写道：
>
Actually this is a bug, most of enviroment variable in interpreter-setting
doesn't work. So try to use property instead of enviroment variable.
Arun Khetarpal 于2017年3月16日周四 上午12:40写道：
Thanks Jeff.. In-general, IMO, there should be a better way to override
these settings atleast when i look at in
Thanks Jeff.. In-general, IMO, there should be a better way to override
these settings atleast when i look at interpreter-settings.json (pasted
below the snippet)
It seems i should have, somehow been able to define the environment
variable, ZEPPELIN_LIVY_HOST_URL somewhere to override default.
T
I have an improved version of solution b.
You can copy interpreter-setting.json (with modified zeppelin.livy.url) to
ZEPPELIN_HOME/interpreter/livy/ to override the default one.
Arun Khetarpal 于2017年3月15日周三 下午10:43写道：
> Hi Jeff -
>
> Thanks for taking out the time to help me out.
>
> Actually
Hi Jeff -
Thanks for taking out the time to help me out.
Actually i have a case of building a managed service and would like any
user who spins up a cluster with zeppelin installed, to have it work with
livy out of the box - since this use case also requires enterprise security
- following this d
Still not clear to me, do you have multiple instances of livy server ? If
there is only one livy server, then you just need to change it one time.
If you have multiple livy instances, you always need to update
zeppelin.livy.url no matter through interpreter setting ui or
programmatically.
Arun
The usecase we have is to create a service to spawn up the zepplin. Now
since i cannot override zeppelin.livy.url and the default value is set to "
https://localhost:8998"; - users which are using my service need to manually
go and change the interpreter url.
I don't know if the scenario is clear
Why is it inconvenient for you ? If you have multiple livy servers, you can
create multiple livy interpreters for each livy server in interpreter
setting page.
Arun Khetarpal 于2017年3月15日周三 下午1:25写道：
> Is there a way to set it programmatically? I find it very inconvenient for
> users to go and
Is there a way to set it programmatically? I find it very inconvenient for
users to go and modify the setting in the page - is there a better way?
Regards,
Arun
On 15 March 2017 at 04:36, Jeff Zhang wrote:
> zeppelin-site.xml is for zeppelin server, not for interpreter. You should
> set zeppeli
zeppelin-site.xml is for zeppelin server, not for interpreter. You should
set zeppelin.livy.url in interpreter setting page.
https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/quickstart/explorezeppelinui.html#settings
Arun Khetarpal 于2017年3月15日周三 上午3:16写道：
> Hi,
>
> I am trying to setup the livy i
Hi,
I am trying to setup the livy interpreter in zeppelin.
For this, i have set zeppelin.livy.url property in zeppelin-site.xml - but
in Zeppelin ui, the property of interpreter is still set to default.
Alternatively, i tried also setting it zeppelin-env.sh as export result
ZEPPELIN_LIVY_HOST_UR
11 matches
Mail list logo
