Thanks!
I did try 1.3.174 the other day and noticed it fixed my issues!
Brian
On Tue, Oct 29, 2013 at 12:51 AM, Thomas Mueller
thomas.tom.muel...@gmail.com wrote:
Hi,
By the way, those bugs have been fixed now. There is now a WriteBuffer
that auto-increases capacity (similar to a
().
writeBufferSize(25).
writeDelay(-1).
fileName(fileName).
cacheSize(100).
open();
Regards,
Thomas
On Thu, Oct 10, 2013 at 3:16 AM, Brian Bray brian...@gmail.comjavascript:
wrote:
I was able to boil my stuff down quite a bit by focusing
to that will also remove all data.
Regards,
Thomas
Hi,
Yes, this is a bug, I will fix it. Thanks for reporting it!
Regards,
Thomas
On Thu, Oct 3, 2013 at 1:31 AM, Brian Bray brian...@gmail.comjavascript:
wrote:
This test throws a Map is closed exception (in 1.3.173) and I don't
believe
Thomas,
Here is a more elusive issue that I'm wondering if its a bug in
MVMap/MVStore.
I'm currently using MVStore as a large, temporary disk cache, I have a java
program that scans about 10GB of raw CSV-ish files, and for each file,
plucks out a few fields I care about and stores it in a
,
Thomas
On Wed, Oct 9, 2013 at 7:52 PM, Brian Bray brian...@gmail.comjavascript:
wrote:
Thomas,
Here is a more elusive issue that I'm wondering if its a bug in
MVMap/MVStore.
I'm currently using MVStore as a large, temporary disk cache, I have a
java program that scans about 10GB
This test throws a Map is closed exception (in 1.3.173) and I don't
believe it should. Looks like MVMap.openMap(...) is not checking for
!old.isClosed()?
@Test
public void testMVMapClearReOpen() {
// open MVMap
File f = new File(System.getProperty(java.io.tmpdir), cache.data);
