{"push_id":1859914846,"size":3,"distinct_size":1,"ref":"refs/heads/j/upsert-simplify","head":"28f2d8c28fdaa2c705c4ada7a72b66a01163e8b0","before":"55666e8d9d590a23b26af29f1e6814ca9a32e319","commits":[{"sha":"f2e851453aa128b4d78a92617e4454451e48a4b8","author":{"name":"Michael Beer","email":"844aface8de49b32585c3c744b570659f1739c56@crate.io"},"message":"fixed classpath issue in windows batch file","distinct":false,"url":"https://api.github.com/repos/crate/crate/commits/f2e851453aa128b4d78a92617e4454451e48a4b8"},{"sha":"2975c3454f698339ea6f1f154137addcd29641eb","author":{"name":"Mathias Fussenegger","email":"bb3637c24a3a37def2478baea23f3a63a3cb44bb@zignar.net"},"message":"Encapsulate resultFuture in BatchIteratorBackpressureExecutor\n\nBefore the `executionFuture` could be completed from two components,\neither the component using the `BatchIteratorBackpressureExecutor` or from\nthe `BatchIteratorBackpressureExecutor` itself. Now the\n`BatchIteratorBackpressureExecutor` owns the future.\n\nThis also changes the kill handling a bit. Now we rely on\n`BatchIterator.moveNext` failing if it's killed.\nIn addition. The `ShardingUpsertExecutor` will no longer short-circuit\nbut wait for pending operations to complete before setting a failure.","distinct":false,"url":"https://api.github.com/repos/crate/crate/commits/2975c3454f698339ea6f1f154137addcd29641eb"},{"sha":"28f2d8c28fdaa2c705c4ada7a72b66a01163e8b0","author":{"name":"Mathias Fussenegger","email":"bb3637c24a3a37def2478baea23f3a63a3cb44bb@zignar.net"},"message":"Simplify BatchIteratorBackpressureExecutor\n\nThis simplifies the BatchIteratorBackpressureExecutor by using a single\nSemaphore to restrict the `consumeIterator` to a single thread instead\nof using multiple AtomicBooleans/booleans.\n\nThis makes it possible to always use the same callback on each\n\"execute-batch\" invocation.","distinct":true,"url":"https://api.github.com/repos/crate/crate/commits/28f2d8c28fdaa2c705c4ada7a72b66a01163e8b0"}]}
{"actor":{"display_login":"mfussenegger"}}