How to Convert modin.pandas.DataFrame to pandas.DataFrame

[yuanjie-ai]

How to Convert modin.pandas.DataFrame to pandas.DataFrame

[eavidan]

This is not part of the API as pandas.DataFrame, naturally, does not posses such a method.
You can use the private method DataFrame._to_pandas() to do this conversion.
If you would like to do this through the official API you can always save the Modin DataFrame to storage (csv, hdf, sql, ect) and then read it back using Pandas. This will probably be the safer way when working big DataFrames, to avoid out of memory issues.

[yuanjie-ai]

Thanks!

how about reading a data frame into a modin data frame ?

[devin-petersohn]

@Vaderv if you have a pandas.DataFrame object, you can call Modin DataFrame constructor and it will be handled for you:

import pandas
import modin.pandas as pd

# have a pandas.DataFrame object called `pandas_df`
modin_df = pd.DataFrame(pandas_df)

It is as easy as that 😄. It is important to note that this will cause some data distribution.

[devin-petersohn]

@bdklahn Please review our code of conduct and make sure any future messages follow it: https://github.com/modin-project/modin/blob/master/CODE_OF_CONDUCT.md. Comments should be respectful and constructive.

The comment by @eavidan above answers the question. If you follow the entire thread, my comment is answering a follow-up question.

If you are running into an issue, please open a new issue. It more helpful to others looking for answers to questions to create another issue. apply is implemented, so please open a new issue if you have run into some problem. We also accept external contributions, and I'm happy to point you to the code where you can contribute a fix.

[bdklahn]

@devin-petersohn , Sorry about that. I edited my comments accordingly.
I agree with the practice of opening a new issue, and I probably should have done that. Sorry about that, too. I also should have more carefully read the comment by @Vaderv, to note it should be a treated as separate issue.
It's probably best not to actively encourage that by answering questions about an unrelated issue, in this issue's thread. It can be confusing for people, and make it hard to track/document everything which needs to be addressed relative to a repo/issue.
It might have been best, for everyone involved, to preface your answer with something like . . . "That's a different question, and might be best addressed as a separate GitHub issue, but . . ."
Here's to hoping you will be "Gracefully accepting constructive criticism". :-)
https://github.com/modin-project/modin/blob/master/CODE_OF_CONDUCT.md