{"push_id":1467753254,"size":37,"distinct_size":37,"ref":"refs/heads/strict-booleans","head":"cbb3822c1b0ca8d81875a663e7e2821723b73a88","before":"db3fd5ee204b33856a95d188c35d362a9a2d54e2","commits":[{"sha":"318ce6ab16635392b6c0f17e7b54015b85eaf1d3","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"fix bug: https://github.com/elastic/elasticsearch/issues/21710","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/318ce6ab16635392b6c0f17e7b54015b85eaf1d3"},{"sha":"46cdb411b53cac6f35455e45623015b2f2bd4e0c","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"modified code according to nik9000's comments.","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/46cdb411b53cac6f35455e45623015b2f2bd4e0c"},{"sha":"ce0ad4e08e93cc4dc1b08f51960aee7e2f0000f3","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"add test case for parse include_in_all in mulit fields","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/ce0ad4e08e93cc4dc1b08f51960aee7e2f0000f3"},{"sha":"4c79f36abb706a77312f07bb7236e501ff970f49","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"1. add license declaration in class header\n2. remove Created by declaration\n3. fix typo method name from testExceptionForCopyToInMultiFields to testExceptionForIncludeInAllInMultiFields\n4. fix typo method name from createMappinmgWithIncludeInAllInMultiField to createMappingWithIncludeInAllInMultiField\n5. use expectThrows rather than try catch according to nik9000's comments","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/4c79f36abb706a77312f07bb7236e501ff970f49"},{"sha":"b857b316b658f93a626cf91b0f6e044f5d3445a6","author":{"name":"Boaz Leskes","email":"daaa071c1d6d35b7f0b1ebbbcc270afab5432337@gmail.com"},"message":"Add BWC layer to seq no infra and enable BWC tests (#22185)\n\nSequence BWC logic consists of two elements:\r\n\r\n1) Wire level BWC using stream versions.\r\n2) A changed to the global checkpoint maintenance semantics.\r\n\r\nFor the sequence number infra to work with a mixed version clusters, we have to consider situation where the primary is on an old node and replicas are on new ones (i.e., the replicas will receive operations without seq#) and also the reverse (i.e., the primary sends operations to a replica but the replica can't process the seq# and respond with local checkpoint). An new primary with an old replica is a rare because we do not allow a replica to recover from a new primary. However, it can occur if the old primary failed and a new replica was promoted or during primary relocation where the source primary is treated as a replica until the master starts the target.\r\n\r\n1) Old Primary & New Replica - this case is easy as is taken care of by the wire level BWC. All incoming requests will have their seq# set to `UNASSIGNED_SEQ_NO`, which doesn't confuse the local checkpoint logic (keeping it at `NO_OPS_PERFORMED`) \r\n2) New Primary & Old replica - this one is trickier as the global checkpoint service currently takes all in sync replicas into consideration for the global checkpoint calculation. In order to deal with old replicas, we change the semantics to say all *new node* in sync replicas. That means the replicas on old nodes don't count for the global checkpointing. In this state the seq# infra is not fully operational (you can't search on it, because copies may miss it) but it is maintained on shards that can support it. The old replicas will have to go through a file based recovery at some point and will get the seq# information at that point. There is still an edge case where a new primary fails and an old replica takes over. I'lll discuss this one with @ywelsch as I prefer to avoid it completely.\r\n\r\nThis PR also re-enables the BWC tests which were disabled. As such it had to fix any BWC issue that had crept in. Most notably an issue with the removal of the `timestamp` field in #21670.\r\n\r\nThe commit also includes a fix for the default value of the seq number field in replicated write requests (it was 0 but should be -2), that surface some other minor bugs which are fixed as well.\r\n\r\nLast - I added some debugging tools like more sane node names and forcing replication request to implement a `toString`","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/b857b316b658f93a626cf91b0f6e044f5d3445a6"},{"sha":"b2e93d28707521667a4fd9dd9cea2e73fa604c8e","author":{"name":"Adrien Grand","email":"83387f1adf6f01406cba47ad9f87966de8fe24be@gmail.com"},"message":"Be explicit about the fact backslashes need to be escaped. (#22257)\n\nRelates #22255","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/b2e93d28707521667a4fd9dd9cea2e73fa604c8e"},{"sha":"1cabf66bd50004255a4fc727ce3437fa80f3f87d","author":{"name":"Yannick Welsch","email":"4642e729622b34408794d8a9ed687701b7880d3c@welsch.lu"},"message":"Use correct block levels for TRA subclasses (#22224)\n\nSubclasses of TransportReplicationAction can currently chose to implement block levels for which the request will be blocked.\r\n- Refresh/Flush was using the block level METADATA_WRITE although they don't operate at the cluster meta data level (but more like shard level meta data which is not represented in the block levels). Their level has been changed to null so that they can operate freely in the presence of blocks.\r\n- GlobChkptSync was using WRITE although it does not make any changes to the actual documents of a shard. The level has been changed to null so that it can operate freely in the presence of blocks.\r\nThe commit also adds a check for closed indices in TRA so that the right exception is thrown if refresh/flush/checkpoint syncing is attempted on a closed index (before it was throwing an IndexNotFoundException, now it's throwing IndexClosedException).","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/1cabf66bd50004255a4fc727ce3437fa80f3f87d"},{"sha":"63af03a1042a6ae1ed333aaabcd9cfc3a9fc3fec","author":{"name":"Yannick Welsch","email":"4642e729622b34408794d8a9ed687701b7880d3c@welsch.lu"},"message":"Atomic mapping updates across types (#22220)\n\nThis commit makes mapping updates atomic when multiple types in an index are updated. Mappings for an index are now applied in a single atomic operation, which also allows to optimize some of the cross-type updates and checks.","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/63af03a1042a6ae1ed333aaabcd9cfc3a9fc3fec"},{"sha":"5bec4f80244b342f7fb61726bd149cbbeac0433d","author":{"name":"Nik Everett","email":"8f968e953049b60f3547bb43375dfdb757e1c88c@gmail.com"},"message":"Unescape \\\\r in stash dump\n\nOh windows.....\n\nRelates to #22195","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/5bec4f80244b342f7fb61726bd149cbbeac0433d"},{"sha":"3421e54a420f9aa506b44cff628b23e15501f806","author":{"name":"Luca Cavanna","email":"fcdf11cc3de751e1fde3dc9c882ec9c523a33c97@users.noreply.github.com"},"message":"Add fromXContent method to GetResponse (#22082)\n\nMoved field values `toXContent` logic to `GetField` (from `GetResult`), which outputs its own fields, and can also parse them now. Also added `fromXContent` to `GetResult` and `GetResponse`.\r\n\r\n The start object and end object for `GetResponse` output have been moved to `GetResult#toXContent`, from the corresponding rest action. This makes it possible to have `toXContent` and `fromXContent` completely symmetric, as parsing requires looping till an end object is found which is weird when the corresponding `toXContent` doesn't print that out.\r\n\r\nThis also introduces the foundation for testing retrieval of _source and stored field values.","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/3421e54a420f9aa506b44cff628b23e15501f806"},{"sha":"87d8764a324e818663d45cce6b0dbbef2673f8cb","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"[TEST] add unit test for XContentHelper#toXContent method","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/87d8764a324e818663d45cce6b0dbbef2673f8cb"},{"sha":"2d71ced2213ec2aadffd762cd00f7b9f1caa8474","author":{"name":"Nik Everett","email":"8f968e953049b60f3547bb43375dfdb757e1c88c@gmail.com"},"message":"Properly fail reindex-from-remote if can't detect content type","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/2d71ced2213ec2aadffd762cd00f7b9f1caa8474"},{"sha":"04d929ff53990dce7baf815a7f0609f890658186","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"add inline comments on GetField binary values parsing","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/04d929ff53990dce7baf815a7f0609f890658186"},{"sha":"38914f17edff05801ccda1f818bf7fef0cd33896","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"[TEST] improve ElasticsearchAssertions#assertEquivalent for ToXContent\n\nRename the method to assertToXContentEquivalent to highlight that it's tailored to ToXContent comparisons.\n\nRather than parsing into a map and replacing byte[] in both those maps, add custom equality assertions that recursively walk maps and lists and call Arrays.equals whenever a byte[] is encountered.","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/38914f17edff05801ccda1f818bf7fef0cd33896"},{"sha":"6a27628f129773da5bad65a99b7394273e632198","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"Remove support for strict parsing mode\n\nWe return deprecation warnings as response headers, besides logging them. Strict parsing mode stayed around, but was only used in query tests, though we also introduced checks for deprecation warnings there that don't need strict parsing anymore (see #20993).\n\n We can then safely remove support for strict parsing mode. The final goal is to remove the ParseFieldMatcher class, but there are many many users of it. This commit prepares the field for the removal, by deprecating ParseFieldMatcher and making it effectively not needed. Strict parsing is removed from ParseFieldMatcher, and strict parsing is replaced in tests where needed with deprecation warnings checks.\n\n Note that the setting to enable strict parsing was never ported to the new settings infra hance it cannot be set in production. It is really only used in our own tests.\n\n Relates to #19552","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/6a27628f129773da5bad65a99b7394273e632198"},{"sha":"5dae10db117d224658d658ce95b81cb5e54258a4","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"[TEST] add warnings check to ESTestCase\n\nWe are currenlty checking that no deprecation warnings are emitted in our query tests. That can be moved to ESTestCase (disabled in ESIntegTestCase) as it allows us to easily catch where our tests use deprecated features and assert on the expected warnings.","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/5dae10db117d224658d658ce95b81cb5e54258a4"},{"sha":"f6b6e4e376bfe0aa7c4d7cc51d6afdd407cebccf","author":{"name":"Grzegorz Gajos","email":"f7ccb337eada8e61c73d3c412474d09b3fac1ccd@gmail.com"},"message":"Added ability to remove pipelines via wildcards (#22149) (#22191)\n\nThis commit is adding an ability to remove pipelines with wildcards.","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/f6b6e4e376bfe0aa7c4d7cc51d6afdd407cebccf"},{"sha":"2e1d152fc0b50633e832b8785d961325e480b54e","author":{"name":"Nik Everett","email":"8f968e953049b60f3547bb43375dfdb757e1c88c@gmail.com"},"message":"Sub-fields should not accept `include_in_all` parameter (#21971)\n\nFail to update mapping when multifield has `include_in_all`.\r\n\r\nCloses #21710","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/2e1d152fc0b50633e832b8785d961325e480b54e"},{"sha":"40b80ae10460567144bbb0d8dcb606d4a10418ac","author":{"name":"Nik Everett","email":"8f968e953049b60f3547bb43375dfdb757e1c88c@gmail.com"},"message":"Fix line length","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/40b80ae10460567144bbb0d8dcb606d4a10418ac"},{"sha":"0ab3cbe3a3b15a154c79138c6d0e6f8dfa888876","author":{"name":"Alexander Lin","email":"017b46951195d4e1c8ee98978867202132676964@gmail.com"},"message":"Adds percent-encoding for Location headers (#21057)\n\nThis should cause unicode elements in the location header to be percent-encoded, instead of being left alone.\r\n\r\nCloses #21016","distinct":true,"url":"https://api.github.com/repos/danielmitterdorfer/elasticsearch/commits/0ab3cbe3a3b15a154c79138c6d0e6f8dfa888876"}]}
{"actor":{"display_login":"danielmitterdorfer"}}