There're several approaches. 1. Use shared mode across notes. So that all the note share the same interpreter 2. Use distributed resource pool via ZeppelinContext api. e.g. z.get, z.set
I plan to to write document about how to sharing data in Zeppelin, hope that would be helpful for users. Manuel Sopena Ballesteros <manuel...@garvan.org.au> 于2019年11月13日周三 下午2:02写道： > Ok, what should I do in order to be able to reuse variables across > different notes? > > > > Manuel > > > > *From:* Jeff Zhang [mailto:zjf...@gmail.com] > *Sent:* Wednesday, November 13, 2019 4:57 PM > *To:* users > *Subject:* Re: spark r interpreter resets working directory > > > > In that case, each user use different interpreter process. In your second > note, the current working directory is the yarn container location which is > expected > > > > > > Manuel Sopena Ballesteros <manuel...@garvan.org.au> 于2019年11月13日周三 下午1:50 > 写道： > > Yarn cluster using impersonate (per user + isolated) > > > > I guess that means each note use different interpreters? > > > > Manuel > > > > *From:* Jeff Zhang [mailto:zjf...@gmail.com] > *Sent:* Wednesday, November 13, 2019 2:35 PM > *To:* users > *Subject:* Re: spark r interpreter resets working directory > > > > Does your different notes share the same interpreter ? I suspect you are > using per note isolated or scoped mode. > > > > Looks like you are local or yarn-client mode for the first note, but using > yarn-cluster mode for the second note > > > > Manuel Sopena Ballesteros <manuel...@garvan.org.au> 于2019年11月13日周三 上午11:31 > 写道： > > Dear Zeppelin community, > > > > I am testing spark r interpreter and realised it does not keep the working > directory across notes. > > > > What is the reason behind this behavior? > > > > Thank you very much > > > > NOTICE > > Please consider the environment before printing this email. This message > and any attachments are intended for the addressee named and may contain > legally privileged/confidential/copyright information. If you are not the > intended recipient, you should not read, use, disclose, copy or distribute > this communication. If you have received this message in error please > notify us at once by return email and then delete both messages. We accept > no liability for the distribution of viruses or similar in electronic > communications. This notice should not be removed. > > > > > -- > > Best Regards > > Jeff Zhang > > NOTICE > > Please consider the environment before printing this email. This message > and any attachments are intended for the addressee named and may contain > legally privileged/confidential/copyright information. If you are not the > intended recipient, you should not read, use, disclose, copy or distribute > this communication. If you have received this message in error please > notify us at once by return email and then delete both messages. We accept > no liability for the distribution of viruses or similar in electronic > communications. This notice should not be removed. > > > > > -- > > Best Regards > > Jeff Zhang > NOTICE > Please consider the environment before printing this email. This message > and any attachments are intended for the addressee named and may contain > legally privileged/confidential/copyright information. If you are not the > intended recipient, you should not read, use, disclose, copy or distribute > this communication. If you have received this message in error please > notify us at once by return email and then delete both messages. We accept > no liability for the distribution of viruses or similar in electronic > communications. This notice should not be removed. > -- Best Regards Jeff Zhang
