[GitHub] [druid] capistrant commented on issue #10042: com.yahoo.sketches.SketchesArgumentException: Incompatible Seed Hashes. 0, -27700

[GitBox <gi...@apache.org>]

capistrant commented on issue #10042:
URL: https://github.com/apache/druid/issues/10042#issuecomment-687842941


   @leerho @gianm 
   
   Circling back on this now that I've gotten my cluster upgraded to druid 18. My team did go forward with using my proposed patch (without seed override) in order to bridge the gap between druid 15 and druid 18. It went well. My question now is how we would like to handle this from a Druid community standpoint?
   
   [Pull 8647](https://github.com/apache/druid/pull/8647) is where I think the introduction of this compatibility issue came. So Druid 17, 18, 19 are all affected when upgrading from <= druid 16. 
   
   Can we retroactively update release notes upgrading sections with an "upgrading from druid 16 or earlier heading" to call out the potential problem?
   
   And do we want to do anything concrete to address this as far as Druid code changes? I haven't thought too hard on if there could be a change for druid 20 that would smooth this over or if this would require a patch release in older druid versions instead (like how my this handled this).
   
   I'm definitely willing to help push whatever we choose is best. Maybe a thread in the dev list is a good place to start? Let me know what you all think.


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org