Hi That is correct.
Doc values can be enabled for numeric, date, Boolean, binary, and geo-point fields, and for not_analyzed string fields. <https://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html#id-1.7.12.6.9.2.2> <https://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html#id-1.7.12.6.9.2.3>They do not currently work with analyzed string fields. Doc values are enabled per field in the field mapping, which means that you can combine in-memory fielddata with doc values: Your error message will have been similar to { "error": "MapperParsingException[mapping [mytype]]; nested: MapperParsingException[Field [myfield] cannot be analyzed and have doc values]; ", "status": 400 } On 28 May 2015 at 11:03, vikas gopal <vikas.ha...@gmail.com> wrote: > Thanks Allan, > > I have changed it to ""Customer": {"type": "string","index" : > "analyzed","doc_values" : true ,"analyzer":"analyzer_keyword"}," , but with > this setting LS is not able to create an index. > > > On Thursday, May 28, 2015 at 2:40:14 PM UTC+5:30, Allan Mitchell wrote: >> >> Hi >> >> >> "Customer" is set to be "not_analyzed" so won't go through your analyser. >> >> not_analyzedIndex this field, so it is searchable, but index the value >> exactly as specified. Do not analyze it. >> >> On 28 May 2015 at 09:45, vikas gopal <vikas...@gmail.com> wrote: >> >>> Hi Experts, >>> >>> In my log I have a field "Customer". It has all the values in capital >>> latter like "VIKAS". Now when I fire query in Kibana like Customer:"vikas" >>> or Customer:"VIK*" I got nothing . It works only when I do exact search >>> like Customer:"VIKAS". >>> >>> I have following question >>> >>> 1) How I can search value with wildcard, something like name start with >>> vi OR VI ? >>> >>> My Template is like >>> >>> { >>> "template_vg":{ >>> "template" : "vg*", >>> "settings" : { >>> "number_of_shards" : 5, >>> "index.cache.field.type" : "soft", >>> "index.refresh_interval" : "5s", >>> "index.store.compress.stored" : true, >>> "index.query.default_field" : "message", >>> "index.routing.allocation.total_shards_per_node" : 5, >>> "index":{ >>> "analysis":{ >>> "analyzer":{ >>> "analyzer_keyword":{ >>> "type": "custom", >>> "tokenizer":"keyword", >>> "filter":"lowercase" >>> } >>> } >>> } >>> } >>> }, >>> "mappings" : { >>> "_default_" : { >>> "_all" : {"enabled" : false}, >>> "properties" : { >>> "Order_ID": {"type": "string","index" :"not_analyzed","doc_values" : >>> true}, >>> "Customer": {"type": "string","index" : "not_analyzed","doc_values" : >>> true ,"analyzer":"analyzer_keyword"}, >>> "Ordered_On": {"type": "string","index" : "not_analyzed","doc_values" : >>> true }, >>> "Required_By": {"type": "string","index" : "not_analyzed","doc_values" : >>> true }, >>> "Freight": {"type": "string","index" : "not_analyzed","doc_values" : >>> true }, >>> "Shipped_On": {"type": "string","index" : "not_analyzed","doc_values" : >>> true }, >>> "Country": {"type": "string","index" : "not_analyzed","doc_values" : >>> true }, >>> "Post_Code": {"type": "string","index" : "not_analyzed","doc_values" : >>> true } >>> } >>> } >>> } >>> } >>> } >>> >>> >>> I read almost everything and got an idea that I need to use analyzer >>> with Lowercase filter which will convert my values to lowercase then I can >>> apply wildcard.But with the above analyzer for Customer I still got nothing >>> . Can someone help me to understand what I am doing wrong . >>> >>> -- >>> Please update your bookmarks! We have moved to >>> https://discuss.elastic.co/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "elasticsearch" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to elasticsearc...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/eb6bda79-428d-4fdc-b478-65f07905fe89%40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/eb6bda79-428d-4fdc-b478-65f07905fe89%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > Please update your bookmarks! We have moved to https://discuss.elastic.co/ > --- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/46c4f481-6876-463b-9c7e-bfb22e4acdee%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/46c4f481-6876-463b-9c7e-bfb22e4acdee%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Please update your bookmarks! We have moved to https://discuss.elastic.co/ --- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAECdJzC6625TyyB%3DnaQr0o3vgcP5Krcy8x2_PA7Nv2DLjGoNvg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.