You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Levon Karayan (JIRA)" <ji...@apache.org> on 2017/02/16 01:45:41 UTC

[jira] [Created] (ZEPPELIN-2121) Support [CT]SV import directly

Levon Karayan created ZEPPELIN-2121:
---------------------------------------

             Summary: Support [CT]SV import directly
                 Key: ZEPPELIN-2121
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2121
             Project: Zeppelin
          Issue Type: Wish
          Components: GUI
            Reporter: Levon Karayan
            Priority: Minor


Thanks for the great tool!

It would be great to have Zeppelin be able to import [TC]SVs, JSON, etc.. into a notebook without having to leverage the underlying interpreter.   We run Zeppelin in the cloud for our users, and for them to use the underlying interpreter we have to have them upload the data into a private S3 bucket that we've exposed via policy files first.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [jira] [Created] (ZEPPELIN-2121) Support [CT]SV import directly

Posted by Windy Qin <wi...@163.com>.
I think importing files is the ETL's task and the Zeppelin is a Data Visualization .

On 2017-02-16 09:45 (+0800), "Levon Karayan (JIRA)" <ji...@apache.org> wrote: 
> Levon Karayan created ZEPPELIN-2121:
> ---------------------------------------
> 
>              Summary: Support [CT]SV import directly
>                  Key: ZEPPELIN-2121
>                  URL: https://issues.apache.org/jira/browse/ZEPPELIN-2121
>              Project: Zeppelin
>           Issue Type: Wish
>           Components: GUI
>             Reporter: Levon Karayan
>             Priority: Minor
> 
> 
> Thanks for the great tool!
> 
> It would be great to have Zeppelin be able to import [TC]SVs, JSON, etc.. into a notebook without having to leverage the underlying interpreter.   We run Zeppelin in the cloud for our users, and for them to use the underlying interpreter we have to have them upload the data into a private S3 bucket that we've exposed via policy files first.
> 
> 
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
>