Expose MappedByteBuffer#force()

[tomfitzhenry]

Good day MrWilson,

For applications that aspire to be less... dirty, it'd be useful to be able to msync, via MappedByteBuffer#force(). Is this reasonable or outside the scope of java-dirty?

Regards,
tom

[mrwilson]

Hi Tom,

Under the hood, java-dirty uses multiple MappedByteBuffers as partitions.

It feels like the safest way to implement Store#force() would be to lock the store against writes (but not reads), then force all of them - something along the lines of below.

public void force() {
  lock.acquire();
  partitions.forEach(MappedByteBuffer::force);
  lock.release();
}

[tomfitzhenry]

Ah, I hadn't noticed partitions. That seems a reasonable safe way to do it, though I no longer have this requirement as I'm no longer looking at java-dirty. I'm looking at other DBs due to additional requirements (persisted indexes).