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: README.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,21 +277,6 @@ You may also define a spring bean of type `FlywayCallback` and annotate it with
277
277
interface provide several hook into the schema management lifecycle that may, for example, be used to
278
278
`SET ROLE migrator`before and `RESET ROLE` after each migration.
279
279
280
-
### Customizing event locks
281
-
282
-
* **lock-duration**: The selected events are locked before transmission. If the transmission fails the events stay locked
283
-
until the lock expires (default: 600 seconds).
284
-
285
-
* **lock-duration-buffer**: Since clocks never work exactly synchronous and sending events also takes some time, a safety
286
-
buffer is included. During the last x seconds before the expiration of the lock the events are not considered for
287
-
transmission (default: 60 seconds).
288
-
289
-
```yaml
290
-
nakadi-producer:
291
-
lock-duration: 600
292
-
lock-duration-buffer: 60
293
-
```
294
-
295
280
### Test support
296
281
297
282
This library provides a mock implementation of its Nakadi client that can be used in integration testing:
@@ -332,6 +317,21 @@ The example above uses `com.jayway.jsonpath:json-path:jar:2.2.0` to parse and te
332
317
333
318
Note that you should disable the scheduled event transmission for the test (e.g. by setting `nakadi-producer.scheduled-transmission-enabled:false`), as that might interfere with the manual transmission and the clearing in the test setup, leading to events from one test showing up in the next test, depending on timing issues.
334
319
320
+
### Customizing event locks
321
+
322
+
* **lock-duration**: The selected events are locked before transmission. If the transmission fails the events stay locked
323
+
until the lock expires. The default is currently 600 seconds but might change in future releases.
324
+
325
+
* **lock-duration-buffer**: Since clocks never work exactly synchronous and sending events also takes some time, a safety
326
+
buffer is included. During the last x seconds before the expiration of the lock the events are not considered for
327
+
transmission. The default is currently 60 seconds but might change in future releases.
328
+
329
+
```yaml
330
+
nakadi-producer:
331
+
lock-duration: 600
332
+
lock-duration-buffer: 60
333
+
```
334
+
335
335
## Contributing
336
336
337
337
We welcome contributions. Please have a look at our [contribution guidelines](CONTRIBUTING.md).
Copy file name to clipboardExpand all lines: nakadi-producer/src/test/java/org/zalando/nakadiproducer/transmission/impl/EventTransmissionServiceTest.java
0 commit comments