{"action":"opened","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/17660","repository_url":"https://api.github.com/repos/elastic/elasticsearch","labels_url":"https://api.github.com/repos/elastic/elasticsearch/issues/17660/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch/issues/17660/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch/issues/17660/events","html_url":"https://github.com/elastic/elasticsearch/issues/17660","id":147529587,"number":17660,"title":"Nested field does not allow a Multifield definition ","user":{"login":"miskander","id":508203,"avatar_url":"https://avatars.githubusercontent.com/u/508203?v=3","gravatar_id":"","url":"https://api.github.com/users/miskander","html_url":"https://github.com/miskander","followers_url":"https://api.github.com/users/miskander/followers","following_url":"https://api.github.com/users/miskander/following{/other_user}","gists_url":"https://api.github.com/users/miskander/gists{/gist_id}","starred_url":"https://api.github.com/users/miskander/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/miskander/subscriptions","organizations_url":"https://api.github.com/users/miskander/orgs","repos_url":"https://api.github.com/users/miskander/repos","events_url":"https://api.github.com/users/miskander/events{/privacy}","received_events_url":"https://api.github.com/users/miskander/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-11T19:30:55Z","updated_at":"2016-04-11T19:30:55Z","closed_at":null,"body":"**Elasticsearch version**: 2.3.1\r\n\r\n**JVM version**: Java(TM) SE Runtime Environment (build 1.8.0_31-b13)\r\n\r\n**OS version**: Mac 10.11.3\r\n\r\n**Description of the problem including expected versus actual behavior**:\r\nMappings of a field in an object doesn't respect multi-field definition. This behavior worked until 1.4.5 but the mappings were defined with the field dot notations. \r\n\r\ncreate an index with the following mappings (assume case_insensitive_sort is defined):\r\n```\r\n{\r\n\t\"my_type\": {\r\n\t\t\"properties\": {\r\n\t\t\t\"object_field\": {\r\n\t\t\t\t\"properties\": {\r\n\t\t\t\t\t\"name\": {\r\n\t\t\t\t\t\t\"type\": \"string\",\r\n\t\t\t\t\t\t\"fields\": {\r\n\t\t\t\t\t\t\t\"lower_case_sort\": {\r\n\t\t\t\t\t\t\t\t\"type\": \"string\",\r\n\t\t\t\t\t\t\t\t\"analyzer\": \"case_insensitive_sort\"\r\n\t\t\t\t\t\t\t}\r\n\t\t\t\t\t\t}\r\n\t\t\t\t\t}\r\n\t\t\t\t}\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\nThe mappings after the data is indexed does not show `lower_case_sort` field and it is not available at query time. Response when inspecting the mappings of the index:\r\n```\r\n\"browse_bits\": {\r\n\t\"properties\": {\t\t\r\n\t\t\"name\": {\r\n\t\t\t\"type\": \"string\"\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n**Steps to reproduce**:\r\n 1. Index a document specifying the mappings indicated above\r\n 2. Inspect mappings after indexing a document, the nested field is not respected.\r\n"}}