capistrant commented on issue #10042: URL: https://github.com/apache/druid/issues/10042#issuecomment-676719085
> I think this assumes the default seed, which is not always the case. Of course, no one stops you from using such a shortcut in your custom build. Hmm, good point. I assumed (probably naively) that since nowhere in the Druid code base I can find `Sketches#wrapSketch(Memory, long)` that everything would just be using that default seed. I'm just starting to throw ideas at the wall at this point. This one appeared to be the easiest to pull off operationally. I've also considered evaluating an upgrade of the sketches dependency for the druid 15 so there is no version incompatibility during rolling upgrade. That would allow me to upgrade sketches in the order that would be clean (broker, historical, middleManager) followed by the druid upgrade in their recommended order (historical, middlemanager, broker). Regardless, it should be a fun time. ---------------------------------------------------------------- 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]
