问题
We need to create a field for an Index that is not going to be tokenised but still be searchable. In Azure Search if you make a field searchable, then the contents of the field are tokenised. If you make it filterable (documentation says then it wont be tokenised) then you cannot search it. In Lucene a KeywordAnalyzer does this job. Since Azure Search is also using Lucene cant understand why we cannot store a field contents AS IS in the index for searching WITHOUT splitting all the words/removing stop words etc. etc. Would appreciate any assistance
回答1:
Using keyword and other Lucene analyzers is now possible using Custom analyzers feature of Azure Search. Note: this functionality is still in preview.
HTH!
来源：https://stackoverflow.com/questions/34303438/azure-search-analyzer