Semantic Search uses System Locale setting to look for stopwords in document stored in FileTables - by MauriD

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
1
Sign in
to vote
ID 753596 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 7/13/2012 7:01:11 AM
Access Restriction Public

Description

When using FileTable to store documents, the language used to check if stopwords are present in the indexed documents is the one defined as System Locale and not the one defined in the full-text index.

The attached script shows the behavior (please note that in order to replicate the problem, System Locale MUST not be in English. Use Italian for Example.)
Sign in to post a comment.
Posted by Matija Lah on 3/17/2013 at 10:09 AM
While this behavior makes perfect sense, it might be completely unexpected.

Please, make sure this is documented appropriately!
Posted by Venkatraman [MSFT] on 3/6/2013 at 8:22 AM
This is by design. In the attached script the Text IFilter would emit the System Locale for the work chunks. And we go by whatever the IFilter emits.
The full-text index language will be used when we have a plain text column without the doctype column.
Posted by Matija Lah on 7/16/2012 at 3:18 PM
Of course, if the language used for system locale is not supported by statistical semantic search, semanticsdb is not populated (which is, however, correctly reflected in the full-text crawl log).