Add configuration flag to enable storing of resources in lucene index (#304)
* Add configuration flag to enable storing of resources in lucene index * Fix build issue * Fix code review suggestions Co-authored-by: Jaison B <jaison.baskaran@smilecdr.com>
This commit is contained in:
@@ -354,10 +354,14 @@ elasticsearch.schema_management_strategy=CREATE
|
||||
|
||||
Set `hapi.fhir.lastn_enabled=true` in the [application.yaml](https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/src/main/resources/application.yaml) file to enable the $lastn operation on this server. Note that the $lastn operation relies on Elasticsearch, so for $lastn to work, indexing must be enabled using Elasticsearch.
|
||||
|
||||
## Enabling Resource to be stored in Lucene Index
|
||||
|
||||
Set `hapi.fhir.store_resource_in_lucene_index_enabled` in the [application.yaml](https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/src/main/resources/application.yaml) file to enable storing of resource json along with Lucene/Elasticsearch index mappings.
|
||||
|
||||
## Changing cached search results time
|
||||
|
||||
It is possible to change the cached search results time. The option `reuse_cached_search_results_millis` in the [application.yaml] is 6000 miliseconds by default.
|
||||
Set `reuse_cached_search_results_millis: -1` in the [application.yaml] file to ignore the cache time every search.
|
||||
It is possible to change the cached search results time. The option `reuse_cached_search_results_millis` in the [application.yaml](https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/src/main/resources/application.yaml) is 6000 miliseconds by default.
|
||||
Set `reuse_cached_search_results_millis: -1` in the [application.yaml](https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/src/main/resources/application.yaml) file to ignore the cache time every search.
|
||||
|
||||
## Build the distroless variant of the image (for lower footprint and improved security)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user