Conversation
datahub-platform#125 (errors/14-unusable-values-are-422) answers a bad timestamp on the REST API with 422 invalid-timestamp (was 400 unreadable-request-body, a 400 with fields, or a 500) and an unparseable datapoint value with 422 invalid-datapoint (was 500). Fixes the 400 claims in client#timestamps and events Create, and lists both types for POST /timeseries/data and in the retry table. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: jgjesdal <jostein@intellistream.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed on the platform
IntelliStream-DataHub/datahub-platform#125 (
errors/14-unusable-values-are-422) gives two kinds of unusable value one answer each:422oftype: ".../errors/invalid-timestamp",retry: change-request, wherever it was sent. It used to be a400unreadable-request-bodywithpointer,lineandcolumn(JSON fields such aseventTimeand filter bounds), a400withfields(datapoint delete window) or a500(datapointtimestampon insert). The acceptance rules are unchanged.POST /timeseries/datais a422oftype: ".../errors/invalid-datapoint". It used to be a500.What this PR changes
reference/client.md§Timestamps: the400claims and the "same problem document as an unknown field" paragraph are replaced by the422and a table of how each place locates the offender (pointerwith noline/column, orfields). Scoped to the REST endpoints it applies to; the/analysiswindow, MCP parameters and file metadata headers are not claimed. The retry table gains a row for both422types.reference/events.md§Create: epoch seconds is refused with a422, not a400.reference/timeseries.md§Write datapoints: a short table of whatPOST /timeseries/datarefuses (400malformed body,422 invalid-timestamp,422 invalid-datapoint). Thebigintnote under Value types links to it.Merge after IntelliStream-DataHub/datahub-platform#125 ships; until then these pages would describe answers the API does not send yet.
🤖 Generated with Claude Code