You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by GitBox <gi...@apache.org> on 2021/06/09 04:19:44 UTC

[GitHub] [sling-org-apache-sling-jcr-repoinit] cziegeler commented on pull request #18: SLING-10418 implement a retry for the application of the statements

cziegeler commented on pull request #18:
URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/18#issuecomment-857360154


   I still don't understand why we need to apply this blindly to every operation. creating a path seems to be the critical one. So why not just handle this?
   In addition, as mentioned in the comment - logging the same exception/error several times is not user friendly. If the error is transient and a retry is solving the problem, don't log any error/exception because from a user perspective there is no error. If the error is not transient, log a single error/exception, because again from a user perspective there is only one error not N.,


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org