{"push_id":1314087094,"size":2,"distinct_size":1,"ref":"refs/heads/5.0","head":"49e858d13350de36e2d262cfc99a8d70f042b895","before":"64ef508975c67b428787ad6efac09282c80a8494","commits":[{"sha":"1c53b0df04c69f459fd13f1bbc20881dc995a118","author":{"name":"Elastic Jasper","email":"3789c9bbedffd2191211a3300776c0a81698f1f8@users.noreply.github.com"},"message":"Backport PR #8421\n---------\n\n**Commit 1:**\nAdd field_capabilities API\n\nThis adds a simple API for getting the searchable/aggregatable status of\na list of fields in a given index, list of indices, or index pattern. In\nthe future this will probably evolve into a full blown fields info API\nthat we can use when removing the index pattern mapping cache. For now\nthough it's built to provide the minimum info needed to fix\nhttps://github.com/elastic/kibana/issues/6769\n\nUsage:\n\nThe API exposes a single GET endpoint.\n\n```\nGET /api/kibana/{indices}/field_capabilities\n```\n\n`indices` can be a single index, a comma delimited list, or a wildcard\npattern\n\nExample response:\n\n```\n{\n  \"fields\": {\n    \"imsearchable\": {\n      \"searchable\": true,\n      \"aggregatable\": false\n    },\n    \"imaggregatable\": {\n      \"searchable\": true,\n      \"aggregatable\": true\n    },\n  }\n}\n```\n\n* Original sha: 1af6b76bd4f790a02d1f211d57bb6585dd458584\n* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-09-21T18:38:34Z\n\n**Commit 2:**\nFilter non-aggregatable fields from vis editor UI\n\nUsing the field_capabilities API added in the previous commit, this commit enhances\nthe client side index pattern object with information about the\nsearchable and aggregatable status of each field in the index pattern.\nWe then use this information to filter out non-aggregatable fields from\nthe vis editor so that users won't accidentally select them and get\nnasty errors. An example of a non-aggregatable field would be a `text`\nfield without fielddata enabled (which is the default).\n\nI also added the searchable and aggregatable flags to the index pattern\npage so users can see the status of their fields. I removed the `indexed`\ncolumn because it was mostly redundant with `searchable` and I needed\nthe horizontal space.\n\nThe addition of the searchable and aggregatable properties for index\npattern fields would require users to manually refresh their field list\nwhen upgrading to 5.0. This commit also adds a check for those properties and\nif they're missing it automatically refreshes the field list for the\nuser in a seamless manner.\n\n* Original sha: 4a906f30c7d0450361ce5296d3ae7c2973f598c0\n* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-09-21T19:18:10Z","distinct":false,"url":"https://api.github.com/repos/elastic/kibana/commits/1c53b0df04c69f459fd13f1bbc20881dc995a118"},{"sha":"49e858d13350de36e2d262cfc99a8d70f042b895","author":{"name":"Matt Bargar","email":"31e7b35f7f9f5d76c1e2ef239c79b97264b2f6d0@devcorr.com"},"message":"Merge pull request #8462 from elastic/jasper/backport/8421/5.0\n\n[backport] PR #8421 to 5.0","distinct":true,"url":"https://api.github.com/repos/elastic/kibana/commits/49e858d13350de36e2d262cfc99a8d70f042b895"}]}
{"actor":{"display_login":"Bargs"}}