Temporary data sets after ops_partition
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 77
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Can we have support for temporary ops_dat declaration after ops_partition?
This would be useful when the size of the data set is not known before hand.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing ops_partition and ops_dat entry points and how data-set sizes are currently provided. Determine the intended lifecycle for an ops_dat declaration made after partitioning, including how an unknown size is supplied. Done means the API supports this temporary-data-set use case and its behavior is covered by appropriate validation or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100