Github user gss2002 commented on the issue:
https://github.com/apache/zeppelin/pull/1458
Also input validation is secure java coding best practice regardless..
http://www.oracle.com/technetwork/java/seccodeguide-139067.html#5
---
If your project is set up for it, you can reply to
Github user gss2002 commented on the issue:
https://github.com/apache/zeppelin/pull/1458
Well we will just agree to disagree
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1458
@spektom I agree with you not to add zeppelin-env.* because it depends on
Live only.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user spektom commented on the issue:
https://github.com/apache/zeppelin/pull/1458
@r-kamath I've added documentation to the `zeppelin-env.sh.template` file,
but I couldn't find any other option related to Livy interpreter in
`zeppelin-site.xml.template`, so I've left this file
Github user r-kamath commented on the issue:
https://github.com/apache/zeppelin/pull/1458
@spektom thanks for the improvement. Can you also
update`conf/zeppelin-env.sh.template` and `conf/zeppelin-site.xml.template`
with env name/property name and description.
---
If your project
Github user spektom commented on the issue:
https://github.com/apache/zeppelin/pull/1458
@AhyoungRyu Added, thanks for pointing it out to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1458
Hi @spektom. Thanks for your contribution :)
As you said
>Yes. Documenting zeppelin.livy.spark.sql.truncateResult option.
But it seems there is no docs file change. The
