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.

Sign up for GitHub

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

Jump to bottom

Handle issue that may arise during migration of timestamp value from string to Instant #2116

Closed
aditya-07 opened this issue Aug 4, 2023 · 0 comments · Fixed by #2117
Closed

Handle issue that may arise during migration of timestamp value from string to Instant #2116

aditya-07 opened this issue Aug 4, 2023 · 0 comments · Fixed by #2117
Assignees
@aditya-07
Labels
effort:small Small effort - 2 days
Milestone
FHIR Engine beta04

Comments

@aditya-07
Copy link
Collaborator 

          I'm wondering about if the string is (for some reason unclear to us) not convertible to a timestamp - how can we mitigate that? can we provide some level of error tolerance or at least recoverability for the client.

Originally posted by @jingtang10 in #2101 (comment)
@aditya-07 aditya-07 self-assigned this Aug 4, 2023
@aditya-07 aditya-07 mentioned this issue Aug 4, 2023
Merged
7 tasks
@aditya-07 aditya-07 added effort:small Small effort - 2 days effort:xsmall Extra small effort - 1 day and removed effort:small Small effort - 2 days effort:xsmall Extra small effort - 1 day labels Aug 7, 2023
@jingtang10 jingtang10 added this to the FHIR Engine beta04 milestone Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aditya-07 aditya-07

Labels
effort:small Small effort - 2 days
Projects
Android FHIR SDK
Status: Complete
Milestone
FHIR Engine beta04
Development

Successfully merging a pull request may close this issue.

Added a default value of EPOCH if migration from string to timestamp fails aditya-07/android-fhir
2 participants
@aditya-07 @jingtang10