Skip to content
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

Does grabbit write assets to S3 datastore? Appears that assets are written to segmentstore. #231

Open
ggindlin opened this issue Jul 2, 2019 · 1 comment

Comments

@ggindlin
Copy link

ggindlin commented Jul 2, 2019

Thanks for taking the time to fill out an issue! To help the community solve your issue, please provide answers to the following questions, along with supporting log and configuration files.

What version of AEM are you running?

How do you produce the issue?

Does the issue occur consistently?

Any additional details?

@sagarsane
Copy link
Contributor

@ggindlin Grabbit uses JCR Node APIs to persist the content and thus does not have control over where assets are physically written.

It only has access to the content paths set up in the Grabbit Configuration file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants