You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For anything that needs to be serialized and stored to disk, then deserialized from disk to RAM, we need some means of testing that the file format and serialized representation remains backward compatible as influxdb evolves. From #25492 (review), in order to test this, we would need something along these lines:
A static file with the appropriate data members checked into the repo
A test that can deserialize the static file and validate it has the members we expect (this is all hard coded stuff)
Another test that takes an in memory structure, serializes it, then deserializes that and validates they're the same (this might be unnecessary)
Using something like insta doesn't work for us since we use a lot of HashMaps in our data types, whose ordering is not deterministic and therefore makes the use of a snapshotting tool like insta too brittle.
The text was updated successfully, but these errors were encountered:
For anything that needs to be serialized and stored to disk, then deserialized from disk to RAM, we need some means of testing that the file format and serialized representation remains backward compatible as
influxdb
evolves. From #25492 (review), in order to test this, we would need something along these lines:Using something like
insta
doesn't work for us since we use a lot ofHashMap
s in our data types, whose ordering is not deterministic and therefore makes the use of a snapshotting tool likeinsta
too brittle.The text was updated successfully, but these errors were encountered: