see that the transmit of table data is sufficient.
Regards,
Maxim Belousov
От: Jeff Zhang
Отправлено: 13 июля 2018 г. 6:00
Кому: users@zeppelin.apache.org
Копия: dev
Тема: Re: [DISCUSS] Share Data in Zeppelin
Thanks Sanjay, I have fixed the example note
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 feat
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?
>
> T
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 = z.getTable("peopl
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 i
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 includ
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 Fri,
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 pa
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
spark.read(table).
