tree 52e5a916cfca9b6f17ec753e8288e5ac9e4f4e77
parent a3c3e10c2e054ca832cc3294fe15bd0e87f78023
author lakshmi-manasa-g <mgaduputi@linkedin.com> 1659482361 -0700
committer GitHub <noreply@github.com> 1659482361 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi6bD5CRBK7hj4Ov3rIwAAKjUIAD+b6oVhz1PgPd0oJB0Yvtgl
 tVdu4z+XRXbK7TrebDJKxOjIXm9XChFfUB6KtOorXNmp26K2XhvaoViMecmDc9Rk
 lfOXt9/Eh0yxdmfcA+f/SGqAuGeNzX4F+h1uRgyuog+CZiEYGWlUhKXRQCRu931x
 mS3Q4qPQTXSB1Yu4K4rqXLkjMTrDOlnXneAIxRXxV/QejLaFOL6umPbA6z4rSeik
 qMF/0zI8+ydm312wfiDsU0o4qrssHbicCXOxYiLdNqJuJekYvrGxYUze62cYU2Yp
 Gu6Op9Q7NQ3WgYmYreU6axfnlr0+84Ndo3IOybomiO77pOa7Bv9SiEV5jbjVhZY=
 =zUzy
 -----END PGP SIGNATURE-----
 

remove keyBucket from checkpoint serde to allow for simpler rollback (#1625)

Symptom: Rolling back to versions which dont accept 4 parts in checkpoint serde can throw NPE exceptions.
Cause: As part of elasticity, #1608 introduced keyBucket into checkpoint serde.
Fix: Remove keyBucket from checkpoint serde - aka do not add it when serializing checkpoint.

Backwards Compatible: yes.
Though checkpoints written after #1608 and before this PR will have 4 part SSP in checkpoint, serde, they can still be read by code in this PR and vice versa.
elasticity will not work completely once this pr is merged.