v1.0.3

Minor API change.

The method checkTableSchemaCompatibility(String, String...) was removed. There is also the method checkTableSchemaCompatibility(String...) which was ambiguous for calls like checkTableSchemaCompatibility("schema1", "schema2"). Since the first method did just call the second, it was removed to simplify things.

v1.0.2

Added convenience methods for better usage of XMI storage tables and other quality of life methods. The data retrieval iterators are now separate classes and have been generalized to read multiple fields. Bug fixes.

v1.0.1

Important: The system has been redubbed from JeDIS to CoStoSys. JeDIS denotes a more general architecture for database supported UIMA processing that includes UIMA components (jcore-xmi-db-reader and jcore-xmi-db-writer) and annotation graph segmentation using jcore-xmi-splitter. The Corpus Storage System (CoStoSys) is the part managing the database.

In this version, primarily some documentation was added. The most important change, besides the renaming, is the new configuration.xsd XMI schema for the configuration file. Check the README for more information. Note that when using CoStoSys from the command line, the configuration file name is now sought case insensitive and may be called dbcconfiguration.xml, costosysconfiguration.xml and costosys.xml.

v1.0.0

The first release of JeDIS, a system to store large XML text corpora in a database. JeDIS offers facilities to create subsets of the main corpus data table without copying any data but just using foreign keys. The system is originally meant to work with the jcore-db-reader which uses subsets to synchronize multiple corpus readers and to track progress and errors.