Skip to content

Conversation

@jorisvandenbossche
Copy link
Member

@jorisvandenbossche jorisvandenbossche commented Jun 17, 2021

The idea is that before fully deprecating/removing the legacy implementation of ParquetDataset, we can already deprecate its custom attributes (which is AFAIK the main/only reason to still use the legacy version).

@github-actions
Copy link

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 from me. Feel free to merge if done.

@kszucs
Copy link
Member

kszucs commented Jun 29, 2021

@jorisvandenbossche is there still work to do here?

@jorisvandenbossche jorisvandenbossche force-pushed the ARROW-13074-parquetdataset-deprecate-properties branch from 781ece3 to 88e7ba4 Compare July 5, 2021 09:29
@jorisvandenbossche
Copy link
Member Author

I also deprecated the manual construction of ParquetDatasetPiece (which seemed to happen in downstream code such as dask, ray or petastorm)

@lidavidm lidavidm closed this in b8bcf76 Jul 15, 2021
@jorisvandenbossche jorisvandenbossche deleted the ARROW-13074-parquetdataset-deprecate-properties branch July 16, 2021 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants