Skip to content

Releases: JULIELab/costosys

v1.6.2

09 Mar 20:37
Compare
Choose a tag to compare
  • [enhancement] Skip PMC update files that cannot be read #18

v1.6.1

17 Nov 16:21
0919d66
Compare
Choose a tag to compare
  • [enhancement] Create a XmiColumnDataInserter #16
  • [closed] Add 'nsAware' attribute to 'tableSchema' #15
  • [closed] Allow update files to be processed again. #13
  • [closed] Make unshared connections available #10
  • [closed] Restructure Medline import/update #9
  • [enhancement] Upgrade Postgres container version to 11.12. #8

v1.6.0

28 Sep 11:29
Compare
Choose a tag to compare
  • [closed] Add a parameter for deleting rows by ID in a given table. #14
  • [enhancement] Let the database document deleter delete from multiple tables #12
  • [closed] Implement JeDIS binary format decoding for CLI queries #11
  • [closed] Add "drop table" functionality #3

v1.5.2

11 Jun 06:01
Compare
Choose a tag to compare
  • [enhancement] Delete reference to removed mirror subset #2
  • [enhancement] Mention database configuration file parameter #1

v1.4.0

v1.3.2

20 May 12:20
1d046a1
Compare
Choose a tag to compare

Setting the subset table column host_name to null when resetting the subset table.

v1.3.1

23 Apr 15:15
Compare
Choose a tag to compare

Some logging at CLI startup about the used schemas has been added.
Also, the timeout for trying to get a connection from the connection pool has been raised from 30s to 60s.

v1.3.0

28 Mar 12:53
Compare
Choose a tag to compare

This is mostly a maintenance release. The new minor revision number stems from the fact that as of this version, CoStoSys required Java11.

v1.2.4

25 Dec 10:02
Compare
Choose a tag to compare

Important bugfix release. The connection concurrency still had issues. As of this version there is no known issue.

v1.2.3

06 Dec 15:08
Compare
Choose a tag to compare

Updates of large collections now need less memory.

Until this version, each file containing documents to be updated was exhaustively read to
avoid duplicate document IDs in the same update batch which can lead
to primary key violation errors. This has now been broken down
in updating batches up to 10k documents.