HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
From my observations, full-text indexes break on a regular basis and there is no maintenance program that can detect and repair the defect. Updall does not find the errors nor does updall repair the FT.
It would be urgent to see in Domino Administrator the size of the FT per DB or also the percentage size in relation to the database size.
I would also like to see in the statistics or the information of the FT, which attachment types occur in which number and what size their indexing takes (it could work something like DAOS Estimator).
Currently I always notice that the full text index is much too large and after discarding the FT and creating it again, the size is "normal" again (10 to 50% instead of 80 to 120%).
Since only on file level the size of the fulltext indexes can be examined (complex), I regularly delete the FTs with nshrun.
What Daniels nshrun can do for years is missing in the core product.
Full text is a black box that I can't trust. Who knows if the search result really covers all documents.
Can you please explain why you want to monitor the FTIndex size? Is there any problem you are trying to address?