When FT_USE_ATTACHMENT_WHITE_LIST=1 is enabled, Japanese (non ASCII) text in .txt file is not found by full-text search
FT_USE_ATTACHMENT_WHITE_LIST=1 is disabled (Default state):
- Full-text search can find a text contained in a .txt file attached to a document.
- Full-text search can not find a text contained in a .txt file in a .zip container file attached to a document.
FT_USE_ATTACHMENT_WHITE_LIST=1 is enabled:
- Full-text search can find ASCII character strings in the text contained in a .txt file attached to a document, but cannot find Japanese (non ASCII) character strings.
- Full-text search can find a text contained in a .txt file in a .zip container file attached to a document.
As described in the help document below, when FT_USE_ATTACHMENT_WHITE_LIST=1 is set, .txt files are not allowed to create full-text indexing and .zip files are allowed.
Configuring the attachment types that can be full-text indexed
https://help.hcltechsw.com/domino/10.0.1/admn_attachment_indexing_customizing.html
Full-text indexes are created by the Brute Force method for the file types with the following extensions.
*.txt, *text, *.log, *.out, *.sms, *.ans, *.ascii, *.uni, *.utxt
If a full-text index of the .txt file is not created by the Tika conversion filter, Brute Force will create a full-text index of ASCII strings only.
When FT_USE_ATTACHMENT_WHITE_LIST=1 is set, there is no mention in the help document that a full-text index of the .txt file will not be created. Full-text index of the .txt file should still be created in such cases.
