Github user orenpai commented on the issue:
https://github.com/apache/zeppelin/pull/1970
To summarize, es-hadoop is aware that from command line, non spark.*
parameters get ignored so they created a workaround to allow setting the
parameters through spark.es.* parameters.
Either
Github user orenpai commented on the issue:
https://github.com/apache/zeppelin/pull/1970
Posted
https://discuss.elastic.co/t/using-es-hadoop-with-zeppelin-and-the-use-of-es-nodes/88392
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user orenpai commented on the issue:
https://github.com/apache/zeppelin/pull/1970
As far as I can tell from the code, yes - it does some verification of this
value on the driver, and then passes it after processing to the executors.
@costin might be able to provide more
Github user orenpai commented on the issue:
https://github.com/apache/zeppelin/pull/1970
@zjffdu @Leemoonsoo I believe this is a mistake, and poses a real problem
for me and other Zeppelin users.
While it's true that the properties file is being skimmed to remove any
non-
