You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a new feature request or rather a little refactoring in the code for reader to allow users to read datasets directly as pyarrow datasets and tables.
As you can see here, we are anyways creating the pyarrow dataset and table, which is then used to convert to a pandas DF in the to_pandas method
I would like to refactor this part and expose this as separate functionalities - to_pyarrow_dataset and to_pyarrow_table.
Advantage of this refactoring is that users will then be able to efficiently get the pyarrow things directly without an additional full copy/ conversion to pandas dataframe if required. This will allow the extension of delta-sharing on other processing systems like Datafusion, Polars etc, since they all extensively rely on pyarrow datasets.
Please let me know if this issue makes sense to you, I can raise a PR quick for this in a day or so.
Note: the existing functionalities will remain unaffected by this refactoring.
The text was updated successfully, but these errors were encountered:
This is a new feature request or rather a little refactoring in the code for reader to allow users to read datasets directly as
pyarrow
datasets and tables.As you can see here, we are anyways creating the pyarrow dataset and table, which is then used to convert to a pandas DF in the
to_pandas
methodI would like to refactor this part and expose this as separate functionalities -
to_pyarrow_dataset
andto_pyarrow_table
.Advantage of this refactoring is that users will then be able to efficiently get the pyarrow things directly without an additional full copy/ conversion to pandas dataframe if required. This will allow the extension of delta-sharing on other processing systems like Datafusion, Polars etc, since they all extensively rely on pyarrow datasets.
Please let me know if this issue makes sense to you, I can raise a PR quick for this in a day or so.
Note: the existing functionalities will remain unaffected by this refactoring.
The text was updated successfully, but these errors were encountered: