Skip to content

ws_shard: make disable_memory_map a direct kwarg with auto-fallback o… - #71

Draft
tig888 wants to merge 1 commit into
mainfrom
tig/mmap-fix
Draft

ws_shard: make disable_memory_map a direct kwarg with auto-fallback o…#71
tig888 wants to merge 1 commit into
mainfrom
tig/mmap-fix

Conversation

@tig888

Copy link
Copy Markdown
Contributor

Move disable_memory_map from a WSDataset-level flag to a WSShard kwarg (default
False), and auto-fall back to pa.OSFile when pa.memory_map raises OSError (e.g.
on NFS / container filesystems that don't support mmap). WSDataset no longer
carries the flag — the common case is now zero-config, and direct WSShard users
no longer need a stub dataset to satisfy dataset.disable_memory_map.

@rashishhume
rashishhume marked this pull request as draft May 13, 2026 18:43
@rashishhume

Copy link
Copy Markdown
Collaborator

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tig888@rashishhume