-
Notifications
You must be signed in to change notification settings - Fork 25
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
Restore lost data for orgs inherited from org1 #668
Comments
All data to be sent is uploaded here - https://drive.google.com/drive/u/4/folders/1gsrLmsvpZ6gbqxHEQb8zYRwUuQ0ALrWh |
Regarding the update of lastModifiedDateTime values, such as the following assignment:
Since 'current_timestamp' value remains fixed for all sql commands within a single transaction, we should also have made use of entity "id" value to ensure that the timestamps are slightly different for each entity to avoid skipping entities during sync fetch.
|
This would only ever be a partial restore of the data to a version available for the data of recovery. Rest of the data has to be reworked on by the organisations. Apart from data fix done as part of this card, @mahalakshme, @petmongrels and @vinayvenu are there some additional checks we could put in place to avoid these issues in future. |
After discussion, came to know of NPE being thrown in case Concept is not found during save of an Entity with observations. |
@himeshr @vinayvenu Once this(data recovery and data to be collected is sent) is done, also reply to the corresponding tickets: |
The text was updated successfully, but these errors were encountered: