-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update jackson and azure #80160
Update jackson and azure #80160
Conversation
There were other changes the last time we tried to update azure - https://github.com/elastic/elasticsearch/pull/73837/files#diff-0a3347d8c82d7507fa4507d2fde0f5feb4fa718a0d5025a249afbcde5621c555 - but the tests don't fail and I don't know what they were for. |
Pinging @elastic/es-distributed (Team:Distributed) |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
This grabs a new version of jackson and snakeyaml to get some bug fixes. It also updates azure to stay compatible with the new jackson. Closes elastic#66555 Closes elastic#67214 Closes elastic#80142
Sadly we are still blocked by this issue Azure/azure-sdk-for-java#22042 I've pinged the team several times but it seems like there hasn't been any progress on that |
Adding these back helped the broken tests.
@fcofdez Oh! Is there any way we can get just jackson upgraded? I really do want to get us unstuck and I don't know anything about Azure. |
Do we have any tests that'd fail on upgrade that I can trigger btw? |
I know few folks on a related team, I'll reach out. |
The CI job that runs the problematic test is |
This failure is the same one we had last time we tried to update:
I really don't know anything about the Azure deployment. I'd like to hand this upgrade off to someone that does. I'm many layers deep from the code I was trying to write in the first place and there are much better experts over here. |
@nik9000 I can take care of this once the bug in the azure SDK is fixed |
Thanks so much. I'm way out of my depth here. Or, at least, it'd take me a lot of reading to catch up. |
hi, @nik9000 , is it necessary to update jackson first? as the badcase in exclude exist in the current version? |
For now at least these are stuck together due to a breaking change in Jackson that breaks azure. It's pretty deep so I can see how the folks that made the change didn't think of it as a version change thing. I think we're waiting on @ChrisHegarty's contacts at Azure to update to the newer version of jackson. |
That would be @grcevski's contact. :-) |
The bug was finally fixed Azure/azure-sdk-for-java#22042 once they release a new version with the fix, I'll upgrade the libraries. |
Fwiw, jackson 2.13.1 was released 6 days ago (at the timing of writing this comment): |
Once we can upgrade jackson and jackson released 2.14 we can fix #63842. |
@fcofdez do you know what version we're waiting on? I can't really tell from the linked issues. |
@nik9000 We're waiting for |
Thanks! |
Checks that archive functionality works with source-only repositories. Relates #80160
Checks that archive functionality works with source-only repositories. Relates elastic#80160
Checks that archive functionality works with source-only repositories. Relates elastic#80160
add a xcontent filter test that will failed, when random to `filterOnParser`. The test will fixed when jackson upgrade in #80160
Overtaken by #83884 |
This grabs a new version of jackson and snakeyaml to get some bug fixes.
It also updates azure to stay compatible with the new jackson.
Closes #66555
Closes #67214
Closes #80142