Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next Link missing in search result bundle with DatabaseBackedPagingProvider for specific resource types #6549

Open
G-2-Z opened this issue Dec 9, 2024 · 0 comments

Comments

@G-2-Z
Copy link

G-2-Z commented Dec 9, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant