You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "jorisvandenbossche (via GitHub)" <gi...@apache.org> on 2023/06/28 12:43:39 UTC

[GitHub] [arrow] jorisvandenbossche commented on pull request #36286: GH-36280: [Python][Parquet] Export C++ WriteRecordBatch in Python API

jorisvandenbossche commented on PR #36286:
URL: https://github.com/apache/arrow/pull/36286#issuecomment-1611332862

   > Should I just change it to `write_record_batch`, or adding a argument to control it to avoid breaking previous behavior? 
   
   I think we could also consider just "breaking" the current behaviour. It will still honor the max row_group_size, just no longer create one row group per batch that you are writing. 
   
   Or only do this if `row_group_size` keyword is None.
   
   What happens if you do a `write_table` after a `write_batch` if the `write_batch` didn't yet finalize the current row group?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org