-
Notifications
You must be signed in to change notification settings - Fork 567
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
Handle the case that a PO can't load a record #986
Comments
metas-ts
added a commit
that referenced
this issue
Feb 17, 2017
FRESH-1405 #986 Handle the case that a PO can't load a record
metas-ts
added a commit
that referenced
this issue
Feb 18, 2017
FRESH-1405 #986 Handle the case that PO can't load a record
metas-ts
added a commit
that referenced
this issue
Feb 20, 2017
FRESH-1405 #986 Handle the case that PO can't load a record
metas-ts
added a commit
that referenced
this issue
Feb 21, 2017
#986 Handle the case that PO can't load a record
metas-ts
added a commit
that referenced
this issue
Feb 21, 2017
FRESH-1372 #968 Include webui in the normal rollout process
metas-ts
added a commit
that referenced
this issue
Mar 5, 2017
* UnarchiveRecordHandler: unarchiving didn't work in-trx * SQL: aparently, a DDL fix was never stored in a migration script so far FRESH-1405 #986 Handle the case that PO can't load a record
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a bug or feature request?
feature request
What is the current behavior?
currently, if
PO
is invoked to load a record and can't get it from the DB, then an exception is thrown and an error is logged.What is the expected or desired behavior?
PO
shall retryPO
to retry.2.a) also consider showing a message to the user (but there we might need to make sure to collect such events and e.g. only show such a message with all of those events at the end of the transaction)
The text was updated successfully, but these errors were encountered: