Backwards compatibility for time using msgpack encoding and decoding

Question

Backwards compatibility for time using msgpack encoding and decoding

Closed this issue 6 years ago · 4 comments

Can you please recommend some backwards compatibility :
If you encode the time in a version before the commit 5a66da2, how can we decode it in the commits after it? The used encoder is msgpack.
The error is : Error executing command: msgpack decode error [pos 131]: invalid length of bytes for decoding time - expecting 4 or 8 or 12, got 15

Answer 1 · 2018-09-27T04:00:18.000Z

@Trial97 That commit didn't make any changes to time encoding for msgpack.

Answer 2 · 2018-09-27T07:55:21.000Z

Sorry for the inconveniences the commit that the change happened is: debb8e2, not the one mentioned before.

Answer 3 · 2018-09-27T14:06:13.000Z

That flag is only to migrate the data?

Answer 4 · 2018-09-27T14:33:25.000Z

This the best I can do.

You might have to read with one handle configured one way, and write back out with another handle configured the other way. This allows you migrate.