leerho edited a comment on issue #10042: URL: https://github.com/apache/druid/issues/10042#issuecomment-676543197
> > We only guarantee that sketches generated from an older code version can be read by newer code versions; not the other way around. > > Hmm, this guarantee unfortunately isn't strong enough for how Druid is designed, for two reasons that apply during software updates: @gianm I suggest we create a new issue on this. We are open to dig deeper into this, but I don't know of any library that guarantees that older code versions can properly interpret newer code versions. Newer code versions not only add features (which, in theory, should not affect this issue), but also do bug fixes, which will impact this issue. Just to clarify, we have code versions, which are the release version numbers, and we have serialization versions, which only change if the layout of the data in the serialized byte array changes. Since code version 0.1.0, October 2015, we have had the same serialization version 3 for Theta sketches. However, even given the same format, how it is populated and interpreted has changed slightly since code version 0.1.0, especially with bug fixes. Let's discuss. Lee. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
