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

Old and outdated resource indexes still present in the database #1825

Closed
ekigamba opened this issue Jan 24, 2023 · 0 comments · Fixed by #1840
Closed

Old and outdated resource indexes still present in the database #1825

ekigamba opened this issue Jan 24, 2023 · 0 comments · Fixed by #1840
Assignees
Labels
effort:small Small effort - 2 days P1 High priority issue type:bug Something isn't working

Comments

@ekigamba
Copy link
Contributor

Describe the bug
FHIR Engine search results sometimes returns outdated results because old indexes are not deleted

Component
Core library

To Reproduce
Steps to reproduce the behavior:

  1. Select a resource to test with by it's ID and resourceUuid from the database
  2. Write code to fetch and call fhirEngine.update on the same resource
  3. Check the DateTimeIndexEntity table using Android Studio app inspection for the _lastUpdated indexes for the specific resource
  4. You'll realize that there are multiple indexes for the same property

Expected behavior
A clear and concise description of what you expected to happen.

Inspecting the database should show only a single record for the resource's _lastUpdated index. This should be the latest index

Screenshots
N/A

Smartphone (please complete the following information):

  • Device: Nexus 5X API 28 emulator
  • Android version: 9
  • Build number: PSR1.180720.117
  • Version 28

Additional context
Add any other context about the problem here.

Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

@ekigamba ekigamba changed the title Old and outdated record indexes still present in the database Old and outdated resource indexes still present in the database Jan 24, 2023
@ekigamba ekigamba added the type:bug Something isn't working label Jan 25, 2023
@PallaviGanorkar PallaviGanorkar added P2 Medium priority issue effort:medium Medium effort - 3 to 5 days effort:small Small effort - 2 days and removed effort:medium Medium effort - 3 to 5 days labels Jan 25, 2023
@omarismail94 omarismail94 added P1 High priority issue and removed P2 Medium priority issue labels Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:small Small effort - 2 days P1 High priority issue type:bug Something isn't working
Projects
Status: Complete
Development

Successfully merging a pull request may close this issue.

4 participants