Hello,
I've been helping, or trying to help, a customer of mine with changing the service accounts that run their LFS and LFFTS services. While I've been doing that, I've been testing some things out regarding the search catalogs and I'd like some clarification on some things.
Say I have a directory that used to be a repository's search catalog but hasn't been for months - a new catalog was created. If I change the search catalog path in the Administration Console back to the old path, I can't get any text searches to work on documents that have been created since the search catalog was changed; that makes sense to me - how is the old catalog supposed to know anything about newer documents?
I can run a search using search syntax: {LF:Indexed=N} and that should supposedly bring up documents that aren't indexed, and this is where I must be misunderstanding some things. In the case I described above, I would have thought that documents created since the new search catalog was created would show up in this search - these documents aren't a part of the search catalog. But I get no results returned instead.
Even if that search returned results, what needs to happen in order to get a document indexed if it isn't? OCRing seems to work, even if the document already has text - is that the only way?
Thanks!
Question
Question
LFFTS - search catalogs and indexing
Replies
If things have gotten split up in weird ways, and this repo isn't in the tens of terabytes ranges, I'd personally reindex the entire thing with the Laserfiche QuickReindex Utility to start fresh.
That's my plan - just reindex the whole thing over the weekend. I'll look into that utility - haven't used it before. Thanks!
One other thing - is there a best practice for where the search catalog should reside in regards to where LFFTS is installed? Does it make sense to put the search catalog on the same machine as LFFTS just to eliminate that cross-network traffic of LFFTS accessing the search catalog?
Storing the search catalog on an SSD-backed disk (not C:\) attached to the LFFTS server is typically best, followed by an SSD-backed file server/share on the local network, followed by HDD local disk, followed by HDD file server/share.