-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add doc for exchanging data frames #1677
Conversation
ZeppelinContext can be used to exchange DataFrames but there are some nasty tricks and typecasts. It's good to provide some examples.
@m30m Awesome! LGTM and merge to master if there're no more comments. |
Should we do it implicitly for user in
|
It's not possible to put the DataFrame directly because of this error:
|
I mean we can internally do this in
|
Yes, that's a good idea. Shall I add a commit to this branch? |
Yes, and you also need to update method
|
Let's keep this as documentation only and let's open a JIRA (another PR) for the DataFrame support? |
If we want to support the feature I mentioned I above in another PR, then the document here is useless because we have to update the doc later. So it would be better to do it in this PR IMHO. |
well, it's a lot quicker to get doc-only PR in :) |
I'm not sure whether it's a good idea to hide this complexity in a special way and I should check whether these changes are backward compatible. So I guess a doc-only PR, with a JIRA issue afterwards to handle some spark special types is a better solution. |
Merge to master if there're no further discussions |
What is this PR for?
ZeppelinContext can be used to exchange DataFrames but there are some nasty tricks and typecasts.
It's good to provide some examples.
What type of PR is it?
Documentation
Questions: