kfaraz opened a new issue, #13320:
URL: https://github.com/apache/druid/issues/13320

   Apache Druid 24.0.1 is a bug fix release that fixes some issues in the 24.0 
release. 
   [See the complete set of changes for additional 
details](https://github.com/apache/druid/milestone/47?closed=1).
   
   ## <a name="24-1-bug-fixes" href="#24-1-bug-fixes">#</a> Bug fixes
   
   https://github.com/apache/druid/pull/13138 to fix dependency errors while 
launching a Hadoop task.
   https://github.com/apache/druid/pull/13214 to fix SQL planning when using 
the JSON_VALUE function.
   https://github.com/apache/druid/pull/13297 to fix values that match a range 
filter on nested columns.
   https://github.com/apache/druid/pull/13077 to fix detection of nested 
objects while generating an MSQ SQL in the web-console.
   https://github.com/apache/druid/pull/13172 to correctly handle overlord 
leader election even when tasks cannot be reacquired.
   https://github.com/apache/druid/pull/13259 to fix memory leaks from SQL 
statement objects.
   https://github.com/apache/druid/pull/13273 to fix overlord API failures by 
de-duplicating task entries in memory.
   https://github.com/apache/druid/pull/13049 to fix a race condition while 
processing query context.
   https://github.com/apache/druid/pull/13151 to fix assertion error in SQL 
planning.
   
   ## <a name="24-1-credits" href="#24-1-credits">#</a> Credits
   Thanks to everyone who contributed to this release!
   
   @abhishekagarwal87 
   @AmatyaAvadhanula
   @clintropolis
   @gianm
   @kfaraz
   @LakshSingla 
   @paul-rogers 
   @vogievetsky 


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to