Skip to content
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

Communicate non-dataframe variables from livy to local #418

Open
sijunhe opened this issue Nov 10, 2017 · 5 comments
Open

Communicate non-dataframe variables from livy to local #418

sijunhe opened this issue Nov 10, 2017 · 5 comments

Comments

@sijunhe
Copy link

sijunhe commented Nov 10, 2017

I am aware of the feature that communicate the contents of a dataframe/pandas from livy to local #333 . What about the communication of other basic data structures, like scalars, lists, etc?

@aggFTW
Copy link
Contributor

aggFTW commented Nov 11, 2017

That's not supported yet, and it's not in a roadmap. Can you please tell us about what you are trying to achieve?

@sijunhe sijunhe changed the title Communicate non-dataframe variables between livy to local Communicate non-dataframe variables from livy to local Nov 12, 2017
@sijunhe
Copy link
Author

sijunhe commented Nov 12, 2017

The use case would be the same as #333, but just for normal variables on the driver. For example , I train a K means model on spark and store its cluster centers to a numpy array variable. If I need to get the variable to local, I'd need to do silly things of either converting it to a data frame and use -o or printing it out and defining the variable in local.

@aggFTW
Copy link
Contributor

aggFTW commented Nov 14, 2017

Got it. That is not in the works currently. What kind of user experience would you like to see? Would it just be a parameter sent to the %%spark api?

This would be a good community contribution.

@kuppu
Copy link

kuppu commented Dec 4, 2017

My vote for prioritizing this feature. I have had to use different workarounds to collect global variables.
This feature will also help in visualization, plots requires variables (data, legends, labels...) to be on single node.

%%collect - o <livy_variable>

@hanyucui
Copy link
Contributor

hanyucui commented Oct 8, 2020

Is this already taken care of by #432?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants