{"push_id":711484096,"size":146,"distinct_size":3,"ref":"refs/heads/feature/renderTemplate","head":"9360e16afd42a649a8f7e27f7435f60cece29c08","before":"dc32dd0b2cb3c1ea7e6d975a72faca07ac473b63","commits":[{"sha":"1bfa722d436b52fb6223b0f3c0718bd7638ab2d6","author":{"email":"0b35fd4729a521ced70d3ea05bf74d1eb85c5108@gmail.com","name":"Adrien Grand"},"message":"Make sure messages are fully read even in case of EOS markers.\n\nWhen using compression over the network, you might sometimes see warnings that\nthe stream was not fully read. This is because DeflaterOutputStream adds an\nend-of-stream marker. When deserializing, we need to poll for one byte using\nInputStream.read() to make sure to decode this EOS marker.\n\nFor the record, it does not strike all the time today because we perform\nbuffering when decompressing to avoid performing too many JNI calls, but it\nis easy to make this warning happen all the time by decreasing the size of\nthe buffer we use.\n\nClose #11748","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/1bfa722d436b52fb6223b0f3c0718bd7638ab2d6"},{"sha":"38ceeb5c30f49767c6656b57a7bbb4e202d38b2e","author":{"email":"d38226a99278fb3742af2aa3c8d508fae49bb4b0@gmail.com","name":"Johannes Barthelmes"},"message":"Fix #11699\n\nAdd a null-check for XContentBuilder#field for BigDecimals","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/38ceeb5c30f49767c6656b57a7bbb4e202d38b2e"},{"sha":"8b60083dda0b8cbe9b35bdb074f9bb198013454b","author":{"email":"f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","name":"Simon Willnauer"},"message":"Add high-level javadocs to delete-by-query\n\nThis commit adds high-level javadocs to the delete-by-query explaining\nit's semantics and why it's moved to a plugin.\n\nCloses #11723","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/8b60083dda0b8cbe9b35bdb074f9bb198013454b"},{"sha":"88f8d58c8bec33494139a10c921afd55d3895d7c","author":{"email":"e46fc836cca3acec03944314d1457c2ae6c68ef3@reelsen.net","name":"Alexander Reelsen"},"message":"Cluster Health: Add max wait time for pending task and active shard percentage\n\nIn order to get a quick overview using by simply checking the cluster state\nand its corresponding cat API, the following two attributes have been added\nto the cluster health response:\n\n* task max waiting time, the time value of the first task of the\n  queue and how long it has been waiting\n* active shards percent: The percentage of the number of shards that are in\n  initializing state\n\nThis makes the cluster health API handy to check, when a fully restarted\ncluster is back up and running.\n\nCloses #10805","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/88f8d58c8bec33494139a10c921afd55d3895d7c"},{"sha":"55c55677a3422ca7ade3f1dbaf688b40b934382d","author":{"email":"07214fe5dc19164a587acf4cfa1dc6b83a5ba1eb@gmail.com","name":"Shay Banon"},"message":"Remove reroute with no reassign\nIts not used in our codebase anymore, so no need for it\ncloses #11804","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/55c55677a3422ca7ade3f1dbaf688b40b934382d"},{"sha":"1f3670733aa8378c6295dacacf99397d99a16fab","author":{"email":"f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","name":"Simon Willnauer"},"message":"Load percolator queries before shard is marked POST_RECOVERY\n\nIf we mark the shard as being in POST_RECOVERY before the percolator\nis fully set up we might expose it to the user as fully searchable before\nall queries are loaded. This can lead to wrong results especially in tests\nwhen a shard is concurrently marked as STARTED.\n\nThis commit also removes unneded abstractions on IndexShard where readoperations\nshould be allowed when the purose is a write.","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/1f3670733aa8378c6295dacacf99397d99a16fab"},{"sha":"eb23530e066f9239238f8ecd47d80ed00b92b7be","author":{"email":"e46fc836cca3acec03944314d1457c2ae6c68ef3@reelsen.net","name":"Alexander Reelsen"},"message":"Internal: Readd accidental removed functionality in InternalClusterService\n\nThe commit about adding cluster health response features also removed\naccidentally some functionality, that resulted in wrong instanceof checks\nin InternalClusterService and thus in test failures because the cluster\nstate task that was added via an anonymous was missing the cast.\n\nThis commit readds the abstract class with slight renaming.\n\nCommit id was: 88f8d58c8bec33494139a10c921afd55d3895d7c","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/eb23530e066f9239238f8ecd47d80ed00b92b7be"},{"sha":"5d94febcb15ba1c42b23a9709ef89a0cd30d0300","author":{"email":"ab3bb6d6e7000c4f1d71c63f7383af263d4c1b86@gmail.com","name":"Zachary Tong"},"message":"Aggregations: Moving average forecasts should not include current datapoint.\n\n- Fixes tests, and removes a few special snowflake, fragile tests.\n- Removes concrete implementation of predict() and moves it into\n  each model so that the logic is clearer.  Because there is some\n  shared checks/assertions, those remain in predict() and the main\n  prediction happens in doPredict()","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/5d94febcb15ba1c42b23a9709ef89a0cd30d0300"},{"sha":"2ebb44d56f2c61cb14afca1caea21a0ecd4130fb","author":{"email":"ab3bb6d6e7000c4f1d71c63f7383af263d4c1b86@gmail.com","name":"Zachary Tong"},"message":"Merge pull request #11641 from polyfractal/bugfix/movavg_predict\n\nAggregations: Moving average forecasts should not include current point","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/2ebb44d56f2c61cb14afca1caea21a0ecd4130fb"},{"sha":"12e7cbe92bcda9767538baee7e1ce1cd934797ed","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Mappings: Lockdown _timestamp\n\nThis is a follow up to #8143 and #6730 for _timestamp. It removes\nsupport for `path`, as well as any field type settings, and\nenables docvalues for _timestamp, for 2.0.  Users who need to\nadjust these settings can use a date field.","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/12e7cbe92bcda9767538baee7e1ce1cd934797ed"},{"sha":"2e07d0ba26c4cc1a3fc99243652d0a3d0187f1f8","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Merge pull request #11794 from rjernst/fix/lockdown-timestamp\n\nMappings: Lockdown _timestamp","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/2e07d0ba26c4cc1a3fc99243652d0a3d0187f1f8"},{"sha":"1df2d3015efee3e3d0df0696729c4e509363a5af","author":{"email":"992531bec19101e9308e69893b3169c39fdfdd41@gmail.com","name":"Boaz Leskes"},"message":"Add OS name to _nodes and _cluster/nodes\n\nwe currently don't expose this.\n\nThis adds the following to the OS section of `_nodes`:\n\n```\n\"os\": {\n     \"name\": \"Mac OS X\",\n     ...\n }\n ```\n\n and the following to the OS section of `_cluster/stats`:\n\n ```\n      \"os\": {\n         ...\n          \"names\": [\n             {\n                \"name\": \"Mac OS X\",\n                \"count\": 1\n             }\n          ],\n          ...\n       },\n ```\n\nCloses #11807","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/1df2d3015efee3e3d0df0696729c4e509363a5af"},{"sha":"adcc0683b8f1ca98dbaefe29ee3f181cd4c5d9e7","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Mappings: Restrict fields with the same name in different types to have the same core settings\n\nWe currently are very lax about allowing data types to conflict for the\nsame field name, across document types. This change makes the underlying\nmap in MapperService a 1-1 map of field name to field type, and throws\nexception when new types are not compatible.\n\nTo still allow changing a type, with parameters that are allowed to be\nchanged, but for a field that exists in multiple types, a new parameter\nto index creation and put mapping API is added: update_all_types.\nThis defaults to false, and the exception messages suggest using\nthis parameter when trying to modify a setting that is allowed to be\nmodified but is being limited by this restriction.\n\nThere are also a couple changes which try to base fields from new types\nfor dynamic mappings, and root mappers, on existing settings. For\ndynamic mappings this is important if the dynamic defaults have been\nchanged. For root mappings, this is mostly just for backcompat when\npre 2.0 root mappers could have their field type changed.\n\nfixes #8871","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/adcc0683b8f1ca98dbaefe29ee3f181cd4c5d9e7"},{"sha":"00bcce79f7c40ab9ceb6fd98eff413bde3c74696","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Simplify root mapper builder creation","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/00bcce79f7c40ab9ceb6fd98eff413bde3c74696"},{"sha":"f123a53d7258349a171e47a35f4581899d8fa776","author":{"email":"1e115feeab9474b9d680e5528024201af6e7722f@traveljury.com","name":"Clinton Gormley"},"message":"Docs: Refactored modules and index modules sections","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/f123a53d7258349a171e47a35f4581899d8fa776"},{"sha":"81d66d8ef373a176dbc353735fd9d6e73f064d06","author":{"email":"1e115feeab9474b9d680e5528024201af6e7722f@traveljury.com","name":"Clinton Gormley"},"message":"Docs: Fixed bad link","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/81d66d8ef373a176dbc353735fd9d6e73f064d06"},{"sha":"b89bd99cd19ce28120c704ca8c791f94bd4f50f7","author":{"email":"1e115feeab9474b9d680e5528024201af6e7722f@traveljury.com","name":"Clinton Gormley"},"message":"Refixed bad link","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/b89bd99cd19ce28120c704ca8c791f94bd4f50f7"},{"sha":"d32443bfb5fbf14ec51aeda8ace473f9905a5760","author":{"email":"78b6854e22ab09d4ae3dac29b92052963103b33e@motovs.org","name":"Igor Motov"},"message":"Docs: add description of the analyze_wildcard parameter to the simple query string query docs","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/d32443bfb5fbf14ec51aeda8ace473f9905a5760"},{"sha":"e7702468a21a546da0dc488497bdaa75d444b3cc","author":{"email":"b94c0cfa21109a77b1c218c0761b0bfc6299786a@gmail.com","name":"javanna"},"message":"Java api: add missing boost support to GeoShapeQueryBuilder\n\nRelates to #11744\nRelates to #11810","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/e7702468a21a546da0dc488497bdaa75d444b3cc"},{"sha":"90a7b4868e1b16a682a9dc5e36d093b3d3aa0ef6","author":{"email":"b94c0cfa21109a77b1c218c0761b0bfc6299786a@gmail.com","name":"javanna"},"message":"Java api: add missing boost support to TermsQueryBuilder\n\nRelates to #11744\nCloses #11810","distinct":false,"url":"https://api.github.com/repos/colings86/elasticsearch/commits/90a7b4868e1b16a682a9dc5e36d093b3d3aa0ef6"}]}