|
|
|
Version 1.0.1 (Build 1.0.52)
The outstanding bugs in this release are as follows:
- Parsing approximately 3,500,000 triples causes an OutOfMemory exception. SF Bug 877346.
- Support for SolarisTM 64-bit currently fails when in 64 bit mode. SF bug 887350.
- On systems running a Windows® operating system, the use of the mapped I/O can cause certain operations (such as truncate) to fail. If any MappedByteBuffers (including DirectByteBuffers) are still mapped when a truncate is called (or other operation on a mapped file) it can fail. This does not cause data corruption or loss it merely leaves the files with unused space. On re-initialization of the database these files are truncated before being mapped, so this will always succeed. SF bug 877351.
- FileTuples are not currently closed correctly under some circumstances. A non-fatal (no data lost) error. SF bug 877352. This has been reduced in the current version.
- Locking of the database files has been removed. Users should not try and run two instances of the same database at the same time. SF bug 89651.
- The current implementation of the Jena API in Kowari is incomplete. SF feature 877348. An incomplete version of the Graph has been introduced.
- Kowari's low-level file operations have been observed to fail under NFS, with the message "No more locks". It's strongly suggested that the database be run from a local file system. This may have changed with the removal of locking (see SF bug 89651) but is currently unverified.
- Under OS X you should kill the Kowari process rather than hitting Ctrl-C as it causes the operating system to become unstable. This may be related to mapped I/O problems. Again, this does not lead to corruption of the database.
Latest News
Kowari 1.1.0 Pre-release 2 Released
Kowari 1.1.0 Pre-release 1 Released
© 2001-2004 Tucana Technologies, Inc. Some rights reserved.