Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 389
  • Last Modified:

Yet Another CF/Verity Question....

I have a collection which indexes all htm, cfm and pdf (adobe acrobat) files under the root.  I would like the collection to be *completely* reindexed every night, as the website goes through many changes during the day.  I have it set up to run an indexing file at night, which simply has a <cfindex action="update"> tag.  That seemed to work for a while, until I noticed that it was only indexing files which have been added, and not removing files from the index which have been removed, or reindexing files which have been changed.  Soooo, I try running <cfindex action="refresh">, and now the collection is empty; I reindex using <cfindex action="update"> and it only indexes htm and cfm files, not pdf, despite the fact that I have the extensions attribute set to extensions=".htm, .html, .cfm, .cfml, .pdf".  So I try purging and reindexing using action="purge" and then action="update", and same thing.  The only solution I've discovered is to completely delete the collection and then recreate it and THEN run <cfindex action="update">.  However when I try to automate that with the aforementioned indexing page, it seems to delete the collection (doesn't show up on cfadmin page) but the directory is locked up on the server, which means I have to go in and stop/start the service before I can delete the directory.  Then I can recreate the collection and index it and it works fine.  But sooooo cloogy, not to mention a pain in the you know what.  Any ideas?
2 Solutions
You've definitely got the right strategy there!  I've got indexing scripts set up on a dozen or so CF webservers, and for each I've had to write scripts to delete, create, then update the collections.  As for your locked directory problem, you need to check the PATH attribute of your CFCOLLECTION tag, and make sure it's pointing at the right place.  If that's okay then I'm stumped!


One other thing to watch out for:  no one can be searching the indexes while you are updating them.  I set a lock in the database to disallow searching while the indexes are refreshing, which can take a while.  It usually corrupts the search index if someone is searching it and then I can't purge it, repair it, nothing works until I delete the collection remake it and reindex it.
No comment has been added lately, so it's time to clean up this question.
I will leave the following recommendation in the Cleanup topic area:

Split techy6 & cdillon

Please leave any comments here within the next four days.

EE Cleanup Volunteer

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now