ng-ngi opened a new issue, #19729: URL: https://github.com/apache/hudi/issues/19729
### Bug Description **What happened:** when using hudi-azure 1.2.0 alongside hudi 1.2.0 on spark 4.0 and 4.1 via spark connect, the internal timeline server fails to start upon a write operation, with the error message suggesting a shading issue: <img width="1665" height="760" alt="Image" src="https://github.com/user-attachments/assets/7414601a-862d-4e18-b365-72c2b15b286a"; /> when we --exclude-packages "org.apache.hudi:hudi-timeline-service", which is a dependency of hudi-azure, the timeline starts as it should upon a write operation: <img width="1687" height="775" alt="Image" src="https://github.com/user-attachments/assets/fb618e96-31b9-4503-bacd-4442748addff"; /> **What you expected:** hudi-azure 1.2.0 should shade its dependencies such that other packages aren't affected. Or, if I'm misunderstanding the problem: hudi-azure 1.2.0 shouldn't prevent hudi's internal timeline server from starting. **Steps to reproduce:** 1. write to an azure-based hudi table using spark 4.0.x via spark connect with hudi 1.2.0 and hudi-azure 1.2.0 2. This may require a second write if initialization doesn't kick off the internal timeline server, but as far as I've seen any attempt to start the internal timeline server fails due to this casting failure ### Environment **Hudi version:** 1.2.0 **Query engine:** Spark 4.0.1 **Relevant configs:** hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.StorageBasedLockProvider hoodie.embed.timeline.server=true ### Logs and Stack Trace shown in "what happened" above -- 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]
