VEuPathDB / VEuPathDB/lib-compute-platform
Record index of job inputs and outputs in S3
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 3
Description
For debugging/transparency, we should write an index file to S3 for a given job's inputs and outputs.
For ease of implementation, this doesn't need to be a singular file, we could have something like inputs.json and outputs.json which contain arrays of file names.
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 locating the Kotlin job execution and S3 upload paths, then inspect how input and output file names are currently tracked. Define the contents and placement of the proposed inputs.json and outputs.json indexes, and verify that each job writes both indexes with the expected file-name arrays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kotlin
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100