{"action":"closed","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/11151","labels_url":"https://api.github.com/repos/elastic/elasticsearch/issues/11151/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch/issues/11151/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch/issues/11151/events","html_url":"https://github.com/elastic/elasticsearch/issues/11151","id":76032353,"number":11151,"title":"multi_field \"default\" field not behaving as expected","user":{"login":"marshall007","id":877936,"avatar_url":"https://avatars.githubusercontent.com/u/877936?v=3","gravatar_id":"","url":"https://api.github.com/users/marshall007","html_url":"https://github.com/marshall007","followers_url":"https://api.github.com/users/marshall007/followers","following_url":"https://api.github.com/users/marshall007/following{/other_user}","gists_url":"https://api.github.com/users/marshall007/gists{/gist_id}","starred_url":"https://api.github.com/users/marshall007/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marshall007/subscriptions","organizations_url":"https://api.github.com/users/marshall007/orgs","repos_url":"https://api.github.com/users/marshall007/repos","events_url":"https://api.github.com/users/marshall007/events{/privacy}","received_events_url":"https://api.github.com/users/marshall007/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-05-13T15:48:42Z","updated_at":"2015-05-15T18:17:34Z","closed_at":"2015-05-15T18:17:33Z","body":"From the [Multi Field Type docs](http://www.elastic.co/guide/en/elasticsearch/reference/0.90/mapping-multi-field-type.html):\r\n\r\n> With `multi_field` mapping, the field that has the same name as the property is treated as if it was mapped without a multi field. That’s the \"default\" field. It can be accessed regularly, for example using name or using typed navigation `tweet.name`.\r\n\r\nThus, given the following mapping, I would expect that querying `test.name` would be equivalent to `test.name.name` but this does not appear to be the case.\r\n\r\n```json\r\n{\r\n  // ...\r\n  \"mappings\": {\r\n    \"test\": {\r\n      \"properties\": {\r\n        \"name\": {\r\n          \"type\": \"string\",\r\n          \"fields\": {\r\n            \"name\": {\r\n              \"analyzer\": \"full_name\",\r\n              \"type\": \"string\",\r\n              \"index\": \"analyzed\"\r\n            },\r\n            \"partial\": {\r\n              \"search_analyzer\": \"full_name\",\r\n              \"index_analyzer\": \"partial_name\",\r\n              \"type\": \"string\",\r\n              \"index\": \"analyzed\"\r\n            }\r\n          }\r\n        },\r\n        // ...\r\n      }\r\n    }\r\n  }\r\n}\r\n```\r\n\r\nI get different results from the following queries:\r\n\r\n```\r\nGET tests/_search\r\n{\r\n  \"query\": {\r\n    \"match\": {\r\n      \"name\": \"rett syndrome\"\r\n    }\r\n  }\r\n}\r\n\r\nGET tests/_search\r\n{\r\n  \"query\": {\r\n    \"match\": {\r\n      \"name.name\": \"rett syndrome\"\r\n    }\r\n  }\r\n}\r\n```"}}