Parameter:
FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MBShort description: Companion setting to the whitelist: sets an upper size limit (in MiB) for attachments; larger files are not indexed.
Profile
Parameter | FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB |
Category | Performance / Memory |
Component | Server, client |
Available since | 14.0 (HCL Domino — companion setting in modifying_file_attachment_indexing from 14.0/14.5) |
Supported versions | 14.0, 14.5, 14.5.1 |
GUI equivalent | Configuration document (NOTES.INI tab) or Desktop Settings policy → Custom Settings → notes.ini |
Possible values | Integer in MiB (mebibytes), e.g. 25, 50, 100, 250 |
Description
FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB is, according to HCL documentation, a companion setting to FT_INDEX_FILTER_ATTACHMENT_TYPES. While FT_INDEX_FILTER_ATTACHMENT_TYPES specifies which file extensions are included in the full-text index via the whitelist, FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB defines the maximum file size of these attachments. The value is an integer and is interpreted in MiB (mebibytes).Attachments larger than the configured value are not indexed even if their extension is on the whitelist. The parameter thus acts as a kind of brake for unwanted large PDFs, ZIP containers, or Office files that would otherwise disproportionately burden the Tika conversion filter and the FT subsystem (memory, CPU, index size).
Typical use: mail files or archive databases with large Office or PDF attachments, in which the full-text search should only capture content up to a practical size (e.g. 50 MiB).
Example configuration
FT_INDEX_FILTER_ATTACHMENT_TYPES=*.pdf,*.docx,*.xlsx,*.pptx,*.txt FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB=50
Runtime variant (server console):
set config FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB=50
Notes & pitfalls
- Effective exclusively in conjunction with the whitelist (
FT_INDEX_FILTER_ATTACHMENT_TYPESplus optionalFT_USE_ATTACHMENT_WHITE_LISTorFT_USE_MY_ATTACHMENT_WHITE_LIST). Without an active whitelist, the setting has no effect.
- Unit is MiB, not MB — 50 MiB = 52,428,800 bytes (factor 1024², not 1000²).
- Attachments above the limit are captured neither with Tika nor with brute-force text stripping — the attachment is simply not present in the FT index.
- Complementary to FTG_Index_Limit (limits the size per document in the FT index, not per attachment) and FTG_MAX_MB_PER_THREAD (memory hard limit per FT search thread).
- Change only takes effect on the next index run —
load updall -ffor affected databases forces a rebuild.