{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/kibana/issues/7419","repository_url":"https://api.github.com/repos/elastic/kibana","labels_url":"https://api.github.com/repos/elastic/kibana/issues/7419/labels{/name}","comments_url":"https://api.github.com/repos/elastic/kibana/issues/7419/comments","events_url":"https://api.github.com/repos/elastic/kibana/issues/7419/events","html_url":"https://github.com/elastic/kibana/issues/7419","id":159651342,"number":7419,"title":"Multi-fields not showing up in Discovery interface field list","user":{"login":"djschny","id":129643,"avatar_url":"https://avatars.githubusercontent.com/u/129643?v=3","gravatar_id":"","url":"https://api.github.com/users/djschny","html_url":"https://github.com/djschny","followers_url":"https://api.github.com/users/djschny/followers","following_url":"https://api.github.com/users/djschny/following{/other_user}","gists_url":"https://api.github.com/users/djschny/gists{/gist_id}","starred_url":"https://api.github.com/users/djschny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djschny/subscriptions","organizations_url":"https://api.github.com/users/djschny/orgs","repos_url":"https://api.github.com/users/djschny/repos","events_url":"https://api.github.com/users/djschny/events{/privacy}","received_events_url":"https://api.github.com/users/djschny/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/elastic/kibana/labels/discuss","name":"discuss","color":"cc317c"},{"url":"https://api.github.com/repos/elastic/kibana/labels/enhancement","name":"enhancement","color":"009800"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-06-10T14:45:15Z","updated_at":"2016-08-09T18:03:29Z","closed_at":null,"body":"In Elasticsearch multi-fields can be defined. These fields are present in the index and can be queried against (just like `_all`) but are not present in the `_source`. \r\n\r\nHowever when in the Discover interface of Kibana, for example even though you can query against these fields in the search box at the top and they show up in the list of fields if you uncheck `Hide missing fields` it appears Kibana does not handle these properly.\r\n\r\nAs a user since I can query on them, I would expect to see them. See https://github.com/elastic/kibana/issues/1829 for original reference.\r\n\r\n<img width=\"314\" alt=\"screen shot 2016-06-10 at 10 44 07 am\" src=\"https://cloud.githubusercontent.com/assets/129643/15968053/57d45218-2ef8-11e6-9cce-2347997dfdec.png\">"},"comment":{"url":"https://api.github.com/repos/elastic/kibana/issues/comments/238638278","html_url":"https://github.com/elastic/kibana/issues/7419#issuecomment-238638278","issue_url":"https://api.github.com/repos/elastic/kibana/issues/7419","id":238638278,"user":{"login":"ppf2","id":7216393,"avatar_url":"https://avatars.githubusercontent.com/u/7216393?v=3","gravatar_id":"","url":"https://api.github.com/users/ppf2","html_url":"https://github.com/ppf2","followers_url":"https://api.github.com/users/ppf2/followers","following_url":"https://api.github.com/users/ppf2/following{/other_user}","gists_url":"https://api.github.com/users/ppf2/gists{/gist_id}","starred_url":"https://api.github.com/users/ppf2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ppf2/subscriptions","organizations_url":"https://api.github.com/users/ppf2/orgs","repos_url":"https://api.github.com/users/ppf2/repos","events_url":"https://api.github.com/users/ppf2/events{/privacy}","received_events_url":"https://api.github.com/users/ppf2/received_events","type":"User","site_admin":false},"created_at":"2016-08-09T18:03:29Z","updated_at":"2016-08-09T18:03:29Z","body":"Multifields is such a common use case though - Logstash generates them automatically for all string fields other than the message field *and* that it disables fielddata for all analyzed strings by default - see https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template-es2x.json.\r\n\r\nFor LS users, if someone wants to sort on application_name in the Discovery view, it will just throw an error now saying that application_name (which is a string analyzed field) cannot be sorted (even though there is an application_name.raw available in the index which is not_analyzed and using doc_values).  So with this limitation, it means that Logstash users by default cannot perform sorting in the Discover table on any string field.  "}}
{"actor":{"display_login":"ppf2"}}