All notable changes to ds-storage will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Bumped SwaggerUI dependency to v5.18.2
- Property for database connection pool size. Under 'db' property new property: 'connectionPoolSize'. Reasonable values are from 10 to 100.
- Fixed inclusion of the same dependencies from multiple sources.
2.3.2 2025-01-07
- Upgraded dependency cxf-rt-transports-http to v.3.6.4 (fix memory leak)
- make all loggers static
- changed UPDATE_STRATEGY to NONE for ds.tv and ds.radio recordBase (origin)
- Changed connection pool size from 10 to 100
- Enabled OAuth2 on /select (solrSearch) endpoint. Much is copy-paste from ds-image to see it working in two different modules. Plans are to refactor common functionality out into kb-util/template projects.
- Removed non-resolvable git.tag from build.properties
- Removed double logging of part of the URL by bumping kb util to v1.5.10
2.1.1 2024-07-16
- Added updateReferenceIdForReocrd method. The method is also added to the client.
2.1.0 2024-07-16
- Refactored endpoint record/referenceId to records/minimal
- Updated client with a ContinuationStream method calling the endpoint records/minimal
- Deprecated the client method getDsRecordsReferenceIdModifiedAfter
2.0.0 2024-07-01
- Bumped version to fix x.y.z release format
1.22 2024-06-24
- Added createMapping method (referenceid <-> kalturaId) to client.
- Bumped kb-util version to improve YAML logging.
1.21 2024-06-20
- Added new API method (/record/referenceids) to extract records with a minimum of fields. Is used to enrich kalturaid data from referenceId
1.19 2024-05-10
- Support for dynamically updating values in OpenAPI spec. DRA-139.
- Change configuration style to camelCase DRA-431
- Changed Nexus used for deployment
- Added sample config files and documentation to distribution tar archive. DRA-417
- new table Mappings with fields (referenceId,kalturaId) and methods to create/update/read entries
- new service method that will enrich records in the records table with kalturaid from the mapping table
- New service method (record/updateKalturaId) to update the kalturaId for a record. Both create new record and update record will set the kalturareferenceid. DRA-314
- new service method (records/updateKalturaId) that updates kalturaId for all records that have referenceId and no Kaltura, given the mapping reference<-> KalturaId is found in mapping table.
- Added two new fields to record: kalturareferenceid and kalturainternalid. The kaltura internal id is required by the frontend for thumbnails and streaming. DRA-314
- Added profiles to POM
- Switch from Jersey to Apache URI Builder to handle parameters containing '{' DRA-338
- Correct resolving of maven build time in project properties. DRA-417
- Wrongly defined URIs in the client.
1.18 2024-03-08
- openAPI endpoints for record/records refatored and changed. This is not backwards compatible.
1.16 2024-03-05
- Changed how the paging-Record-Count is calculated. A simple database lookup is now performed instead of creating an intermediary stream.
- Changed the origin used for StorageClient tests as 'ds.radiotv' is removed in the near future.
- Integration test uses aegis configuration.
- bump sbforge-parent to v25
- Removed origin enums from openAPI specification
1.15 2024-02-06
- Added git information to the status endpoint. It now delivers, deployed branch name, commit hash, time of latest commit and closest tag
- Added the Paging-Record-Count header to responses from all endpoints that deliver multiple records.
1.14 2024-01-22
- logback template changes
1.12 2023-12-05
- General style of YAML configuration files, by removing the first level of indentation.
- Updated OpenAPI YAML with new example values
- Multiple method names was changed in DsStorageClient to align naming with ds-client
- Some helper classes for continuation streams was moved to kb-util. No change to behaviour
- DsStorageClient has new method to stream records with no limit of number of records.
- new API method to delete records by origin within a time interval. The purpose is to clean up old records after af full ingest.
- Record object has new attribute:recordType. allowed recordTypes are defined in the YAML config
- New method to retrieve all records from an origin and recordtype. The records will contain the local tree.
- Client for ds-storage
- refactoring
- method to get record with local tree as object, immedient parent and children only.
- API service methods renamed (url's).
-
ID normalisation: If a record contains a invalid character after the recordbase part, it will be normalised and the invalid characters will be replaced. The original (invalid) id will be stored in the 'orgid' field and flagged for invalid id. Having the original id will make it possible to track it back to the collection it came from. The record can still be retrieved and updated using the invalid id, but also by the normalised id. Regexp for recordbase: ([a-z0-9.]+)
Regexp for id: ([a-z0-9.]+):([a-zA-Z0-9:._-]+) -
Jetty port set explicitly to 9072 instead of default 8080 to avoid collisions with projects using default tomcat/jetty setup.
- Test release, nothing new
- Initial release of ds-storage