Repository navigation
GH-54637: [Python] add MemoryPool support to pq.read_table - #54919
Conversation
|
|
|
My understanding before implementing/opening the PR - Function
|
|
cc @pitrou |
pitrou
left a comment
There was a problem hiding this comment.
Thanks for doing this @omkar-334 . This looks good on the principle, just a small suggestion for improving tests.
|
Thanks a lot @omkar-334 ! @AlenkaF @jorisvandenbossche Do you want to give this a final review? |
AlenkaF
left a comment
There was a problem hiding this comment.
Added one question that doesn't necessarily need a code change, but I'm curious what you think @omkar-334.
69c29d6 to
8b9af5d
Compare
|
@AlenkaF I've made the changes. The
|
AlenkaF
left a comment
There was a problem hiding this comment.
Just one comment on the read_table changes.
|
Thanks a lot @omkar-334! |

Rationale for this change
pq.read_tablehas no way to pass a memory pool.ParquetReaderandDataset.to_tablealready accept one, it just wasn't added.What changes are included in this PR?
I added a
memory_poolargument toread_table,ParquetFileandParquetDataset. It is passed toParquetReaderand toDataset.to_table, with docstrings updated.Are these changes tested?
Yes. I added new tests in
test_basic.py- It reads a Parquet file with a tracked memory pool and check that the pool was actually used. They coverread_table,ParquetFileandParquetDataset.Are there any user-facing changes?
New optional
memory_poolkeyword. No breaking changes.Was AI used for this PR?
PR code and description written by:
Reviewed before submission by:
Github Issue - #54637