tree 576021a1bf92b3cb2300af2a17b9b51521bfc548
parent 78c50e7ae5b4127ff4cc7a53f322f428c4b52323
author Sanil Jain <sanil.jain15@gmail.com> 1617154468 -0700
committer GitHub <noreply@github.com> 1617154468 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgY9GkCRBK7hj4Ov3rIwAAdHIIABzh4aO8g3XLjZX99SgCTjAx
 1im4JstNLYWI7U+RDNxdzJcG5gBE0bW2RoSL8nT2DP0X7+0og9pPJusPJ2f00igN
 4OgiZR5/Df4LDv1Mki3Y4IqlGeSnbsP4/BkNv4PNaZoHyHej3L896t2TDyxW5X4J
 YZDDSLEel+jXd8KOE5RdRh5v4Dt5vTEJtKR2TPWrjRorU7NyvnTY8es9oIGZOFmJ
 3lbonj9O7sVKxcGrt8r5g2QIABFabHKPuEcFy2HcgGxxID+nig3ltmTMvU+NPMUN
 4mwPa0+eum5zByciO+lJbcMd1JSXPoMHOGSH+bz5J8BvvT1hKtb2QTHvy+ypwMo=
 =Z1zT
 -----END PGP SIGNATURE-----
 

SAMZA-2643: Cleanup redundant null serde checks in ContainerStorageManager, these checks should only be in BaseKeyValueStorageEngineFactory (#1486)

Feature/Issue:
BaseKeyValueStorageEngineFactory assumes non-null serdes for k,v of stores using it and applies check/ ContainerStorageManager also applies redundant check to verify the same, however, this might not hold true for some StorageEngine use cases, since some stores may elect to not expose serdes but just use Java Objects as K, V

Changes:

Remove the redundant check from ContainerStorageManager that assumes each store should have non-null serdes
Add docs to BaseKeyValueStorageEngineFactory on serde assumption
Add more docs on assumptions for serdes and existence between wrappedStore & rawStore in KeyValueStorageEngine API