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
Antoine Pitrou / @pitrou:
When memory mapping a file, it's the OS which makes decisions about whether to keep things in memory. Chances are that, if the file is kept entirely in memory, it simply means there's no other application requesting that memory.
Do you have reasons to believe something different is happening?
When converting a memory mapped arrow file into parquet file, it loads the whole table into RAM. This effectively negates the point of memory mapping.
If this is not a bug, perhaps there is a proper way of converting the memorymapped arrow file to parquet without using excessive memory?
Example code:
Reporter: Sep Dehpour
Note: This issue was originally created as ARROW-9526. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: