From 1133c5a6fc924b7a955c969ea30baa4efc23dd50 Mon Sep 17 00:00:00 2001 From: Ken Stevens Date: Mon, 20 Apr 2020 17:24:30 -0400 Subject: [PATCH] retroactively add javadoc for a search database change --- .../4_3_0/1698-remove-search-last-used-column.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/4_3_0/1698-remove-search-last-used-column.yaml diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/4_3_0/1698-remove-search-last-used-column.yaml b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/4_3_0/1698-remove-search-last-used-column.yaml new file mode 100644 index 00000000000..81a34c55ed7 --- /dev/null +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/4_3_0/1698-remove-search-last-used-column.yaml @@ -0,0 +1,10 @@ +--- +type: change +issue: 1698 +title: "Removed the SEARCH_LAST_RETURNED column of the HFJ_SEARCH table. Hapi updated the HFJ_SEARCH table with every +request, but this led to unecessary database load. The purpose of this column was to ensure that search results were +kept around long enough for systems that needed them for paging (default one hour). When expiring search results, +we used to add one hour to SEARCH_LAST_RETURNED to determine the expiry time. However, the length of time where a search +result could be updated was relatively small (default one minute). So rather than keeping track of the expiry time to expire +exactly one hour after the last returned time, hapi now simply expires after the maximum possible length of time (default one hour +plus one minute). This eliminates the need to update the HFJ_SEARCH table with every search."