THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The sink needs a way to build back pressure, eg, if the throughput limit of the destination is exceeded. Initially we were planning to adopt the isAvailable pattern from the source interface. But the benefits are too vague at this point and it would require substantial changes to the sink API, we'll start with a blocking implementation of the write function and see how far we get.
| Code Block | ||||
|---|---|---|---|---|
| ||||
/**
* Signals if enough RequestEntryTs have been buffered according to the user
* specified buffering hints to make a request against the destination. This
* functionality will be added to the sink interface by means of an
* additional FLIP.
*
* @return a future that will be completed once a request against the
* destination can be made
*/
public CompletableFuture<Void> isAvailable() {
...
}
|
...