You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: documentation/src/main/resources/jsonschema/protocol-streaming-subscription-subscribe-for-persisted-events-payload.json
+4
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,10 @@
21
21
"type": "string",
22
22
"format": "date-time",
23
23
"description": "The timestamp to stop the streaming at."
24
+
},
25
+
"filter": {
26
+
"type": "string",
27
+
"description": "An RQL expression defining which events to filter for in the stream. Only supported for thing events."
### Streaming historical events via Ditto Protocol
142
163
143
164
Please inspect the [protocol specification of DittoProtocol messages for streaming persisted events](protocol-specification-streaming-subscription.html)
@@ -219,6 +240,24 @@ It will do so either until all existing events were sent, in that case a `comple
219
240
Or it will stop after the `demand` was fulfilled, waiting for the requester to claim more demand with a new `request`
220
241
message.
221
242
243
+
#### Filtering streamed historical events for things via Ditto Protocol
244
+
245
+
The `filter` for streaming historical thing events may also be specified via Ditto Protocol.
246
+
247
+
Example protocol message for subscribing for the persisted events of a thing with a `filter`:
0 commit comments