{"push_id":2718708650,"size":41,"distinct_size":6,"ref":"refs/heads/dry-up-painless-script-engine","head":"b80bb979c924c3c624367e3ef1c0d38beef7443a","before":"f2a95c57ddfcf1647bed26a2ef741cc2bca35408","commits":[{"sha":"ae5c70e6037ed2b7f27b231177990cd590690d30","author":{"name":"Martijn van Groningen","email":"4bbd6538573d69157ec8155ac2937b38e64a59f4@gmail.com"},"message":"muted tests due to #31940","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/ae5c70e6037ed2b7f27b231177990cd590690d30"},{"sha":"e3707efe740356f1c5c38d71e0d98b80291f00ab","author":{"name":"Alexander Reelsen","email":"e46fc836cca3acec03944314d1457c2ae6c68ef3@reelsen.net"},"message":"Tests: Mute SearchFieldsIT.testDocValueFields()\n\nRelates #31992","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/e3707efe740356f1c5c38d71e0d98b80291f00ab"},{"sha":"2cfe703299a9955c6eef8a1d38774c9fc63f9dc0","author":{"name":"Dimitris Athanasiou","email":"e8f1ad116483bc79a2a9b237334769e79f91ffb6@elastic.co"},"message":"[ML] Ensure immutability of MlMetadata (#31957)\n\nThe test failure in #31916 revealed that updating\r\nrules on a job was modifying the detectors list\r\nin-place. That meant the old cluster state and the\r\nupdated cluster state had no difference and thus the\r\nchange was not propagated to non-master nodes.\r\n\r\nThis commit fixes that and also reviews all of ML\r\nmetadata in order to ensure immutability.\r\n\r\nCloses #31916","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/2cfe703299a9955c6eef8a1d38774c9fc63f9dc0"},{"sha":"edf83c1d87951e350be26ce86764ef783f80ab8a","author":{"name":"Andrei Stefan","email":"b7173f824f036ebf5de1f548643e696597d47c25@users.noreply.github.com"},"message":"SQL: Add support for single parameter text manipulating functions (#31874)\n\nAdded support for ASCII, BIT_LENGTH, CHAR, CHAR_LENGTH, LCASE, LENGTH, LTRIM, RTRIM, SPACE, UCASE functions.\r\nWherever Painless scripting is necessary (WHERE conditions, ORDER BY etc), those scripts are being used.","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/edf83c1d87951e350be26ce86764ef783f80ab8a"},{"sha":"6fcd606536d88b1365fb3870380514f91610519b","author":{"name":"David Kyle","email":"dbae93ae58290c477ca495305491bd57429018d8@elastic.co"},"message":"[ML] Get ForecastRequestStats doc in RestoreModelSnapshotIT (#31973)","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/6fcd606536d88b1365fb3870380514f91610519b"},{"sha":"4ae4ac08d55d831b9e3651f2ef646a45765ceaa1","author":{"name":"Christoph Büscher","email":"e94fcfcfda62411722b8e83e850b947a59336941@posteo.de"},"message":"Add Expected Reciprocal Rank metric (#31891)\n\nThis change adds Expected Reciprocal Rank (ERR) as a ranking evaluation metric\r\nas descriped in:\r\n\r\nChapelle, O., Metlzer, D., Zhang, Y., & Grinspan, P. (2009).\r\nExpected reciprocal rank for graded relevance.\r\nProceeding of the 18th ACM Conference on Information and Knowledge Management.\r\nhttps://doi.org/10.1145/1645953.1646033\r\n\r\nERR is an extension of the classical reciprocal rank to the graded relevance\r\ncase and assumes a cascade browsing model. It quantifies the usefulness of a\r\ndocument at rank `i` conditioned on the degree of relevance of the items at ranks\r\nless than `i`. ERR seems to be gain traction as an alternative to (n)DCG, so it\r\nseems like a good metric to support. Also ERR seems to be the default optimization\r\nmetric used for training in RankLib, a widely used learning to rank library.\r\n\r\nRelates to #29653","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/4ae4ac08d55d831b9e3651f2ef646a45765ceaa1"},{"sha":"0b7e7befdd304a35437f9ad5f1f62a1088d85000","author":{"name":"Alexander Reelsen","email":"e46fc836cca3acec03944314d1457c2ae6c68ef3@reelsen.net"},"message":"Tests: Fix SearchFieldsIT.testDocValueFields (#31995)\n\nThis test produced different implementations of joda time classes,\r\ndepending on if the data was serialized or not (DateTime vs\r\nMutableDateTime). This now uses a common base class to extract the\r\nmilliseconds from the data.\r\n\r\nCloses #31992","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/0b7e7befdd304a35437f9ad5f1f62a1088d85000"},{"sha":"043e40addedc8dc0b3919ee2c19a9160b3a6332e","author":{"name":"Christoph Büscher","email":"e94fcfcfda62411722b8e83e850b947a59336941@posteo.de"},"message":"Fix unreachable error condition in AmazonS3Fixture (#32005)\n\nThe `else` branch where currently the error response should be thrown is not\r\nreachable because `handler` is always non-null inside the previous outer check.\r\nMoving error creation into an else branch on the other condition check, removing\r\nthe other superflous check for non-null handler inside the first branch.","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/043e40addedc8dc0b3919ee2c19a9160b3a6332e"},{"sha":"44f280fc8938039bee949bef01c16c922f1f594f","author":{"name":"Igor Motov","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@motovs.org"},"message":"Force execution of fetch tasks (#31974)\n\nForces fetch tasks to queue even in the event that the queue is\r\nalready full. The reasoning is that fetch tasks may only be follow-up\r\nto query tasks, so the number of additional fetch tasks that may enter\r\nthe threadpool is expected to be reasonable.\r\n\r\nCloses #29442","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/44f280fc8938039bee949bef01c16c922f1f594f"},{"sha":"334c2555162910f3ffa5dcb3ed1c4c8f9940cd84","author":{"name":"olcbean","email":"d965b7d9fe5caffaf943eca3c4154623690a66dc@yahoo.com"},"message":"XContentTests : Insert random fields at random positions (#30867)\n\nCurrently AbstractXContentTestCase#testFromXContent appends random fields, but in\r\na fixed position. This PR shuffles all fields after the random fields have been appended, \r\nhence the random fields are actually added to random positions.","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/334c2555162910f3ffa5dcb3ed1c4c8f9940cd84"},{"sha":"c375d5ab23db63c457013c2851e915ed1043c44c","author":{"name":"Tim Brooks","email":"5ee0edb9e2229c0838f1959779f1949031de0123@uncontended.net"},"message":"Add nio transport to security plugin (#31942)\n\nThis is related to #27260. It adds the SecurityNioTransport to the\r\nsecurity plugin. Additionally, it adds support for ip filtering. And it\r\nrandomly uses the nio transport in security integration tests.","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/c375d5ab23db63c457013c2851e915ed1043c44c"},{"sha":"30d6fd3ca74c44de27f8314fe7c070ac1d23819a","author":{"name":"Andy Bristol","email":"6e4a57f298cab7a7b5716cb4d858136c8d9d46a2@elastic.co"},"message":"[test] disable packaging tests for suse boxes\n\nFor #30295","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/30d6fd3ca74c44de27f8314fe7c070ac1d23819a"},{"sha":"de2eb85aaf1448ebeac680de830db8c504048a00","author":{"name":"Tom Veasey","email":"2262c8a57e3e20eae031f2724e787421804f824b@users.noreply.github.com"},"message":"[ML] Re-enable memory limit integration tests (#31328)","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/de2eb85aaf1448ebeac680de830db8c504048a00"},{"sha":"9822a6f911cba6e00a8828432e2094e289935435","author":{"name":"Nik Everett","email":"cd30b83b3787c52251dabc7000a4f9dfbe1c5f24@gmail.com"},"message":"Docs: Explain closing the high level client\n\nIt looks like we weren't clear on when and why you should close the high\nlevel client and folks were closing it after every request which is not\nefficient. This explains why you should close the client and when so\nthis shouldn't be as common.\n\nCloses #32001","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/9822a6f911cba6e00a8828432e2094e289935435"},{"sha":"332c134517bdcf11acd74c205482245c692186fb","author":{"name":"Christoph Büscher","email":"e94fcfcfda62411722b8e83e850b947a59336941@posteo.de"},"message":"[TEST] Mute SlackMessageTests.testTemplateRender","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/332c134517bdcf11acd74c205482245c692186fb"},{"sha":"c662565f291db3c7e95f9cfa75e764999cd1bbfb","author":{"name":"Tim Vernum","email":"5ee0edb9e2229c0838f1959779f1949031de0123@adjective.org"},"message":"Access SSL contexts using names instead of Settings (#30953)\n\nHistorically we have loaded SSL objects (such as SSLContext,\r\nSSLIOSessionStrategy) by passing in the SSL settings, constructing a\r\nnew SSL configuration from those settings and then looking for a\r\ncached object that matches those settings.\r\n\r\nThe primary issue with this approach is that it requires a fully\r\nconfigured Settings object to be available any time the SSL context\r\nneeds to be loaded. If the Settings include SecureSettings (such as\r\npasswords for keys or keystores) then this is not true, and the cached\r\nSSL object cannot be loaded at runtime.\r\n\r\nThis commit introduces an alternative approach of naming every cached\r\nssl configuration, so that it is possible to load the SSL context for\r\na named configuration (such as \"xpack.http.ssl\"). This means that the\r\ncalling code does not need to have ongoing access to the secure\r\nsettings that were used to load the configuration.\r\n\r\nThis change also allows monitoring exporters to use SSL passwords\r\nfrom secure settings, however an exporter that uses a secure SSL setting\r\n(e.g. truststore.secure_password) may not have its SSL settings updated\r\ndynamically (this is prevented by a settings validator).\r\nExporters without secure settings can continue to be defined and updated\r\ndynamically.","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/c662565f291db3c7e95f9cfa75e764999cd1bbfb"},{"sha":"d2461643cdfc147d78a2c78164bd96033e918340","author":{"name":"David Roberts","email":"78a0de84f73f75a59acf5b635cb4b514ff6819d2@elastic.co"},"message":"[ML] Move open job failure explanation out of root cause (#31925)\n\nWhen an ML job cannot be allocated to a node the exception\r\ncontained an explanation of why the job couldn't be\r\nallocated to each node in the cluster.  For large clusters\r\nthis was not particularly easy to read and made the error\r\ndisplayed in the UI look very scary.\r\n\r\nThis commit changes the structure of the error to an outer\r\nElasticsearchException with a high level message and an\r\ninner IllegalStateException containing the detailed\r\nexplanation.  Because the definition of root cause is the\r\ninnermost ElasticsearchException the detailed explanation\r\nwill not be the root cause (which is what Kibana displays).\r\n\r\nFixes #29950","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/d2461643cdfc147d78a2c78164bd96033e918340"},{"sha":"f174f72fee0c38ab078641b097e4745c7899eb46","author":{"name":"Daniel Mitterdorfer","email":"6af016838da1f0f82b254730ffc3ce721afe497e@gmail.com"},"message":"Circuit-break based on real memory usage\n\nWith this commit we introduce a new circuit-breaking strategy to the parent\r\ncircuit breaker. Contrary to the current implementation which only accounts for\r\nmemory reserved via child circuit breakers, the new strategy measures real heap\r\nmemory usage at the time of reservation. This allows us to be much more\r\naggressive with the circuit breaker limit so we bump it to 95% by default. The\r\nnew strategy is turned on by default and can be controlled  with the new cluster\r\nsetting `indices.breaker.total.userealmemory`.\r\n\r\nNote that we turn it off for all integration tests with an internal test cluster\r\nbecause it leads to spurious test failures which are of no value (we cannot\r\nfully control heap memory usage in tests). All REST tests, however, will make\r\nuse of the real memory circuit breaker.\r\n\r\nRelates #31767","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/f174f72fee0c38ab078641b097e4745c7899eb46"},{"sha":"23198ea5512891c86e422c69e45970e357c9fade","author":{"name":"Alpar Torok","email":"ea81b2e7d913dc7dae901781766a687b3bfb664b@gmail.com"},"message":"Convert Version to Java - clusterformation part1 (#32009)\n\nImplement buildSrc Version in java\r\n\r\n- This allows to move all  all .java files from .groovy.\r\n- Will prevent eclipse from tangling up in this setup\r\n- make it possible to use Version from Java","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/23198ea5512891c86e422c69e45970e357c9fade"},{"sha":"69c2b2d8027a2c3c07d33316184db07c611df2e9","author":{"name":"Christoph Büscher","email":"e94fcfcfda62411722b8e83e850b947a59336941@posteo.de"},"message":"[Tests] Mute failing SearchDocumentationIT#testSearchRequestAggregations","distinct":false,"url":"https://api.github.com/repos/original-brownbear/elasticsearch/commits/69c2b2d8027a2c3c07d33316184db07c611df2e9"}]}
{"actor":{"display_login":"original-brownbear"}}