Great to hear that! Fortunately, I was waiting for someone to answer and hadn't looked at it yet.
Seems a quite straightforward solution for an issue that shouldn't have to exist if the right unit test had been implemented. What do you think about adding a test to check this issue doesn't happen again? I'm planning to write an article about Spark Connect, so ... thanks again for providing the project to start playing around. El dom, 23 mar 2025, 2:01, Bobby <wbo4...@gmail.com> escribió: > Thx @Ángel <angel.alvarez.pas...@gmail.com> , I had a PR > https://github.com/apache/spark/pull/50334 to fix it. Please help review. > > Ángel Álvarez Pascua <angel.alvarez.pas...@gmail.com> 于2025年3月22日周六 > 16:27写道： > >> Is anyone looking into this issue? If not, I'd like to try fixing it. >> I've never tried out Spark Connect, so... 2x1! (way better than spending >> the weekend binge-watching on Netflix 😅🤣). >> >> @Bobby <wbo4...@gmail.com> , thanks a lot, not only for reporting the >> issue but also for providing a time-saving project for testing. >> >> El sáb, 22 mar 2025 a las 1:11, Bobby (<wbo4...@gmail.com>) escribió: >> >>> I think https://issues.apache.org/jira/browse/SPARK-51537 should be >>> fixed before 4.0.0 release, or else, the executor side will not use global >>> jars added by `--jars` in the connect mode, which could result in >>> deserialization exceptions. >>> >>
