>>> But not sure about how other interpreters can do the same thing. (e.g
trivial, but let’s think about shell interpreter which keeps it’s tabledata
on memory)
The approach I proposed is general for all the interpreters. What we need
do is to add one method in RemoteInterpreterProcess for other
i
Hi Park,
Thanks for the sharing, this is a very interested and innovated idea. I
have several comments and concerns.
1. What does the resource registration mean ?
IIUC, currently it means it would cache the data in Interpreter Process.
Then it might be a memory issue when more and more resourc
Thanks for the questions guys!
@Jun Kim actually that feature was originally discussed and was put into
backlog since proposal was more about tables processed by interpreters and
their sharing. However having quick visualisation on the fly for not so
large data makes sense indeed, and possibly cou
Hi guys,
this is great! I think this can also enable some drop-down feature between
tables in the UI...
Do you think this enhancements can also include the graph part?
Andrea
Il giorno lun 12 giu 2017 alle ore 05:47 Jun Kim ha
scritto:
> All of the enhancements looks great to me!
>
> And I wish
All of the enhancements looks great to me!
And I wish a feature which can upload a small CSV file (maybe about
20MB..?) and play with it directly.
It would be great if I can drag a file to Zeppelin and register it as the
table.
Thanks :)
2017년 6월 12일 (월) 오전 11:40, Park Hoon <1am...@gmail.com>님이
