[FEAT-API]: Enable Go Consequences to read from S3
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- Go consequences can currently read from s3 but is not compatible with the paraquet files that are output by stormsim
- we need to update the Go consequences repo to integrate with stormsim and be able to read paraquet files
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 Go consequences repository and reviewing its existing S3 reader, then compare it with the Parquet files produced by Stormsim. Determine the compatibility gap and verify the reader against a Stormsim-generated Parquet file. Done means Go consequences can read those files from S3 successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100