Add Options for resolving duplicate date-times when POSTing timeseries data
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
There is currently no way to resolve duplicate date-times in timeseries data. Current behavior is to error out with 400 error code.
See https://github.com/USACE/cwms-data-api/issues/1783
Describe the solution you'd like
Add options to specify first, last, average resolution if there are duplicate date-times present in timeseries data. Default would be to error.
Additional context
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 at the POST timeseries endpoint and trace where duplicate date-times currently produce the 400 response. Determine how first, last, and average resolution options should be exposed while retaining error as the default, then add coverage for each option and the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100