The v3 write api supports a "no_sync" option that causes the server to return an ack for a write as soon as possible - specifically, it doesn't wait for an sync that the write is durable in the wal (fsync for disk; ack for object store).

The write command doesn't currently support this option available in the api; add it.