$expand operation - Hibernate Search was not initialized

724 views
Skip to first unread message

Nobert Mijumbi

unread,
Jun 24, 2021, 9:29:15 AM6/24/21
to HAPI FHIR
Hi,

I am running HAPI FHIR 5.4.0 - R4. I have having and issue whenever i try to valuesets with the $expand operation.
{
"resourceType": "OperationOutcome",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>Failed to call access method: org.hibernate.search.util.common.SearchException: HSEARCH800001: Hibernate Search was not initialized.</pre></td>\n\t\t\t</tr>\n\t\t</table>\n\t</div>"
},
"issue": [ {
"severity": "error",
"code": "processing",
"diagnostics": "Failed to call access method: org.hibernate.search.util.common.SearchException: HSEARCH800001: Hibernate Search was not initialized."
} ]
}

Does anyone have an idea what could be going on.

Thanks
Nobert

Ally Shaban

unread,
Jul 6, 2021, 4:37:32 AM7/6/21
to HAPI FHIR
For records to whoever comeback here, this can be fixed by enabling hibernate.search on the configuration file.

Vivek

unread,
Dec 6, 2021, 7:30:23 AM12/6/21
to Ally Shaban, HAPI FHIR
Anyone tried this by enabling through environment variables in docker/K8S. What is the environment variable used?
Tried this : SPRING_JPA_PROPERTIES_HIBERNATE_SEARCH_ENABLED and all other possible combinations, but could not get it to work.
Any help would be appreciated.

--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hapi-fhir/84b1795a-499b-4c86-a904-395a795db140n%40googlegroups.com.


--
Regards,
Vivek

pa.f....@gmail.com

unread,
Dec 6, 2021, 7:39:02 AM12/6/21
to HAPI FHIR

Vivek

unread,
Dec 6, 2021, 7:43:48 AM12/6/21
to pa.f....@gmail.com, HAPI FHIR
Thanks,I checked it already and it's working when I enable these values directly in the application.yaml. I was trying to send it as an environment variable at the docket container level. The same is working for spring.datasource.url , username and password configurations, but not for this.

Regards,
Vivek

Reply all
Reply to author
Forward
0 new messages