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
[MRESOLVER-536] Followup change: log failures #471
Conversation
Do not swallow cases like AccessDeniedEx, and log failures. --- https://issues.apache.org/jira/browse/MRESOLVER-536
ping @Jurrie I know you are targeting 1.9.x but just FYI |
if (e instanceof AccessDeniedException) { | ||
throw e; | ||
} | ||
logger.debug("Failed to set last-modified: {}", path, e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be even on trace because it can be very verbose....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
if (e instanceof AccessDeniedException) { | ||
throw e; | ||
} | ||
logger.debug("Failed to set last-modified: {}", path, e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Failed to set last modified date: {}"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
Do not swallow cases like AccessDeniedEx, and log failures. Make new method
void
as nothing is interested in return value, while all we wanted (swallow some and log) is handled here.This PR builds upon prev PR #468
https://issues.apache.org/jira/browse/MRESOLVER-536