Allowing custom analyzer for a field will help us deciding tokenization process
We are using search service in industrial domain for searching some information in the plant. They follow some nomenclature for some of fields like BLG1TEMPReact_South. In above case i want to tokenize based on underscore and camel casing because currently it is tokenized as one word and substring is not supported. Hence currently we are pre-processing this and storing in a seperate collection<string> field. But it would be nicer if custom analyzer for some field type is allowed.
We have enabled this feature in our most recent Preview API version: 205-02-28-Preview
Please take a look the following blog post and documentation for more information :