{"push_id":1302644464,"size":4,"distinct_size":4,"ref":"refs/heads/5.x","head":"eb53e1c31bedfe9d56fc5bd4ed9ed422aa872a4c","before":"1eef6b7ef3b30429ed47598c2d68d83b76483f61","commits":[{"sha":"ed0f4a3c2a147f112ac7b720e1b0e807acc61284","author":{"name":"Luca Cavanna","email":"fcdf11cc3de751e1fde3dc9c882ec9c523a33c97@users.noreply.github.com"},"message":"Throw error if query element doesn't end with END_OBJECT (#20528)\n\n* Throw error if query element doesn't end with END_OBJECT\r\n\r\nFollowup to #20515 where we added validation that after we parse a query within a query element, we should not get a field name. Truth is that the only token allowed at that point is END_OBJECT, as our DSL allows only one single query within the query object:\r\n\r\n```\r\n{\r\n  \"query\" : {\r\n    \"term\" : { \"field\" : \"value\" }\r\n  }\r\n}\r\n```\r\n\r\nWe can then check that after parsing of the query we have an end_object that closes the query itself (which we already do). Following that we can check that the query object is immediately closed, as there are no other tokens that can be present in that position.\r\n\r\nRelates to #20515","distinct":true,"url":"https://api.github.com/repos/NSIT/elasticsearch/commits/ed0f4a3c2a147f112ac7b720e1b0e807acc61284"},{"sha":"0a50f43e3fa2b008e2be5f9ca0283eec7c8684ae","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"[TEST] introduce test plugin to inject random search ext elements in search request tests\n\nA few of our unit tests generate a random search request body nd run tests against it. The source can optionally contain ext elements under the ext sections, which can be parsed by plugins. With this commit we introduce a plugin so that the tests don't use the one from FetchSubPhasePluginIT anymore. They rather generate multiple search ext elements. The plugin can parse and deal with all those. This extends the test coverage as we may have multiple elements with random names.\n\nTook the chance to introduce a common test base class for search requests, called AbstractSearchTestCase, given that the setup phase is the same for all three tests around search source. Then we can have the setup isolated to the base class and the subclasses relying on it.\n\nCloses #17685","distinct":true,"url":"https://api.github.com/repos/NSIT/elasticsearch/commits/0a50f43e3fa2b008e2be5f9ca0283eec7c8684ae"},{"sha":"d164ef6eb37370ac4d15e89b580e718634eacaff","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"[TEST] set back the visibility of our search ext plugin in FetchSubPhasePluginIT to private\n\nThis plugin is not used in other tests anymore, it should be private to make sure its usage doesn't spread again","distinct":true,"url":"https://api.github.com/repos/NSIT/elasticsearch/commits/d164ef6eb37370ac4d15e89b580e718634eacaff"},{"sha":"eb53e1c31bedfe9d56fc5bd4ed9ed422aa872a4c","author":{"name":"javanna","email":"d51142909d00e71ece4605b8a70f34f3bab55d33@gmail.com"},"message":"[TEST] delete specific index boost serialization test, already covered by testSerialization\n\nindexBoost is already randomly set, we don't need a specific test for it in SearchSourceBuilderTests","distinct":true,"url":"https://api.github.com/repos/NSIT/elasticsearch/commits/eb53e1c31bedfe9d56fc5bd4ed9ed422aa872a4c"}]}
{"actor":{"display_login":"pmvs-deploy"}}