FHIR Chat · Upgrading from 4.1.0 to 4.2.0 · hapi

Stream: hapi

Topic: Upgrading from 4.1.0 to 4.2.0


view this post on Zulip Hershil Patel (Feb 26 2020 at 21:44):

I am trying to update to HAPI 4.2.0 from HAPI 4.1.0 . Currently I have the example from the documentation in my test case:

    Bundle results = ourClient
              .search()
              .forResource(Patient.class)
              .where(Patient.FAMILY.matches().value("duck"))
              .returnBundle(Bundle.class)
              .execute();

My client search tests work in 4.1.0 but fail in 4.2.0 with a "HTTP 500 Server Error: Column 'SEARCH_LAST_RETURNED' cannot accept a NULL value.".

Is there anything I am doing wrong?

Here is the stack trace:

ca.uhn.fhir.rest.server.exceptions.InternalErrorException: HTTP 500 Server Error: Column 'SEARCH_LAST_RETURNED' cannot accept a NULL value.
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
at ca.uhn.fhir.rest.server.exceptions.BaseServerResponseException.newInstance(BaseServerResponseException.java:302)
at ca.uhn.fhir.rest.client.impl.BaseClient.invokeClient(BaseClient.java:349)
at ca.uhn.fhir.rest.client.impl.GenericClient$BaseClientExecutable.invoke(GenericClient.java:434)
at ca.uhn.fhir.rest.client.impl.GenericClient$SearchInternal.execute(GenericClient.java:1838)...

view this post on Zulip James Agnew (Feb 27 2020 at 10:51):

Hi Hershil,

Can you try running the migrator tool? https://hapifhir.io/hapi-fhir/docs/server_jpa/upgrading.html What does the output look like?

view this post on Zulip Hershil Patel (Feb 28 2020 at 17:27):

I am using derby, but I ended up deleting and recreating the database and that fixed it! Thanks for your help


Last updated: Apr 12 2022 at 19:14 UTC