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

Feature: Have the ability to configure a more comprehensive deltaContent #216

Open
mzgubin opened this issue Oct 4, 2018 · 0 comments
Open

Comments

@mzgubin
Copy link

mzgubin commented Oct 4, 2018

Currently when using deltaContent flag in the configurations the idea is that only content/nodes that have been created after the last run of grabbit will be copied over.
This presents a bit of an issue when something goes wrong and there is a failure.
When a failure occurs in the job run, the rest of the content that was supposed to be copied does not get copied.

And on subsequent job runs if the deltaContent flag is enabled what Grabbit does is only copy content after the last job run that contained that same path. So if the same job is retried it will skip over copying those nodes.

What would be great if we have the ability to specify another kind of deltaContent (maybe call it deepDeltaContent?) which would do a check on the target AEM instance to see if those files are there or not first instead of just comparing the timestamps.
I know this will tremendously slow down the copying, but might be really useful to get a comprehensive copy that ensures that all of the content does get copied over even if there were failures.

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

1 participant