honeymoose
/
hapi-fhir
mirror of https://github.com/hapifhir/hapi-fhir.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added changelog entries.

This commit is contained in:
Diederik Muylwyk 2019-09-26 11:36:55 -04:00
parent a4f9894104
commit efae77a330
2 changed files with 38 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term/BaseHapiTerminologySvcImpl.java
View File

@ -1000,6 +1000,7 @@ public abstract class BaseHapiTerminologySvcImpl implements IHapiTerminologySvc,
private void addLoincFilterAncestorIn(String theSystem, QueryBuilder theQb, BooleanJunction<?> theBool, ValueSet.ConceptSetFilterComponent theFilter) {
throw new UnsupportedOperationException();
// FIXME: DM 2019-09-25 - Filter with op=IN on ancestor; see #1512 in GitHub.
// FIXME: DM 2019-09-26 - Once implemented, fix changelog entry for #1454 in changes.xml
// String[] values = theFilter.getValue().split(",");
// for (String value : values) {
// logFilteringValueOnProperty(value, theFilter.getProperty());

44
src/changes/changes.xml
View File

@ -42,7 +42,7 @@
</action>
<action type="add" issue="1489">
<![CDATA[
<b>Improovement</b>:
<b>Improvement</b>:
A significant performance improvement was made to the parsers (particularly the Json Parser)
when serializing resources. This work yields improvements of 20-50% in raw encode speed when
encoding large resources. Thanks to David Maplesden for the pull request!
@ -90,11 +90,11 @@
The informational message returned in an OperationOutcome when a delete failed due to cascades not being enabled
contained an incorrect example. This has been corrected.
</action>
<action type="fix">
In some cases, deleting a CodeSystem resource would fail because the underlying
codes were not correctly deleted from the terminology service tables. This is
fixed.
</action>
<action type="fix">
In some cases, deleting a CodeSystem resource would fail because the underlying
codes were not correctly deleted from the terminology service tables. This is
fixed.
</action>
<action type="change">
Two foreign keys have been dropped from the HFJ_SEARCH_RESULT table used by the FHIR search query cache. These
constraints did not add value and caused unneccessary contention when used under high load.
@ -114,7 +114,7 @@
leaving the Bundle.entry.request.method blank in DSTU3 transactions and setting the request payload
as a Binary resource containing a valid patch.
</action>
<action type="change" issue="1366">
<action type="change">
The HAPI FHIR CLI server now uses H2 as its database platform instead of Derby.
Note that this means that data in any existing installations will need to be
re-uploaded to the new database platform.
@ -218,6 +218,36 @@
handled by method implementations that did not have any <![CDATA[<code>@IncludeParam</code>]]> defined. This
is now corrected. Thanks to Tuomo Ala-Vannesluoma for reporting and providing a test case!
</action>
<action type="add" issue="1366">
The ValueSet operation <![CDATA[<code>$expand</code>]]> has been optimized for large ValueSets. ValueSets are
now persistence-backed by the terminology tables, which are populated by a scheduled pre-expansion process.
A ValueSet previously stored in an existing FHIR repository will need to be re-created or updated to make
it a candidate for pre-expansion. ValueSets that have yet to be pre-expanded will continue to be expanded
in-memory.
</action>
<action type="add" issue="1431">
The ValueSet operation <![CDATA[<code>$validate-code</code>]]> has been optimized for large ValueSets.
Codes in ValueSets that have yet to be pre-expanded will continue to be validated in-memory.
</action>
<action type="add" issue="1447">
LOINC filenames for terminology upload are now configurable using the
<![CDATA[<code>loincupload.properties</code>]]> file.
</action>
<action type="add" issue="1451">
Support for the LOINC <![CDATA[<code>EXTERNAL_COPYRIGHT_NOTICE</code>]]> property and
<![CDATA[<code>copyright</code>]]> filter has been added.
</action>
<action type="add" issue="1453">
Support for the LOINC <![CDATA[<code>parent</code>]]> and <![CDATA[<code>child</code>]]> filters has been
added. Both filters can be used with either of the <![CDATA[<code>=</code>]]> or
<![CDATA[<code>in</code>]]> operators.
</action>
<action type="add" issue="1454">
Support for the LOINC <![CDATA[<code>ancestor</code>]]> and <![CDATA[<code>descendant</code>]]> filters has
been added. The <![CDATA[<code>descendant</code>]]> filter can be used with either of the
<![CDATA[<code>=</code>]]> or <![CDATA[<code>in</code>]]> operators. At present, the
<![CDATA[<code>ancestor</code>]]> filter can only be used with the <![CDATA[<code>=</code>]]> operator.
</action>
</release>
<release version="4.0.3" date="2019-09-03" description="Igloo (Point Release)">
<action type="fix">