[SPARK-50886][BUILD][3.5] Upgrade Avro to 1.11.4#49563
[SPARK-50886][BUILD][3.5] Upgrade Avro to 1.11.4#49563dongjoon-hyun wants to merge 2 commits intoapache:branch-3.5from
Conversation
|
cc @LuciferYang |
|
Could you review this PR, @panbingkun ? |
The compilation for Scala 2.13 failed. Can we re-trigger it to confirm if it was just a random occurrence? |
The compilation for Scala 2.13 failed.
|
Oh.. Let me check. |
|
I tried it out and found that 1.11.3 can be compiled successfully. The issue likely stems from 1.11.4. |
|
Oh, surprising. Actually, 1.11.4 was requested last year. Let me dig more. |
|
The root cause seems due to the SBT dependency bug. I pinned |
|
BTW, this patch and the pinning is only for |
|
It seems so. I tried compiling with Maven, and it worked fine at commit |
LuciferYang
left a comment
There was a problem hiding this comment.
+1, LGTM
pending tests
|
Thank you always for your deep review and co-investigation! |
|
All tests passed. Merged to branch-3.5. |
### What changes were proposed in this pull request? This PR aims to upgrade Avro to 1.11.4. ### Why are the changes needed? To bring the latest bug fixes like the following. - https://github.com/apache/avro/releases/tag/release-1.11.3 - apache/avro#2432 - apache/avro#2318 - apache/avro#1720 - https://github.com/apache/avro/releases/tag/release-1.11.4 - apache/avro#2980 ### Does this PR introduce _any_ user-facing change? Yes, this is a dependency change. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #49563 from dongjoon-hyun/SPARK-50886. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
|
+1, late LGTM |


What changes were proposed in this pull request?
This PR aims to upgrade Avro to 1.11.4.
Why are the changes needed?
To bring the latest bug fixes like the following.
Does this PR introduce any user-facing change?
Yes, this is a dependency change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.