Skip to content

Support Per-node DataTree chunking - #10105

Draft
sjperkins wants to merge 3 commits into
pydata:mainfrom
sjperkins:fine-grained-datatree-chunking
Draft

Support Per-node DataTree chunking#10105
sjperkins wants to merge 3 commits into
pydata:mainfrom
sjperkins:fine-grained-datatree-chunking

Conversation

@sjperkins

Copy link
Copy Markdown
Contributor
  • ClosesPer-node DataTree chunking #9634
  • Tests added
  • User visible changes (including notable bug fixes) are documented in whats-new.rst
  • New functions/methods are listed in api.rst

@welcome

welcomeBot commented Mar 7, 2025

Copy link
Copy Markdown

Thank you for opening this pull request! It may take us a few days to respond here, so thank you for being patient.
If you have questions, some answers may be found in our contributing guidelines.

@sjperkinssjperkins changed the title Initial commitSupport Per-node DataTree chunkingMar 7, 2025
@sjperkins
sjperkinsforce-pushed the fine-grained-datatree-chunking branch from 52653bd to 4d5383bCompareMarch 7, 2025 13:39
@sjperkins

Copy link
Copy Markdown
ContributorAuthor

Some initial work to support per-node DataTree chunking. It might be this easy (I'm guessing because of all the work @keewis did in #9660), but I've almost certainly missed some subtleties.

One thing that occurred to me was that it's probably worth supporting a default chunk entry, perhaps keyed with "".

I still need to get my head around the mypy errors, but i's EOW for me.

@TomNicholasTomNicholas added the topic-DataTree Related to the implementation of a DataTree class label Mar 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic-DataTreeRelated to the implementation of a DataTree class

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Per-node DataTree chunking

2 participants

@sjperkins@TomNicholas