Forward port 5 4 2 (#2781)
* Add new version to enum * Add backport tags, new VersionEnum, and new release folder for 5.4.2
This commit is contained in:
parent
d762a07817
commit
3e7bc2a81e
|
@ -73,6 +73,7 @@ public enum VersionEnum {
|
|||
V5_3_3,
|
||||
V5_4_0,
|
||||
V5_4_1,
|
||||
V5_4_2,
|
||||
V5_5_0,
|
||||
;
|
||||
|
||||
|
|
|
@ -0,0 +1,3 @@
|
|||
---
|
||||
release-date: "2021-07-06"
|
||||
codename: "Pangolin"
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: change
|
||||
backport: 5.4.2
|
||||
issue: 2732
|
||||
title: "The ConceptMap.group.element.display storage size limit has been increased to 500 characters."
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2739
|
||||
backport: 5.4.2
|
||||
title: "Too many MDM candidates matching could result in an OutOfMemoryError. Candidate matching is now limited to the
|
||||
value of IMdmSettings.getCandidateSearchLimit(), default 10000."
|
||||
|
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2747
|
||||
backport: 5.4.2
|
||||
title: "Added null checks to MDM resource interceptor in order to avoid NPEs."
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2748
|
||||
backport: 5.4.2
|
||||
title: "A new tag storage mode called **Inline Tag Mode** tas been added. In this mode, all tags are stored directly
|
||||
in the serialized resource body in the database, instead of using dedicated tables. This has significant performance
|
||||
advantages when storing resources with many distinct tags (i.e. many tags that are unique to each resource, as opposed
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2748
|
||||
backport: 5.4.2
|
||||
title: "The SQL generated for the `_profile` search parameter did not use all of the columns on the tag index table,
|
||||
resulting on poor performance on MySQL. This has been corrected."
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: change
|
||||
issue: 2760
|
||||
backport: 5.4.2
|
||||
title: "If two authorization compartments apply to the same targets and share the same compartment name,
|
||||
then instead of creating a new compartment, the rule builder now adds the new owner to the list of owners in the
|
||||
existing compartment."
|
||||
|
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2762
|
||||
backport: 5.4.2
|
||||
title: "A regression was introduced in 2760 where a READ compartment could get collapsed into a WRITE compartment. This has been corrected."
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2764
|
||||
backport: 5.4.2
|
||||
title: "Searches for mdm-expanded references such as Observation?subject:mdm=123 were getting denied by access rules
|
||||
that did not recognize the :mdm suffix. This has been corrected."
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: change
|
||||
issue: 2773
|
||||
backport: 5.4.2
|
||||
title: "Flyway migration used to enforce order by default. This has been changed so now the default behaviour is
|
||||
out of order migrations are permitted. Strict order can be enforced via the new strict-order flag if required."
|
||||
|
|
Loading…
Reference in New Issue