(total mail now) Hello Adam,
You are right that it might be a little confusing with all the different indexers. First of all, in the domain.xml in a namespace configuration, you say which indexer to use. Default, there is <indexer src="config/slide/dasl-indexer.xml"/> In principle, all our projects run with this dasl-indexer.xml (so I wouldn't see a reason to ever replace it). In the dasl-indexer.xml you can configure a cron job, for when the indexing queue is emptied. By default, every 3 or 5 sec is fine. When you remove/delete an entire index, the index is rebuild from scratch. When you restart a repository, the index is *only* rebuild, when there is no index present. So, when restarting a repository with no index, starts indexing the content. If, before finishing, you stop the repository again, and then start, the re-indexing won't continue. So, when re-indexing is done, the repository must finish this process. Hope this clarifies things a little, Regards Ard > > Gentlemen- > > Can someone explain the difference between the indexer's > referenced in > dasl-indexer.xml, property-indexer.xml and indexer.xml under > my config/slide > directory? We are seeing that our index is rebuilt on > startup only, and I > assume one of these files is the problem. Currently I have > the DASL_indexer > with the cron scheduled every 5 seconds, should I have the > others turned on > as well? If so what are reasonable values for what they are doing. > > > > Thanks for the help, > > Adam > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
