Currently the driver does not support exhaust queries since many of the benefits of exhaust are already available to users just by the nature of the driver being asynchronous (e.g., we can avoid client stalls by just using an appropriate batch size).
To be complete we should add support for exhaust queries. This means that the driver will need to detect that a reply applies to the "previous" callback.
Currently the driver does not support exhaust queries since many of the benefits of exhaust are already available to users just by the nature of the driver being asynchronous (e.g., we can avoid client stalls by just using an appropriate batch size).
To be complete we should add support for exhaust queries. This means that the driver will need to detect that a reply applies to the "previous" callback.