NVIDIA-NeMo / NVIDIA-NeMo/Curator
Revisit limit behavior for FilePartitioningStage
Open
Nobody has claimed this yet.
enhancement
ray-api
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 328
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 30
Description
Is your feature request related to a problem? Please describe.
Currently in FilePartitioningStage , if we provide limit we just drop other tasks, dont think we should do that.
Contributor guide
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 with ray-curator/ray_curator/stages/file_partitioning.py, especially the limit handling around lines 96-99, and trace how FilePartitioningStage selects and discards tasks. Clarify the intended limit behavior and validate it against the stage's existing tests or execution path; done means the chosen behavior is explicit and no longer silently drops tasks unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100