search

snd297 / braintrust

Automatically exported from code.google.com/p/braintrust
0 stars 0 forks source link

MongoDB does not reject cached blocks when source files are changed #495

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Have a study uploaded and accessed in Matlab with MongoDB running
2. Change the files on AWS
3. Access the same dataset in Matlab

What is the expected output? What do you see instead?
I expect to get the updated dataset, and have the Client not return the cached 
blocks in MongoDB as they are depreciated. However, even after restarting the 
server, the client still returns the incorrect old blocks.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by JBWagenaar on 3 Sep 2014 at 2:39