I was not happy the way kibana showing it in table as the whole string was separated into words, so I changed my mapping back to
"alertmsg": {"type":"string","index" : "not_analyzed","doc_values" : true}
I can still see this field as analyzed field not sure why , do I need re-indexing in this case . As per my understanding since i have changed mapping from analyzed to not_analyzed , so from now on this field will act as not_analyzed field and for old data it will remain analyzed ? Please correct me if I am wrong , because if this is the case it should implement , or I may be missing something ?
Thanks for the quick response , I have another query . Is it possible to make a field full text search wih not_analyzed . Why I am asking this is when I create a field analyzed with standard tokenizer it cuts the whole string into words and that's look ugly in kibana table .
What I want is to show a complete sting **"malicious ips"*in the table row but full text search should be enable on that string so that I can search it like alertmsg:malicious.
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.