Release v0.18.0

CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## v0.18.0
+
+### New Features
+
+* Allow Population Basis Differ from Subject in Measures ([#768](https://github.com/samply/blaze/pull/768))
+* Implement Sorting by _lastUpdated ([#98](https://github.com/samply/blaze/issues/98))
+* Allow Metadata Requests in Batches ([#781](https://github.com/samply/blaze/pull/781))
+* Allow to Set Separate RocksDB WAL Dirs ([#791](https://github.com/samply/blaze/pull/791))
+
+The full changelog can be found [here](https://github.com/samply/blaze/milestone/36?closed=1).
+
 ## v0.17.12
 
 ### Security

README.md

@@ -14,7 +14,7 @@ The goal of this project is to provide a FHIR® Store with an internal CQL Evalu
 
 Blaze passes all [Touchstone FHIR 4.0.1 Basic Tests][12] and almost all [CQL Tests][3]. Please refer to the [Conformance](docs/conformance.md) section and report any issues you encounter during evaluation.
 
-Latest release: [v0.17.12][5]
+Latest release: [v0.18.0][5]
 
 ## Quick Start
 
@@ -24,7 +24,7 @@ In order to run Blaze just execute the following:
 
 ```sh
 docker volume create blaze-data
-docker run -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.17
+docker run -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.18
 ```
 
 Blaze will create multiple directories inside the `blaze-data` volume on its first start and use the same directories on subsequent starts.
@@ -72,7 +72,7 @@ Unless required by applicable law or agreed to in writing, software distributed
 
 [3]: <https://cql.hl7.org/tests.html>
 [4]: <https://alexanderkiel.gitbook.io/blaze/deployment>
-[5]: <https://github.com/samply/blaze/releases/tag/v0.17.12>
+[5]: <https://github.com/samply/blaze/releases/tag/v0.18.0>
 [6]: <https://www.yourkit.com/java/profiler/>
 [7]: <https://www.yourkit.com/.net/profiler/>
 [8]: <https://www.yourkit.com/youmonitor/>

docker-compose.yml

@@ -1,7 +1,7 @@
 version: '3.2'
 services:
   blaze:
-    image: "samply/blaze:0.17"
+    image: "samply/blaze:0.18"
     environment:
       BASE_URL: "http://localhost:8080"
       JAVA_TOOL_OPTIONS: "-Xmx2g"

docs/cql-queries.md

@@ -17,7 +17,7 @@ The most accessible way to create and execute CQL queries is to use the Quality
 If you don't already have Blaze running, you can read about how to do it in [Deployment](deployment/README.md). If you have Docker available just run:
 
 ```
-docker run -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.17
+docker run -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.18
 ```
 
 Start the Quality Reporting UI. You should see an empty measure list.

docs/cql-queries/command-line.md

@@ -15,7 +15,7 @@ git clone https://github.com/samply/blaze.git
 If you don't already have Blaze running, you can read about how to do it in [Deployment](../deployment/README.md). If you have Docker available just run:
 
 ```sh
-docker run -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.17
+docker run -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.18
 ```
 
 ## Import some data

docs/data-sync/docker-compose.yml

@@ -1,7 +1,7 @@
 version: '3.2'
 services:
   blaze:
-    image: "samply/blaze:0.17"
+    image: "samply/blaze:0.18"
     environment:
       BASE_URL: "http://localhost:8080"
       JAVA_TOOL_OPTIONS: "-Xmx4g"

docs/database/migration.md

@@ -22,7 +22,7 @@ backup of all the data Blaze has written to disk, **plan for a downtime**, delet
 Please start Blaze with a shell assuming that you use the volume `blaze-data`:
 
 ```sh
-docker run -it -v blaze-data:/app/data samply/blaze:0.17 sh
+docker run -it -v blaze-data:/app/data samply/blaze:0.18 sh
 ```
 
 in that shell, go into `/app/data` and list all directories:

docs/deployment/distributed/docker-compose.yml

@@ -72,7 +72,7 @@ services:
       HEAP_NEWSIZE: "200M"
 
   blaze-1:
-    image: "samply/blaze:0.17"
+    image: "samply/blaze:0.18"
     hostname: "blaze-1"
     environment:
       JAVA_TOOL_OPTIONS: "-Xmx4g"
@@ -102,7 +102,7 @@ services:
     - cassandra-3
 
   blaze-2:
-    image: "samply/blaze:0.17"
+    image: "samply/blaze:0.18"
     hostname: "blaze-2"
     environment:
       JAVA_TOOL_OPTIONS: "-Xmx4g"

docs/deployment/docker-deployment.md

@@ -11,7 +11,7 @@ docker volume create blaze-data
 ## Blaze
 
 ```sh
-docker run -d --name blaze -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.17
+docker run -d --name blaze -p 8080:8080 -v blaze-data:/app/data samply/blaze:0.18
 ```
 
 Blaze should log something like this:
@@ -27,7 +27,7 @@ Blaze should log something like this:
 2021-06-27T11:02:37.834Z ee086ef908c1 main INFO [blaze.core:64] - JVM version: 16.0.2
 2021-06-27T11:02:37.834Z ee086ef908c1 main INFO [blaze.core:65] - Maximum available memory: 1738 MiB
 2021-06-27T11:02:37.835Z ee086ef908c1 main INFO [blaze.core:66] - Number of available processors: 8
-2021-06-27T11:02:37.836Z ee086ef908c1 main INFO [blaze.core:67] - Successfully started Blaze version 0.17.12 in 8.2 seconds
+2021-06-27T11:02:37.836Z ee086ef908c1 main INFO [blaze.core:67] - Successfully started Blaze version 0.18.0 in 8.2 seconds
 ```
 
 In order to test connectivity, query the health endpoint:
@@ -47,7 +47,7 @@ that should return:
 ```json
 {
   "name": "Blaze",
-  "version": "0.17.12"
+  "version": "0.18.0"
 }
 ```
 
@@ -61,7 +61,7 @@ A Docker Compose file looks like this:
 version: '3.2'
 services:
   blaze:
-    image: "samply/blaze:0.17"
+    image: "samply/blaze:0.18"
     environment:
       BASE_URL: "http://localhost:8080"
       JAVA_TOOL_OPTIONS: "-Xmx2g"

docs/deployment/manual-deployment.md

@@ -2,12 +2,12 @@
 
 The installation works under Windows, Linux and macOS. The only dependency is an installed OpenJDK 11 or 17 with 17 recommended. Blaze is tested with [Eclipse Temurin][1].
 
-Blaze runs on the JVM and comes as single JAR file. Download the most recent version [here](https://github.com/samply/blaze/releases/tag/v0.17.12). Look for `blaze-0.17.12-standalone.jar`.
+Blaze runs on the JVM and comes as single JAR file. Download the most recent version [here](https://github.com/samply/blaze/releases/tag/v0.18.0). Look for `blaze-0.18.0-standalone.jar`.
 
 After the download, you can start blaze with the following command (Linux, macOS):
 
 ```sh
-java -jar blaze-0.17.12-standalone.jar -m blaze.core
+java -jar blaze-0.18.0-standalone.jar -m blaze.core
 ```
 
 Blaze will run with an in-memory, volatile database for testing and demo purposes.
@@ -17,14 +17,14 @@ Blaze can be run with durable storage by setting the environment variables `STOR
 Under Linux/macOS:
 
 ```sh
-STORAGE=standalone java -jar blaze-0.17.12-standalone.jar -m blaze.core
+STORAGE=standalone java -jar blaze-0.18.0-standalone.jar -m blaze.core
 ```
 
 Under Windows, you need to set the Environment variables in the PowerShell before starting Blaze:
 
 ```powershell
 $Env:STORAGE="standalone"
-java -jar blaze-0.17.12-standalone.jar -m blaze.core
+java -jar blaze-0.18.0-standalone.jar -m blaze.core
 ```
 
 This will create three directories called `index`, `transaction` and `resource` inside the current working directory, one for each database part used.
@@ -42,7 +42,7 @@ The output should look like this:
 2021-06-27T11:02:37.834Z ee086ef908c1 main INFO [blaze.core:64] - JVM version: 16.0.2
 2021-06-27T11:02:37.834Z ee086ef908c1 main INFO [blaze.core:65] - Maximum available memory: 1738 MiB
 2021-06-27T11:02:37.835Z ee086ef908c1 main INFO [blaze.core:66] - Number of available processors: 8
-2021-06-27T11:02:37.836Z ee086ef908c1 main INFO [blaze.core:67] - Successfully started Blaze version 0.17.12 in 8.2 seconds
+2021-06-27T11:02:37.836Z ee086ef908c1 main INFO [blaze.core:67] - Successfully started Blaze version 0.18.0 in 8.2 seconds
 ```
 
 In order to test connectivity, query the health endpoint:
@@ -62,7 +62,7 @@ that should return:
 ```json
 {
   "name": "Blaze",
-  "version": "0.17.12"
+  "version": "0.18.0"
 }
 ```
 

modules/rest-api/src/blaze/rest_api/capabilities.clj

@@ -117,7 +117,7 @@
          :copyright
          #fhir/markdown"Copyright 2019 - 2022 The Samply Community\n\nLicensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at\n\nhttp://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."
          :kind #fhir/code"instance"
-         :date #fhir/dateTime"2022-07-21"
+         :date #fhir/dateTime"2022-09-22"
          :software
          {:name "Blaze"
           :version version}

perf-test/gatling/pom.xml

@@ -5,7 +5,7 @@
 
   <groupId>samply.blaze</groupId>
   <artifactId>gatling</artifactId>
-  <version>0.17.12</version>
+  <version>0.18.0</version>
 
   <properties>
     <maven.compiler.source>1.8</maven.compiler.source>

pom.xml

@@ -3,7 +3,7 @@
     <modelVersion>4.0.0</modelVersion>
     <groupId>samply</groupId>
     <artifactId>blaze</artifactId>
-    <version>0.17.12</version>
+    <version>0.18.0</version>
     <name>blaze</name>
 
     <description>A FHIR Store with internal, fast CQL Evaluation Engine</description>

src/blaze/system.clj

@@ -85,7 +85,7 @@
 
 
 (def ^:private root-config
-  {:blaze/version "0.17.12"
+  {:blaze/version "0.18.0"
 
    :blaze/clock {}