No limit on /v1/reading #2560
Labels
bug
Something isn't working
Comments
This was referenced Jun 17, 2020
|
Closing this issue as it is being resolved in V2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐞 Bug Report
Affected Services
Several of the reading related API calls support a limit argument but /v1/reading does not.
Why not? A long running EdgeX instance which has not processed it's readings will run into an issue of Error: 500 - limit 53470 exceeds configured max. We should provide a limit argument and a complementary method that allows us to purge all readings.
Is this a regression?
Yes, the previous version in which this bug was not present was: ....Description and Minimal Reproduction
🔥 Exception or Error
🌍 Your Environment
Deployment Environment:
EdgeX Version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: