xvrl opened a new pull request #12032:
URL: https://github.com/apache/druid/pull/12032


   - HttpResponse no longer includes request content, this changes some
     HttpReponseHandler implementations to no longer assume content is
     generated as part of the handleResponse call, and instead expect all
     request content as part of the handleChunk
   
   - HttpResponseHandler changes uncovered a long-standing bug in
     AppendableByteArrayInputStream where calling exceptionCaught before
     appending any bytes would not throw the exception to the reader
   
   - Netty HTTP decoder now stores decoder errors in the message instead of
     triggering exceptionCaught, so we need to check the statuf of the
     decoder.
   
   - Netty Messages and underlying buffers are reference counted, so they
     need to be explicitly released after handling. As part of this
     ChannelBuffer became ByteBuf and are reference counted instead of
     garbage collected.
   
   - To support back-pressure, Channels need to disable AUTO_READ and call
     read() explicitly when needed instead of using setReadable(true/false)
   
   - ClientBootstrap no longer uses separate bosspool and workerpool sizes,
     instead relying on the workerpool.
   
   - Netty HTTP codec now supports resuming handling of HTTP messages after
     handling CONNECT, removing the need to manually add the codec back to
     the pipeline.
   
   - Remove deprecated Netty method calls and rename classes to align with
     Netty class name changes
   
   - Remove deprecated use of ExpectedException in favor of
     Assert.assertThrows for all tests that had to be touched.
   


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