The string field PrimaryAssembly is being "analyzed" by ES. You can either:
Create a template and set {"index": "not_analyzed"} for any string field that matches a pattern. In your case, it would be {"match": "PrimaryAssembly"} (this requires re-indexing the data)
OR
Add a raw sub-field (i.e. PrimaryAssembly.raw) and set it to be "not_analyzed". This is probably ideal if you don't want to re-index. But any saved searches and Kibana charts will have to be edited to reference the new "not_analyzed" field
There are many ways, depends on what you want to do. For example, if you want every string field in all indices created from now on to have a raw "not_analyzed" subfield, you can create a dynamic template that matches all (or just certain indices and fields). The example below create a new dynamic template named "receipt". Any new indices created with name matches the pattern "receipt-*" (defined by the template parameter) will have all of its string fields, regardless of name (this can be controlled by the match parameter), appended with a raw subfield:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.