Re: Main Helium package file empty
If anyone knows a way to make Zeppelin ignore having to pull down this file upon restart, I would appreciate the guidance. Thanks, Jonathan Greenleaf On Thu, Nov 21, 2019, 11:07 AM Mor Yariv wrote: > Seems like it's fixed now. > > On Thu, Nov 21, 2019 at 3:03 PM Mor Yariv wrote: > >> Hey all, >> It looks like the main helium.json file which Zeppelin downloads from S3 >> is empty: >> >> $ curl https://s3.amazonaws.com/helium-package/helium.json >> [{}] >> >> Head object says it was modified just an hour ago at Thu, 21 Nov 2019 >> 12:02:26 GMT. >> >> Can this be fixed please? Or is there a backup file somewhere we can >> point our clusters to in the meantime? >> >> Thanks, >> Mor Yariv >> >
pyspark run a specific paragraph
Haven't had luck with documentation. What is the syntax to run a specific paragraph using the pyspark interpreter? I'm using Version 0.8.0-SNAPSHOT. %pyspark z.run('20170227-213250_876580864') .. AttributeError: 'PyZeppelinContext' object has no attribute 'run' Thank you Jonathan Greenleaf
SSL with Elasticsearch / Shield
I have been able to start the server on 8443, but have not been able to make a connection to my Elasticsearch data node over SSL. I verified I can curl (curl --insecure -v -u user:pwd https:xx.xx.xx.xx:9200/...) the ES box with the Shield credentials. Within the interpreter I have name -> value shield.user -> user:pwd shield.transport.ssl -> true we use port 9200 and force the gets/searches to require https. and I don't know if this is even used but I included this dependency: /zeppelin/interpreter/elasticsearch/shield-2.4.4.jar based on what I read here: https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/interpreter/elasticsearch.html /zeppelin/logs/zeppelin-root-ip-10-2-3-144.log INFO [2017-01-27 20:38:44,556] ({main} AbstractConnector.java[doStart]:266) - Started ServerConnector@30aba78f{SSL-HTTP/1.1}{0.0.0.0:8443} elasticsearch log complains: [2017-01-27 21:23:18,161][WARN ][shield.transport.netty ] [esdata3] received plaintext http traffic on a https channel, closing connection [id: 0xf43a9b2f, /xx.xx.xx.xx:36188 => /xx.xx.xx.xx:9200] I built from source - 0.8.0-SNAPSHOT. I also added this to /zeppelin/elasticsearch/pom.xml org.elasticsearch.plugin shield 2.4.4 I'm confused what I need to do with Shield on the Zeppelin server. Do I need to copy a cert from my existing Shield setup on my data node? Any pointers appreciated. Thanks - Jonathan