tree 00b61c42677e1d373bdc92237e1dd99ea168c067
parent 66d7cf343bd6dd40bed1e561a2ee9d157169fe81
author Blake Bender <bbender@pivotal.io> 1618584263 -0700
committer GitHub <noreply@github.com> 1618584263 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgeaLHCRBK7hj4Ov3rIwAAFFQIAK3+A6OT7xjCZecJf0Jngbey
 ojgDPgcSqqxXhGiLyBVeBQ1+vG6QE33nMPABiVFO/z0LbdaXXvwnpdMNwfhJoCyP
 h5JXOMerEC9Q7pwYbOA19qRt/hbqCwmirqSzoL8vQswvFE9YZxoBvk5YTuo7YdAf
 ShV+64Rsx/pY7mwQ1fNJrUazn44GilcVMj1m0Dbpk56aBbTOsN5wSsH15VX9opOo
 DDdpG9XOoWhBwIUBBjjpwYVQQKhtNP4gh5BFejdGllAZASLmHHo/WVbg5eHfd4dv
 BFbbrY9QTSYNtrY1a9G5mrdAg2Nsw+7s5V6FuiTRC3BmQzMV4Zc0353bTxjLW6U=
 =H7j9
 -----END PGP SIGNATURE-----
 

GEODE-9147: Revert to multi-hop PUTALL in the face of missing metadata (#784)

- This matches the behavior of the Java client
- Our current code to "tack on" values that we don't have metadata
  for will sometimes result in EventIds reaching a server out-of-order,
  causing them to be dropped and resulting in data loss.  Resorting
  to multi-hop avoids this altogether.
- Add test to repro issue of missing keys on single-hop putAll