No. The code in `LocalDurabilityFilter` is intended to be completely non-blocking, so as not to impede ingest and allow for local durability to be achieved concurrently while the request is being processed. Here is the process.

1. request comes in.
1. LocalDurabilityFilter captures raw bytes, since them to some asynchronous system to make the request durable.
1. Dropwizard ingest resources gets the request, including the commitReceipt.
1. Dropwizard ingest processes the request. In the future, the cassandra write can be asynchronous.
1. When Dropwizard ingest is finished, it uses the commitReceipt to verify that the request has been made durable. If it has, it returns; if not, it blocks.

It's not a hack at all. It may look that way now because it's just stubbed in. My next hack day project is to figure out how to run an embedded Kafka in the ingest VM. Then magic.