Releases: application-research/delta-dm
Releases · application-research/delta-dm
v1.4.0
What's Changed
- Refactor: dataset - use id on all endpoints and cli by @jcace in #65
- feat.replications schema updates by @jcace in #71
- feat.replicationProfile (#58)
- fix: ambiguous dataset id selector by @jcace in #73
- fix: explicity specify gorm Scan struct by @jcace in #74
Note: Breaking Changes
- The concept of SP <> Dataset assignment has been moved to Replication Profiles. This profile also contains the flags
Unsealed
andIndexed
, which have been removed from the Datasets schema. - Please create new Replication Profiles for each Dataset<>SP mapping - the existing associations will no longer be valid.
Note: MANUAL Migration Required
This release introduces schema changes that cannot automatically be migrated.
If this is a brand-new set up of DDM, no intervention is necessary.
If upgrading from V1.3.0 or earlier with an existing database, you must follow the steps outlined in the migration guide to ensure database consistency.
Full Changelog: v1.3.0...v1.4.0
v1.3.0
What's Changed
- feat: wallet/dataset many-to-many by @jcace in #56
- feat: secure api key by @jcace in #57
- feat: allow custom port, change default by @jcace in #60
- feat: add totalCount to replications GET api by @jcace in #53
- fix: guard against reconciliations job encountering empty arrays by @jcace in #49
- fix: fix incorrect removeUnsealedCopy param
- fix: properly support postgres db
- docs: add hero image and update readmes
Full Changelog: v1.2.0...v1.3.0
v1.2.0
What's Changed
- feat: json response for self-service api (required for delta-importer v1.0.0)
- feat: add countTotal to datasets response
- feat: add count_replicated to datasets response
- fix: replications - empty dataset bug
- feat: sp-allowed-dataset by @jcace in #40
- fix: update json of delta deal response to match by @jcace in #41
- feat: contents API by @jcace in #42
- feat: allow specifying delay start in replications body by @jcace in #43
Full Changelog: v1.1.0...v1.2.0