Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Version purge 6.4

Shakthi1
Level 4
Level 4

I configured daily take of version purge but that did not delete the version.this was configured under the maintenance task page.

Also the curl command did not purge the versions.Please can you advise if the version purge steps are different in 6.4 and is the below curl command still good in 6.4.

Thanks in advance.

curl --silent -u admin:admin -f -o /proj/purge_log/vista_feature_purge.txt -d "cmd=purge&maxdays=1&maxversions=1&path=pathofconent&recursive=true" "http://localhost:4502/etc/versioning/purge.html"

1 Accepted Solution
Gaurav-Behl
Correct answer by
Community Advisor
Community Advisor

Limit  # page version creation, paths under which version can be created implicitly and age of versions. You could even choose to stop implicit version creation (after evaluating pros/cons) and move into manual mode that would be done by authors explicitly for specific project(s).That depends on your requirements.

Limit the age of versions so that you have less numbers of purge activities based on your requirements/compliance etc.

Schedule the purge job to run on off-business hours when no author is creating versions. That should not slow down the system.

I'm not aware of any patch for same. DayCare ticket is your best bet for patches.

1712450_pastedImage_0.png

1712451_pastedImage_4.png

couple of links in case you want to proceed with a custom solution -

Adobe CQ/Adobe AEM: How to work with Version in CQ

http://localhost:4502/libs/cq/workflow/admin/console/content/launchers.html

View solution in original post

7 Replies
Shakthi1
Level 4
Level 4

also getting the error

org.apache.jackrabbit.oak.plugins.index.lucene.directory.CopyOnWriteDirectory COWRemoteFileReference::local file (_1re.cfe) doesn't exist

Gaurav-Behl
Community Advisor
Community Advisor

Just tested 'dryrun' on 6.4.3 & it works fine

curl -u admin:admin -f -o progress.txt -d "cmd=dryrun&maxdays=0&maxversions=5&path=/content&recursive=true" "http://localhost:4502/etc/versioning/purge.html"

Schedule a version purge

Shakthi1
Level 4
Level 4

HI Gaura,

Thanks a lot for the reply.Actualy we are on 6.4 version.

The issue is whne we update the node version is created and we want to hold the versions.

But the process takes lot of time .and slows down the system.Is there any fix patc that needs to be installed on 6.4 to mitigate this issue.Request you to please advise.

thanks.

Gaurav-Behl
Correct answer by
Community Advisor
Community Advisor

Limit  # page version creation, paths under which version can be created implicitly and age of versions. You could even choose to stop implicit version creation (after evaluating pros/cons) and move into manual mode that would be done by authors explicitly for specific project(s).That depends on your requirements.

Limit the age of versions so that you have less numbers of purge activities based on your requirements/compliance etc.

Schedule the purge job to run on off-business hours when no author is creating versions. That should not slow down the system.

I'm not aware of any patch for same. DayCare ticket is your best bet for patches.

1712450_pastedImage_0.png

1712451_pastedImage_4.png

couple of links in case you want to proceed with a custom solution -

Adobe CQ/Adobe AEM: How to work with Version in CQ

http://localhost:4502/libs/cq/workflow/admin/console/content/launchers.html

View solution in original post

Shakthi1
Level 4
Level 4

Thanks a lot that is very useful.

1.As per the documentation in

      http://www.wemblog.com/2012/08/how-to-work-with-version-in-cq.html

      i don't find repository.xml  under  /crx-quickstart/repository/repository.xml .

     Is this relevant for 6.4 version.Please can you tell where this configurations exist in 6.4.

Please find the below screen shot.

1712818_pastedImage_1.png

2.

Also from application end we have created index under /oak:index/appNameLucene. but on the logs get the below when i do re-indexing

" consider creating an index or changing the query".

Gaurav-Behl
Community Advisor
Community Advisor

That article was for reference, you won't find repo.xml in 6.4

Configure the same in Day CQ WCM Version Manager and Purge Task available under /system/console/configMgr

How is this indexing issue related to version purging? You'd need to fix your index definition for that.