Prepare changelog for 5.4.1 release
This commit is contained in:
jamesagnew
parent
474cca877a
commit
48eea5a7cc
|
|
@ -72,6 +72,7 @@ public enum VersionEnum {
|
|||
V5_3_2,
|
||||
V5_3_3,
|
||||
V5_4_0,
|
||||
V5_4_1,
|
||||
V5_5_0,
|
||||
;
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,3 @@
|
|||
---
|
||||
release-date: "2021-06-15"
|
||||
codename: "Pangolin"
|
||||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2509
|
||||
backport: 5.4.1
|
||||
title: "Pagination returned incorrect offset and count in the previous link of the last page
|
||||
when total element count was one more than multiple of page size. Problem is now fixed"
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2652
|
||||
backport: 5.4.1
|
||||
title: "Settings have been added to the JPA Server DaoConfig to enable/disable various individual kinds of scheduled tasks."
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: change
|
||||
issue: 2653
|
||||
backport: 5.4.1
|
||||
title: "When performing a conditional create/update/delete on a JPA server, if the match URL
|
||||
contained a plus character, this character was interpreted as a space (per legacy URL encoding
|
||||
rules) even though this has proven to not be the intended behaviour in real life applications.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2653
|
||||
backport: 5.4.1
|
||||
title: "When performing a conditional create operation on a JPA server, the system will now
|
||||
verify that the conditional URL actually matches the data supplied in the resource body,
|
||||
and aborts the conditional create if it does not."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2665
|
||||
backport: 5.4.1
|
||||
title: When performing a FHIR transaction containing a conditional create, references to that resource
|
||||
were inadvertently replaced with contained references."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2672
|
||||
backport: 5.4.1
|
||||
title: "A concurrency error was fixed when using client assigned IDs on a highly concurrent server
|
||||
with resource deletion disabled."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2672
|
||||
backport: 5.4.1
|
||||
title: "Support has been added to the JPA server for `_include` and `_revinclude` where the
|
||||
value is a qualified star, e.g. `_include=Observation:*`."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2674
|
||||
backport: 5.4.1
|
||||
title: "A null-pointer exception was fixed when a ResponseTerminologyDisplayInterceptor is registered and a search
|
||||
or read response returns a resource with code value that in turn returns a null code lookup."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2675
|
||||
backport: 5.4.1
|
||||
title: "A new interceptor ValidationMessageSuppressingInterceptor has been added. This interceptor can be used
|
||||
to selectively suppress specific vaLidation messages."
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2676
|
||||
backport: 5.4.1
|
||||
title: "A new config option has been added to the DaoConfig that causes generated SQL statements to
|
||||
account for potential null values in HAPI FHIR JPA date index rows. Nulls are no longer ever
|
||||
used in this table after HAPI FHIR 5.3.0, but legacy data may still have nulls."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2676
|
||||
backport: 5.4.1
|
||||
title: "A new setting has been added to the DaoConfig that allows the maximum number of
|
||||
`_include` and `_revinclude` resources to be added to a single search page result."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2676
|
||||
backport: 5.4.1
|
||||
title: "When performing non-query cache JPA searches (i.e. searches with `Cache-Control: no-store`)
|
||||
the loading of `_include` and `_revinclude` will now factor the maximum include count."
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2676
|
||||
backport: 5.4.1
|
||||
title: "Subscription notifications will no longer be triggered by default in response to changes
|
||||
that do not increment the resource version (e.g. `$meta-add` and `$meta-delete`). A new
|
||||
DaoConfig setting has been added to make this configurable."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2674
|
||||
backport: 5.4.1
|
||||
title: "When myDaoConfig.setDefaultTotalMode(SearchTotalModeEnum.ACCURATE) and there are zero search results on an _id search,
|
||||
An Index Out of Bounds error was thrown. This has been corrected."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2681
|
||||
backport: 5.4.1
|
||||
title: "A new DaoConfig setting called Mass Ingestion Mode has been added. This mode enables rapid
|
||||
data ingestion by skipping a number of unnecessary checks during backloading."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2682
|
||||
backport: 5.4.1
|
||||
title: "Fixes the problem that FHIR package IDs were incorrectly treated as case sensitive when being loaded, causing loads to fail when dependencies were declared with a different case than in the package itself."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: perf
|
||||
issue: 2688
|
||||
backport: 5.4.1
|
||||
title: "FHIR Transaction duplicate record checks are now performed without any database interactions or SQL statements,
|
||||
reducing the processing load associated with FHIR transactions by at least a small amount."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: perf
|
||||
issue: 2688
|
||||
backport: 5.4.1
|
||||
title: "Conditional URL lookups in the JPA server will now explicitly specify a maximum fetch size of 2, avoiding
|
||||
fetching more data that won't be used inadvertently in some situations."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2692
|
||||
backport: 5.4.1
|
||||
title: "A new Pointcut has been added that is invoked when a new Bulk Export is initiated."
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2693
|
||||
backport: 5.4.1
|
||||
title: "Constraint errors were not always auto-retried even when configured to do so on certain
|
||||
platforms (particularly Postgresql) where constraint names are auto converted to lower case.
|
||||
Thanks to Bruno Hedman for the pull request!"
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: change
|
||||
issue: 2695
|
||||
backport: 5.4.1
|
||||
title: "Bulk import batch jobs are now activated in a local scheduled task, making bulk import
|
||||
jobs better able to take advantage of large clusters."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2702
|
||||
backport: 5.4.1
|
||||
title: "The JPA server terminology uploader now supports uploading ICD-10-CM (US Edition) using the
|
||||
native format for that vocabulary."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2705
|
||||
backport: 5.4.1
|
||||
title: "When searching by source, if deleted resources are matched, the search returned an incorrect size. This has been corrected."
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
type: fix
|
||||
issue: 2695
|
||||
backport: 5.4.1
|
||||
title: "The _filter search parameter was incorrectly included in the server capability statement if it was disabled
|
||||
on the server. This has been corrected."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
type: add
|
||||
issue: 2712
|
||||
backport: 5.4.1
|
||||
title: "AuthorizationInterceptor can now be used to authorize bulk export requests"
|
||||
|
|
|
|||
Loading…
Reference in New Issue