Is this the only known issue with Windows/64bit ? So this means that you cannot completely release a particular dataset from the in-memory cache and continue to run the JVM, which you may want to do if you have a set of separate datasets and you would want to dynamically open and close them in a running process? This could be a reason to decide that Windows/64bit is not an appropriate platform on which to run TDB if you have such a situation. I'd like to get this clarified.
-----Original Message----- From: Andy Seaborne [mailto:[email protected]] Sent: Thursday, August 08, 2013 5:36 PM To: [email protected] Subject: Re: Dataset cannot be deleted completely during run time. TDBFactory.release(location) ; This does not work on Windows/64bit. Andy On 08/08/13 17:46, Kurt Landen wrote: > "Deleting files behind TDB's back can only be done with great care. > You must use StoredConnection.release() to expel it from the in-JVM > cache. Then delete the files, then reopen it the database. > > Otherwise, the caches are still there and some of your data is still > around. Eventually something will go wrong. Such data is not persistent. > > This does not work on Windows/64bit. This is a well-documented issue > on MS Windows with memory mapped files." - Andy Seaborne > > > On Thu, Aug 8, 2013 at 11:41 AM, Site Guo <[email protected]> wrote: > >> Hi, GuysI deleted a dataset by using FileUtils.deleteDirectory to >> delete the directory which holds the dataset. The directory got >> deleted and the dataset did not exist. There was no problem. However, >> the problem arises when the program keeps running and creates another >> dataset with the same name (namely, creates the same directory). All >> the models and the inside triplets still exist in the dataset. >> Although, I've checked that the directory did get deleted during the running >> time. >> Please shed some light here. Which Jena API Method can we use to >> completely delete a dataset? >> Thanks,Victor >
