Re: Multi-line scripts in spark interpreter

Jeff Zhang's comment here may be useful. Regards, Sanjay On Fri, Jul 13, 2018 at 1:01 AM, Paul Brenner wrote: > This behavior is

Re: [DISCUSS] Share Data in Zeppelin

Thanks Sanjay, I have fixed the example note. *Folks, to be noticed,* the example note is just a fake note, it won't work for now. Jongyoul Lee 于2018年7月13日周五 上午10:54写道： > BTW, we need to consider the case where the result is large in a design > time. In my experience, If we implement this

Re: [DISCUSS] Share Data in Zeppelin

BTW, we need to consider the case where the result is large in a design time. In my experience, If we implement this feature, users could use it with large data. On Fri, Jul 13, 2018 at 11:51 AM, Sanjay Dasgupta wrote: > I prefer 2.b also. Could we use (save*Result*AsTable=people) instead? > >

Re: [DISCUSS] Share Data in Zeppelin

I prefer 2.b also. Could we use (save*Result*AsTable=people) instead? There are a few typos in the example note shared: 1) The line val peopleDF = spark.read.format("zeppelin").load() should mention the table name (possibly as argument to load?) 2) The python line val peopleDF =

Re: [DISCUSS] Share Data in Zeppelin

That would be great. BTW, does ZEPL's example work for now? On Fri, Jul 13, 2018 at 11:43 AM, Jeff Zhang wrote: > > Sure, we can support plain text as well. > > Jongyoul Lee 于2018年7月13日周五 上午10:37写道： > >> Yes, it's similar to 2.b. >> >> Basically, my concern is to handle all kinds of data. But

Re: [DISCUSS] Share Data in Zeppelin

Sure, we can support plain text as well. Jongyoul Lee 于2018年7月13日周五 上午10:37写道： > Yes, it's similar to 2.b. > > Basically, my concern is to handle all kinds of data. But in your case, it > looks like focusing on table data. It's also useful but it would be better > to handle all of the data

Re: [DISCUSS] Share Data in Zeppelin

Yes, it's similar to 2.b. Basically, my concern is to handle all kinds of data. But in your case, it looks like focusing on table data. It's also useful but it would be better to handle all of the data including table or plain text as well. WDYT? About storage, we could discuss it later. On

Re: [DISCUSS] Share Data in Zeppelin

I think your use case is the same of 2.b. Personally I don't recommend to use z.get(noteId, paragraphId) to get the shared data for 2 reasons 1. noteId, paragraphId is meaningless, which is not readable 2. The note will break if we clone it as the noteId is changed. That's why I suggest to use

Re: [DISCUSS] Share Data in Zeppelin

I have a bit different idea to share data. In my case, It would be very useful to get a paragraph's result as an input of other paragraphs. e.g. -- Paragrph 1 %jdbc select * from some_table; -- Paragraph 2 %spark val rdd = z.get("noteId", "paragraphId").parse.makeRddByMyself

[DISCUSS] Share Data in Zeppelin

Hi Folks, Recently, there's several tickets [1][2][3] about sharing data in zeppelin. Zeppelin's goal is to be an unified data analyst platform which could integrate most of the big data tools and help user to switch between tools and share data between tools easily. So sharing data is a very

Re: Multi-line scripts in spark interpreter

This behavior is coming from the new spark interpreter. Jeff opened  ZEPPELIN-3587 to fix it. In the mean time you can use the old spark interpreter (set zeppelin.spark.useNew to false) to get around this. Hopefully you aren't dependent on the new spark interpreter. (

Multi-line scripts in spark interpreter

Hi, This used to work: val a = new Something() .someMethod() .someMethod2() in 0.7.3 but it doesn't in 0.8.0 ... it says the .someMethod(), etc. are an illegal start of expression. Some of these setups I have are fluently expressed but would be unmanageable in a single long line.

Export Zeppelin Notebooks in HTML Format

Hi, One feature that is currently missing from Zeppelin is the ability to export a notebook in HTML (or PDF or Tex or Txt) format. What are the options here (if any) and what are the workarounds? How do other people here present their work on their manager who don't run Zeppelin herself/himself?