Armin Braun
Armin Braun
> This could mean that shards with no changes being scheduled after large file uploads? We figured this was somewhat unlikely (to happen a lot) and outweigh by the fact...
> Am I missing something essential here? You're not directly missing anything actually. But I think there is a tradeoff here. This change makes it so that running a snapshot...
This should be good to review now at long last, did my best to keep the changes short, there's certainly some follow-ups possible here to streamline the code a little....
Thanks Henning I adjusted the API as you suggested in one case and commented on the other now, let me know what you think :)
@henningandersen gentle ping here :)
Thanks Henning all points addressed again I think :)
Thanks Henning, I think I addressed all points (hope I didn't miss anything :crossed_fingers: ). This should be good for another round I think.
Thanks again Henning! I think I once again addressed all points :)
@DaveCTurner > if we add a response header (especially a deprecation warning) during REST serialization, which might now be after we've finished sending response headers to the client Good point....
Jenkins run elasticsearch-ci/part-1 ( known + unrelated)