{"push_id":1468947710,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"7946396fe682103929dd81c8d21dec1ad6fb3c95","before":"91cb56324726f7541dabb4dfe1e7aee103cac8bb","commits":[{"sha":"7946396fe682103929dd81c8d21dec1ad6fb3c95","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Introduce translog no-op\n\nAs the translog evolves towards a full operations log as part of the\r\nsequence numbers push, there is a need for the translog to be able to\r\nrepresent operations for which a sequence number was assigned, but the\r\noperation did not mutate the index. Examples of how this can arise are\r\noperations that fail after the sequence number is assigned, and gaps in\r\nthis history that arise when an operation is assigned a sequence number\r\nbut the operation never completed (e.g., a node crash). It is important\r\nthat these operations appear in the history so that they can be\r\nreplicated and replayed during recovery as otherwise the history will be\r\nincomplete and local checkpoints will not be able to advance. This\r\ncommit introduces a no-op to the translog to set the stage for these\r\nefforts.\r\n\r\nRelates #22291","distinct":true,"url":"https://api.github.com/repos/gfyoung/elasticsearch/commits/7946396fe682103929dd81c8d21dec1ad6fb3c95"}]}
{"actor":{"display_login":"gfyoung"}}