[Spike]: Investigate Heavy Operations Support for Move/Copy with Job Queue Integration
Open
Nobody has claimed this yet.
Team : Scout
Type : Spike
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Purpose
Analyze requirements for move and copy operations, especially for large folder structures, and design the async processing approach using job queue system.
Goals
- Research current move/copy capabilities (if any) in existing APIs
- Evaluate (not implement) job queue integration for heavy operations
- Define a folder locking/flagging mechanism during operations
- Analyze circular reference prevention for move operations
- Design conflict resolution for copy operations when target exists
- Evaluate performance implications for large folder operations
- Design progress tracking and status reporting (it might require @zJaaal guidance)
Acceptance Criteria
- [ ] Documentation of any existing move/copy functionality
- [ ] Technical design for job queue integration
- [ ] Specification for folder status flagging during operations
- [ ] Conflict resolution strategy for copy operations
- [ ] Circular reference prevention algorithm for move operations
- [ ] Performance benchmarks for different folder sizes
- [ ] API design for async operation status tracking
- [ ] Error handling and recovery mechanisms for failed operations
- [ ] User experience flow for long-running operations
Parent Issue
Subtask of #32302
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 parent issue #32302 and document the existing move/copy capabilities in the current APIs. Define the requested job-queue design, folder status handling, conflict and circular-reference strategies, performance benchmarks, async status API, recovery, and user flow as the completed deliverables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100