-
Notifications
You must be signed in to change notification settings - Fork 253
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
Labels
Comments
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
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
7 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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:
fhirEngine.update
on the same resourceDateTimeIndexEntity
table using Android Studio app inspection for the_lastUpdated
indexes for the specific resourceExpected 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 indexScreenshots
N/A
Smartphone (please complete the following information):
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.
The text was updated successfully, but these errors were encountered: