What happens when... for JSON Batch Format.
See original GitHub issueI have few implementation questions around json batch format.
- Is it expected that the receiver is delivered the array? Or can an implementation not expose batching and deliver the events one at a time?
- What happens when that receiver has an issue with one of n of these events? The response code should be?
- If a valid response is
[]
, is that also a valid request? IE, should an SDK prevent you from sending[]
?
Issue Analytics
- State:
- Created 4 years ago
- Comments:24 (18 by maintainers)
Top Results From Across the Web
Json batch format in ODataLib - OData | Microsoft Learn
A JSON batch request has only one top level property named requests , whose value is an array containing multiple requests and multiple...
Read more >JSON batch format - Sumo Logic Support
I'm trying to post some batches of data to an HTTP source. If I send a single JSON line, everything works fine in...
Read more >Windows Batch - Pretty Print JSON per Script - Stack Overflow
The JSON files all aren't formatted properly, meaning there are no tab-spaces at the beginning of lines.
Read more >Batch Job Result In Json format for both Success and Error ...
I want the BatchJob result in json format. I know i can get the result like below for number of records pass or...
Read more >JSON is the New CSV and Streams are the New Batch
One of the big shifts in application design over the past ten years was a move to REST APIs with payloads formatted in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@n3wscott We do all or nothing.
The group has discussed this a lot and the end result is to leave processing model out of the CloudEvents spec. We can revisit how to process Batch in the processing model if we get to defining it.
Closing this.