You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We've encountered an unusual behavior in our custom HAPI FHIR server, based on the starter project and we were unable to make sense of it. Some but not all deployments show this behavior for some of the resources.
When performing searches, for e.g. Provenances, the search bundle doesn't generate a 'next-link' for additional pages, despite us knowing there should be more. We are using the default DataBaseBackedPagingProvider.
It's important to note that we filter out some returned resources via AuthorizationInterceptor and ConsentService, but the same codebase works as expected in another deployment environment.
We've been unable so far to identify the source of the issue and where not able to reproduce it. Does anyone know a reason why this might happen? Which part of the pagination might fail here?
We would greatly appreciate any assistance or suggestions for further troubleshooting, or any ideas that might help us resolve this.
To Reproduce
If only we knew.
Expected behavior
Returned bundles for search queries matching more than page size results should contain a next link where the next paginated bundle can be found.
Environment (please complete the following information):
HAPI FHIR Version: 7.2.1
OS: Inside container based on distroless debian
DB: PostgreSQL
The text was updated successfully, but these errors were encountered:
Describe the bug
We've encountered an unusual behavior in our custom HAPI FHIR server, based on the starter project and we were unable to make sense of it. Some but not all deployments show this behavior for some of the resources.
When performing searches, for e.g. Provenances, the search bundle doesn't generate a 'next-link' for additional pages, despite us knowing there should be more. We are using the default
DataBaseBackedPagingProvider
.It's important to note that we filter out some returned resources via
AuthorizationInterceptor
andConsentService
, but the same codebase works as expected in another deployment environment.We've been unable so far to identify the source of the issue and where not able to reproduce it. Does anyone know a reason why this might happen? Which part of the pagination might fail here?
We would greatly appreciate any assistance or suggestions for further troubleshooting, or any ideas that might help us resolve this.
To Reproduce
If only we knew.
Expected behavior
Returned bundles for search queries matching more than page size results should contain a next link where the next paginated bundle can be found.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: