You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by GitBox <gi...@apache.org> on 2020/07/21 14:54:26 UTC
[GitHub] [sling-org-apache-sling-distribution-journal-messages] tmaret commented on pull request #4: SLING-9593: Abstract out binary handling to allow plugging of different stores
tmaret commented on pull request #4:
URL: https://github.com/apache/sling-org-apache-sling-distribution-journal-messages/pull/4#issuecomment-661910485
It makes sense to avoid ResourceResolver as it's tied to the Sling repository and we will likely store packages not managed by Sling (e.g. Azure blobs, S3, etc.).
What is the proposed alternative API exactly ?
Regarding the transition, storing the packages under a different path would indeed only affect the collection of the packages. It would not impact importing the packages because those are resolved at the JCR level with references pointing to the blob store. As pointed out by @cschneider, barely any packages are stored in JCR anyway, we added that path for compatibility reason, knowing it'd be barely used. Our 1500+ cloud environment exhibit 0 occurrence over last week for instance.
----------------------------------------------------------------
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