-
Notifications
You must be signed in to change notification settings - Fork 448
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
Comments
That's not supported yet, and it's not in a roadmap. Can you please tell us about what you are trying to achieve? |
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 |
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 This would be a good community contribution. |
My vote for prioritizing this feature. I have had to use different workarounds to collect global variables. %%collect - o <livy_variable> |
Is this already taken care of by #432? |
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?
The text was updated successfully, but these errors were encountered: