I have a large repository that takes forever to index.
I added a whole bunch of hidden directories to suppress the indexing of the parts of the repository that people could live without. The hope was it would speed things up.
It turns out that some of the hidden directories need to be changed from hidden to not hidden.
My questions are:
Q1) does hiding a directory for an indexed repo keeps the directory from being crawled during the indexing process and therefore reduce indexing times? Or, are the hidden directories indexed, but the files aren't visible to the user?
Q2) unhiding a directory for an indexed repo will cause which of these to happen:
Q3) what is the difference in hide and exclude? it is confusing to me. Specifically, which one should be used to reduce indexing time?
thanks in advance,
-rob
Hello Robert,
Q1) does hiding a directory for an indexed repo keeps the directory from being crawled during the indexing process and therefore reduce indexing times? Or, are the hidden directories indexed, but the files aren't visible to the user?
Per our documentation, "FishEye will still index and cache these directories".
Q2) unhiding a directory for an indexed repo will cause which of these to happen:
- the whole repo will be re-indexed
- just an incremental indexing of those newly visible directories will occur
- no re-indexing at all- it will just allow the files to be viewable in GUI
- other
As you stated, no re-indexing at all. It will just allow the files to be viewable in GUI.
Q3) what is the difference in hide and exclude? it is confusing to me. Specifically, which one should be used to reduce indexing time?
In order to reduce indexing time, you should exclude paths from being indexed.
Thanks,
based on your answer I went ahead and removed the hidden directories and saved the repo settings.
You're absolutely right! it did not perform a re-index.
thanks a bunch!
-rob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.