{"push_id":1898609192,"size":582,"distinct_size":2,"ref":"refs/heads/fix-23823","head":"f4c0ec1fe86b3db917de63058f7a8c68b99f7e7c","before":"3341f38cc439f11ac7bfe0f72620da3c7c0e1ce9","commits":[{"sha":"a7a3af6f4878e8bd4d1eca0b98f85d29b07aea4a","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Log checkout so SHA is known\n\nThis commit changes the task type of the checkoutBwcBranch task to Exec\r\nfrom LoggedExec so that the output of the checkout command is\r\nshown. This enables us to see the SHA used for the checkout which can be\r\nuseful when debugging a BWC break.\r\n\r\nRelates #25166","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/a7a3af6f4878e8bd4d1eca0b98f85d29b07aea4a"},{"sha":"5cdbebec94ebce38925481300e6327a917c35acb","author":{"name":"Jim Ferenczi","email":"63c02f77e9b55c1b0416b1dcd7c38c9829c78407@elastic.co"},"message":"Test: remove faling test that relies on merge order","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/5cdbebec94ebce38925481300e6327a917c35acb"},{"sha":"5108fa75296b741cf677a93572fe14143fa69b86","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Remove unneeded weak reference from prefix logger\n\nWe have a custom logger implementation known as a prefix logger that is\r\nused to write every message by the logger with a given prefix. This is\r\nuseful for node-level, index-level, and shard-level messages where we\r\nwant to log the node name, index name, and shard ID, respectively, if\r\npossible. The mechanism that we employ is that of a marker. Log4j has a\r\nbuilt-in facility for managing these markers, but its effectively a\r\nmemory leak because these markers are held in a map and can never be\r\nreleased. This is problematic for us since indices and shards do not\r\nnecessarily have infinite life spans and so on a node where there are\r\nmany indices being creted and destroyed, this infinite lifespan can be a\r\nproblem indeed. To solve this, we use our own cache of markers. This is\r\nnecessary to prevent too many instances of the marker for the same\r\nprefix from being created (just think of all the shard-level components\r\nthat exist in the system), and to workaround the effective leak in\r\nLog4j. These markers are stored as weak references in a weak hash\r\nmap. It is these weak references that are unneeded. When a key is\r\nremoved from a weak hash map, the corresponding entry is placed on a\r\nreference queue that is eventually cleared. This commit simplifies\r\nprefix logger by removing this unnecessary weak reference wrapper.\r\n\r\nRelates #22460","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/5108fa75296b741cf677a93572fe14143fa69b86"},{"sha":"7ed3d6e75b48025b6fd366602693ded6f5a55fcb","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Fix comment formatting in EvilLoggerTests\n\nThe comments here were formatted inconsistently so this commit fixes\nthem.","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/7ed3d6e75b48025b6fd366602693ded6f5a55fcb"},{"sha":"718257790435cb31d110010b72b750821b9e0df8","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Fix handling of exceptions thrown on HEAD requests\n\nToday when an exception is thrown handling a HEAD request, the body is\r\nswallowed before the channel has a chance to see it. Yet, the channel is\r\nwhere we compute the content length that would be returned as a header\r\nin the response. This is a violation of the HTTP specification. This\r\ncommit addresses the issue. To address this issue, we remove the special\r\nhandling in bytes rest response for HEAD requests when an exception is\r\nthrown. Instead, we let the upstream channel handle the special case, as\r\nwe already do today for the non-exceptional case.\r\n\r\nRelates #25172","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/718257790435cb31d110010b72b750821b9e0df8"},{"sha":"9b8754e4c2650a026c5fe3c0dd88f1f469f3b826","author":{"name":"Boaz Leskes","email":"daaa071c1d6d35b7f0b1ebbbcc270afab5432337@gmail.com"},"message":"TranslogTests#commit didn't allow for a concurrent closing of a view\n\nThe view closing will trim unneeded files but there is a small window where they may still be around.","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/9b8754e4c2650a026c5fe3c0dd88f1f469f3b826"},{"sha":"dcf57f296e8f691e8099ea57ce011c41061e79c8","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Fix get mappings HEAD requests\n\nGet mappings HEAD requests incorrectly return a content-length header of\r\n0. This commit addresses this by removing the special handling for get\r\nmappings HEAD requests, and just relying on the general mechanism that\r\nexists for handling HEAD requests in the REST layer.\r\n\r\nRelates #23192","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/dcf57f296e8f691e8099ea57ce011c41061e79c8"},{"sha":"725f6b6983d0393b4622c2665b3e0c9e65f1cf9d","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Change BWC versions on get mapping 404s\n\nThis commit changes the BWC versions on the get mapping 404s now that\nthis API returning 404s when a type is missing is supported since 5.5.0.\n\nRelates #23192","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/725f6b6983d0393b4622c2665b3e0c9e65f1cf9d"},{"sha":"cfb5f6a5a69983c1b893019fc91bacc3296a0793","author":{"name":"Boaz Leskes","email":"daaa071c1d6d35b7f0b1ebbbcc270afab5432337@gmail.com"},"message":"Adapt TranslogTests.testWithRandomException to checkpoint syncing on trim\n\n#25005 changed the translog dynamic to fsync the checkpoint before trimming a file. This changed the dynamics of potential failure modes which requires a change to testWithRandomException - it's now possible that we had an exception but the translog was trimmed.\n\nCloses #25133","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/cfb5f6a5a69983c1b893019fc91bacc3296a0793"},{"sha":"f34136eda47bf965ea136e4fbe76e290a4a4da3e","author":{"name":"Boaz Leskes","email":"daaa071c1d6d35b7f0b1ebbbcc270afab5432337@gmail.com"},"message":"TranslogTests.testWithRandomException ignored a possible simulated OOM when trimming files","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/f34136eda47bf965ea136e4fbe76e290a4a4da3e"},{"sha":"7ab3d5d04a7c6dfef084e49587a81f7334a85cb4","author":{"name":"Jim Ferenczi","email":"63c02f77e9b55c1b0416b1dcd7c38c9829c78407@elastic.co"},"message":"Speed up sorted scroll when the index sort matches the search sort (#25138)\n\nSorted scroll search can use early termination when the index sort matches the scroll search sort.\r\nThe optimization can be done after the first query (which still needs to collect all documents)\r\nby applying a query that only matches documents that are greater than the last doc retrieved in the previous request.\r\nSince the index is sorted, retrieving the list of documents that are greater than the last doc\r\nonly requires a binary search on each segment.\r\nThis change introduces this new query called `SortedSearchAfterDocQuery` and apply it when possible.\r\nScrolls with this optimization will search all documents on the first request and then will early terminate each segment\r\nafter $size doc for any subsequent requests.\r\n\r\nRelates #6720","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/7ab3d5d04a7c6dfef084e49587a81f7334a85cb4"},{"sha":"518cda6637a4480fde5d7dde044dab5b2a0e2936","author":{"name":"markharwood","email":"0204eaa580bbd54c1fcaa27eb0c3886f1087ddf8@gmail.com"},"message":"Aggregations bug: Significant_text fails on arrays of text. (#25030)\n\n* Aggregations bug: Significant_text fails on arrays of text.\r\nThe set of previously-seen tokens in a doc was allocated per-JSON-field string value rather than once per JSON document meaning the number of docs containing a term could be over-counted leading to exceptions from the checks in significance heuristics. Added unit test for this scenario\r\n\r\nCloses #25029","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/518cda6637a4480fde5d7dde044dab5b2a0e2936"},{"sha":"2e29b69f6a497fdac496a5f94df3ab2ec1a7a2eb","author":{"name":"James Baiera","email":"d4cd44d347a01db171464f206187db7d089ed829@gmail.com"},"message":"Revert \"Revert \"Sense for VirtualBox and $HOME when deciding to turn on vagrant testing. (#24636)\"\"\n\nThis reverts commit b9e2a1f9890e12948c7e6a2fb57c30ca2b1fa76a.","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/2e29b69f6a497fdac496a5f94df3ab2ec1a7a2eb"},{"sha":"982900eabf67ceb3174a6eee2a16d7ef41992551","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Do not swallow node lock failed exception\n\nWhen attempting to obtain the node lock, if an exception is thrown it is\r\nnot logged. This makes debugging difficult. This commit causes such an\r\nexception to be logged.\r\n\r\nRelates #25176","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/982900eabf67ceb3174a6eee2a16d7ef41992551"},{"sha":"bb66f3b76b9df9be6684c9a7db2531d437ee45c6","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Explicitly reject duplicate data paths\n\nDuplicate data paths already fail to work because we would attempt to\r\ntake out a node lock on the directory a second time which will fail\r\nafter the first lock attempt succeeds. However, how this failure\r\nmanifests is not apparent at all and is quite difficult to\r\ndebug. Instead, we should explicitly reject duplicate data paths to make\r\nthe failure cause more obvious.\r\n\r\nRelates #25178","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/bb66f3b76b9df9be6684c9a7db2531d437ee45c6"},{"sha":"ee1113c902b3d6a7fc30fa1bfca934cac50dba2b","author":{"name":"Lee Hinman","email":"e62162cf4d95df85defedbb6fc7531efd473b77b@writequit.org"},"message":"Tweak AggregatorBase.addRequestCircuitBreakerBytes\n\nThis modifies a method Mark added to the AggregatorBase that allows aggregations\nto add additional memory tracking for datastructures used during execution. If\nan aggregation would like to reclaim circuit breaker reserved bytes by adding a\nnegative number, `addWithoutBreaking` should be used instead of\n`addEstimateBytesAndMaybeBreak`.\n\nResolves #24511","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/ee1113c902b3d6a7fc30fa1bfca934cac50dba2b"},{"sha":"88591fecacb45dd18aeccc7dbb3836fa51796069","author":{"name":"Spencer","email":"ba0781b4ccd0ad10284dc136298a445e1003e0c6@users.noreply.github.com"},"message":"[docs] include two cluster doc pages missing from index (#25180)\n\n* [docs] include two cluster doc pages missing from index\r\n\r\n* [rest-api-spec] update link to remote-info docs","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/88591fecacb45dd18aeccc7dbb3836fa51796069"},{"sha":"2f7de46b72df1b82f445b1e632e7487cc86fb6b5","author":{"name":"Lisa Cawley","email":"3aa2a8ba6142c2967cdcc4c973f2122b2d3fd5e1@elastic.co"},"message":"[DOC] Add X-Pack links to Elasticsearch Reference (#25164)\n\n* [DOC] Add X-Pack links to Elasticsearch Reference\r\n\r\n* [DOCS] Address alignment of attributes in Versions.asciidoc","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/2f7de46b72df1b82f445b1e632e7487cc86fb6b5"},{"sha":"f6821c41d8931bf1f508bdc185deba0d6e538d31","author":{"name":"Russ Cam","email":"8b23efd19b176e9445ed122ad8aaa6877ef7b64a@elastic.co"},"message":"Add half_float and scaled float (#22988)\n\nto numeric datatypes\n(cherry picked from commit 67ea06145a80d5ec52ba55d1f2e1e8287e1882b1)","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/f6821c41d8931bf1f508bdc185deba0d6e538d31"},{"sha":"a0f50e8aa41fcdc7676aea95d19ca09bce040438","author":{"name":"Russ Cam","email":"8b23efd19b176e9445ed122ad8aaa6877ef7b64a@elastic.co"},"message":"Supported Azure Storage account types (#25167)\n\n* Supported Azure Storage account types\r\n\r\nAdd important note for Azure Storage account types\r\n\r\nRelates #20844","distinct":false,"url":"https://api.github.com/repos/sneivandt/elasticsearch/commits/a0f50e8aa41fcdc7676aea95d19ca09bce040438"}]}
{"actor":{"display_login":"sneivandt"}}