[ https://issues.jboss.org/browse/RTGOV-461?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-461: ------------------------------------- Using a simple http client Perform POST on http://localhost:9200/rtgov/_analyze?analyzer with payload = ID-gbrown-redhat-34752-1402652608663-0-3 Result , see below. This displays how the string is represented in eleasticsearch The default value of a string is analyzed, therefore ES splits it up into multiple tokens. which your search matches. recommendation is to set the mapping of that field to "not_analyzed". This will prevent the spliting into token. http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/analysi... http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/mapping... I can test this this evening. I think i it may be worth while evaluating this as a default setting for all the objects managed by RTGov. I think i have accommodated for such default requirement with the based rtgov.mapping file. Result of analyzed string {"tokens":[{"token":"id","start_offset":0,"end_offset":2,"type":"<ALPHANUM>","position":1},{"token":"gbrown","start_offset":3,"end_offset":9,"type":"<ALPHANUM>","position":2},{"token":"redhat","start_offset":10,"end_offset":16,"type":"<ALPHANUM>","position":3},{"token":"34752","start_offset":17,"end_offset":22,"type":"<NUM>","position":4},{"token":"1402652608663","start_offset":23,"end_offset":36,"type":"<NUM>","position":5},{"token":"0","start_offset":37,"end_offset":38,"type":"<NUM>","position":6},{"token":"3","start_offset":39,"end_offset":40,"type":"<NUM>","position":7}]} -- This message was sent by Atlassian JIRA (v6.2.6#6264)