cshannon opened a new pull request, #16754:
URL: https://github.com/apache/kafka/pull/16754

   This is a draft implementation of 
[KIP-1032](https://cwiki.apache.org/confluence/display/KAFKA/KIP-1032%3A+Upgrade+to+Jakarta+and+JavaEE+10+in+Kafka+4.0).
 This updates Kafka to Jakarta specs and JavaEE and Jetty 12. The changes here 
primarily effect Kafka Connect and MM2.
   
   There are a couple of things that are still outstanding (marked as TODOs in 
the code) but it's generally close to being finished and the connect and MM2 
tests are passing.
   
   **TODO/Notes:**
   
   1. For now I just bumped the entire build to JDK 17 (except the client to 
11) to make it easier vs having to go through each module and change which ones 
require 17. I know the broker is being bumped as well so I figure this can be 
sorted out soon.
   2. There is an issue with one of the MM2 tests that I had to change for now 
that involves escaping characters and not quite sure what to do about it yet. 
The cause is the Servlet 6 spec changing what is allowed in the path. See: 
https://github.com/jetty/jetty.project/issues/11890
   3. I had to configure the idle timeout in Jetty requests to match our 
request timeout so tests didn't fail. This was needed to fix the 
`ConnectWorkerIntegrationTest#testPollTimeoutExpiry()` test
   4. `CrossOriginFilter` has been deprecated and replaced with 
`CrossOriginHandler` so we may want to switch to that.
   
   
   Testing is being done by just using the existing tests for Connect and MM2 
which should be sufficient.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   


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

Reply via email to