Create a separate job obj table
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
At the moment, our exporter uses ar-table. Every time it updates the status of the exporter, it spams the table. We should probably create a separate table for that.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the exporter code and the path that updates status in ar-table. Determine the separate job-object table's required schema and update behavior, then verify that exporter status updates no longer spam ar-table and that the new table is used consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, nodejs
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100