[issue-8297] upgrade netty due to security concerns#8298
[issue-8297] upgrade netty due to security concerns#8298pjfanning wants to merge 7 commits intoapache:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8298 +/- ##
=============================================
- Coverage 70.83% 30.78% -40.05%
=============================================
Files 1631 1619 -12
Lines 85462 85108 -354
Branches 12877 12839 -38
=============================================
- Hits 60539 26203 -34336
- Misses 20746 56556 +35810
+ Partials 4177 2349 -1828
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
Hi @pjfanning , Can you please rebase this PR with latest master |
|
Please rebase |
1383fd7 to
95f498c
Compare
|
I rebased this but there are problems with pinot-pulsar and its unit tests. It appears that something in the version of pulsar that pinot-pulsar uses that relies on the old netty. I'm not an expert on pinot or pulsar and might need to leave this to someone else to solve. It might be better to upgrade pulsar first before trying to update netty. |
Description
update netty jars due to security concerns
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)
backward-incompat, and complete the section below on Release Notes)Does this PR fix a zero-downtime upgrade introduced earlier?
backward-incompat, and complete the section below on Release Notes)Does this PR otherwise need attention when creating release notes? Things to consider:
release-notesand complete the section on Release Notes)Release Notes
Documentation