{"push_id":684946287,"size":20,"distinct_size":1,"ref":"refs/heads/feature/query-refactoring","head":"313e9c67697a8c6f0b332e2005a39cf69f68c3df","before":"b1f6d1abd65735f6abee642212bb4b4569fe1aca","commits":[{"sha":"1f2c42fd0be06e7a7ab9cf2c5e70d82988a11856","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Mappings: Refactor core index/query time properties into FieldType\n\nMappers are currently used at both index and query time for deciding\nhow to \"use\" a field.  For #8871, we need the index wide view of\nmappings to have a unified set of settings for each field of a given\nname within the index.\n\nThis change moves all the current settings (and methods defining\nquery time behavior) into subclasses of FieldType. In a future\nPR, this will allow storing the field type at the index level,\ninstead of mappers (which can still have settings that differ\nper document type).\n\nThe change is quite large (I'm sorry). I could not see a way to\nmigrate to this in a more piecemeal way. I did leave out cutting\nover callers of the query methods to using the field type, as\nthat can be done in a follow up.","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/1f2c42fd0be06e7a7ab9cf2c5e70d82988a11856"},{"sha":"b625ddd17f933d81510f32fc4f642da9c6c28e5c","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Merge branch 'master' into pr/fieldtype-mapper-split","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/b625ddd17f933d81510f32fc4f642da9c6c28e5c"},{"sha":"6598d82ae8f1ce36991ddc7af2a7e53a3f1a8541","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"fix bad merge for parent field mapper, and change most field types to be\npkg-private and final","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/6598d82ae8f1ce36991ddc7af2a7e53a3f1a8541"},{"sha":"a3f51544d51f8fc88595d40432e7bccb08a62930","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Merge pull request #11422 from rjernst/pr/fieldtype-mapper-split\n\nMappings: Refactor core index/query time properties into FieldType","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/a3f51544d51f8fc88595d40432e7bccb08a62930"},{"sha":"a805cef045eca2ad0bdcf28b50105e01697bdf48","author":{"email":"b8d3f9a31e790918c9363385aecaff2936991009@gmail.com","name":"Tanguy Leroux"},"message":"Bulk: allow null values in action/metadata line parameters\n\nCloses #11458","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/a805cef045eca2ad0bdcf28b50105e01697bdf48"},{"sha":"5fd96d9371f68645ac6ec2ec17c0faeaa21610a8","author":{"email":"cdedbaf433217656e9df940dd535438abed9f74c@writequit.org","name":"Lee Hinman"},"message":"[DOCS] Document the `index.shared_filesystem.recover_on_any_node` setting\n\nRelates to #10960\nCloses #11047","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/5fd96d9371f68645ac6ec2ec17c0faeaa21610a8"},{"sha":"0f207bf4fb85725e0c3893b1232675d79ada83ed","author":{"email":"f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","name":"Simon Willnauer"},"message":"Cleanup DeleteByQuery code from IndexShard","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/0f207bf4fb85725e0c3893b1232675d79ada83ed"},{"sha":"01e8eaf181148d1ae5239800b5d71bd38c0c2896","author":{"email":"e46fc836cca3acec03944314d1457c2ae6c68ef3@reelsen.net","name":"Alexander Reelsen"},"message":"Date Parsing: Add parsing for epoch and epoch in milliseconds\n\nThis commit changes the date handling. First and foremost Elasticsearch\ndoes not try to convert every date to a unix timestamp first and then\nuses the configured date. This now allows for dates like `2015121212` to\nbe parsed correctly.\n\nInstead it is now explicit by adding a `epoch_second` and `epoch_millis`\ndate format. This also means, that the default date format now is\n`epoch_millis||dateOptionalTime` to remain backwards compatible.\n\nCloses #5328\nRelates #10971","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/01e8eaf181148d1ae5239800b5d71bd38c0c2896"},{"sha":"b3779a03fcee69ceb794c8d4b88331fe77d49f4c","author":{"email":"e46fc836cca3acec03944314d1457c2ae6c68ef3@reelsen.net","name":"Alexander Reelsen"},"message":"Test: Fix search query tests to use correct date, mark one test as awaitsfix","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/b3779a03fcee69ceb794c8d4b88331fe77d49f4c"},{"sha":"aa248990bb4c54466a3dc16b6ea16f4cf0c6b81e","author":{"email":"69d448d1f653a116556c7279810bf60a3ebff907@elasticsearch.com","name":"Simon Willnauer"},"message":"Merge pull request #11468 from s1monw/cleanup_delete_by_query\n\nCleanup DeleteByQuery code from IndexShard","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/aa248990bb4c54466a3dc16b6ea16f4cf0c6b81e"},{"sha":"7264fd4eb810c514e80ee7b5e5dfd1c8f95e5d26","author":{"email":"f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","name":"Simon Willnauer"},"message":"Fix possible BWC break after upgrading from pre 1.0.0\n\nThis is happening because of #4074 when we required that the top-level \"query\" is present to delete-by-query requests, but prior to that we required that it is not present. So the translog has a DBQ without \"query\" and when we try to parse it we hit this exception.\n\nThis commit adds special handling for pre 1.0.0 indices if we hit parse exception, we\ntry to reparse without a top-level query object to be BWC compatible for these indices.\n\nCloses #10262\n\nConflicts:\n\tsrc/main/java/org/elasticsearch/index/shard/IndexShard.java\n\tsrc/test/java/org/elasticsearch/index/shard/IndexShardTests.java","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/7264fd4eb810c514e80ee7b5e5dfd1c8f95e5d26"},{"sha":"d621b160e9b940add546a6234bc2d17381334f33","author":{"email":"f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","name":"Simon Willnauer"},"message":"Use the smallest version rather than the default version\n\nThe minimum version comparison was always using the default version\nsicne the comparison was flipped.\n\nCloses #11474","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/d621b160e9b940add546a6234bc2d17381334f33"},{"sha":"f0e6addc53bdd82dd55bab96f024012a7ba8456c","author":{"email":"78b6854e22ab09d4ae3dac29b92052963103b33e@motovs.org","name":"Igor Motov"},"message":"Snapshot/Restore: sync up snapshot shard status on a master restart\n\nWhen a snapshot operation on a particular shard finishes, the data node where this shard resides sends an update shard status request to the master node to indicate that the operation on the shard is done. When the master node receives the command it queues cluster state update task and acknowledges the receipt of the command to the data node.\n\nThe update snapshot shard status tasks have relatively low priority, so during cluster instability they tend to get stuck at the end of the queue. If the master node gets restarted before processing these tasks the information about the shards can be lost and the new master assumes that they are still in process while the data node thinks that these shards are already done.\n\n This commit add a retry mechanism that checks compares cluster state of a newly elected master and the current state of snapshot shards and updates the cluster state on the master again if needed.\n\nCloses #11314","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/f0e6addc53bdd82dd55bab96f024012a7ba8456c"},{"sha":"90cbf80fc4e0864d83f3d8ebe9ff14b0f0cecde0","author":{"email":"78b6854e22ab09d4ae3dac29b92052963103b33e@motovs.org","name":"Igor Motov"},"message":"Tests: remove race condition in the masterShutdownDuringSnapshotTest","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/90cbf80fc4e0864d83f3d8ebe9ff14b0f0cecde0"},{"sha":"26d71fe00e8b9f5986a277ab5b6d2bb470a13766","author":{"email":"992531bec19101e9308e69893b3169c39fdfdd41@gmail.com","name":"Boaz Leskes"},"message":"Reduce shard inactivity timeout to 5m\n\nTo better distribute the memory allocating to indexing, the IndexingMemoryController periodically checks the different shard for their last indexing activity. If no activity has happened for a while, the controller marks the shards as in active and allocated it's memory buffer budget (but a small minimal budget) to other active shards. The recently added synced flush feature (#11179, #11336) uses this inactivity trigger to attempt as a trigger to attempt adding a sync id marker (which will speed up future recoveries).\n\nWe wait for 30m before declaring a shard inactive. However, these days the operation just requires a refresh and is light. We can be stricter (and 5m) increase the chance a synced flush will be triggered.\n\nCloses #11479","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/26d71fe00e8b9f5986a277ab5b6d2bb470a13766"},{"sha":"171687d207fdf88c1e8a285d1b785682969e9426","author":{"email":"1e115feeab9474b9d680e5528024201af6e7722f@traveljury.com","name":"Clinton Gormley"},"message":"Docs: Reorganised the Query DSL docs into families and explaing query vs filter context","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/171687d207fdf88c1e8a285d1b785682969e9426"},{"sha":"a522ddb4acf712dd3d9104ea48c8844fcb06785b","author":{"email":"f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","name":"Simon Willnauer"},"message":"[TEST] Add more logging to allocation decision","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/a522ddb4acf712dd3d9104ea48c8844fcb06785b"},{"sha":"f85a17ff1a01c4494a15a5337b1ddd083d44b34b","author":{"email":"1e115feeab9474b9d680e5528024201af6e7722f@traveljury.com","name":"Clinton Gormley"},"message":"Docs: Fixed heading level for in query DSL docs","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/f85a17ff1a01c4494a15a5337b1ddd083d44b34b"},{"sha":"39a20c3b5b68578a0c9b93d8bbd62a8c81e227cf","author":{"email":"4256e500e435802b8322cb0e0564f6a923e6df1d@users.noreply.github.com","name":"Colin Goodheart-Smithe"},"message":"Aggregations: Allow aggregation_binary to build and parse\n\nPreviously AggregationBuilder would wrap binary_aggregations in an aggregations object which would break parsing. This has been fixed so that for normally specified aggregations there are wrapped in an `aggregations` object, for binary aggregation which have the same XContentType as the builder it will use an `aggregations` field name and use the aggregationsBinary as the value (this will render the same as normal aggregations), and for binary aggregation with a different ContentType from the builder we use an `aggregations_binary` field name and add the aggregationsBinary as a binary value.\n\nAdditionally the logic in AggregationParsers needed to be changed as it previously did not parse `aggregations_binary` fields in sub-aggregations. A check has been added for the `aggregations_binary` field name and the binaryValue of this field is used to create a new parser and create the correct AggregatorFactories.\n\nClose #11457","distinct":false,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/39a20c3b5b68578a0c9b93d8bbd62a8c81e227cf"},{"sha":"313e9c67697a8c6f0b332e2005a39cf69f68c3df","author":{"email":"7abde52c298496fa169fb750f91f213a282142af@elastic.co","name":"Christoph Büscher"},"message":"Merge branch 'master' into feature/query-refactoring\n\n Conflicts:\n\tsrc/main/java/org/elasticsearch/index/query/RangeQueryParser.java\n\tsrc/main/java/org/elasticsearch/index/query/SpanTermQueryParser.java","distinct":true,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/313e9c67697a8c6f0b332e2005a39cf69f68c3df"}]}