lriggs commented on issue #43576: URL: https://github.com/apache/arrow/issues/43576#issuecomment-2452735001
Hi, I work with @laurentgo at Dremio and I've started looking into this issue. Let me know if there is a better format for this discussion (email vs GH issue, etc). I wanted to summarize some of the different threads and then talk about how I've worked around the issue here at Dremio. The test errors seem to all be "Symbols not found: [ llvm_orc_registerEHFrameSectionWrapper ]" which is also tracked [here](https://github.com/apache/arrow/issues/43769 ), and a few causes and ideas for fixes are listed [here](https://github.com/apache/arrow/pull/43770#issuecomment-2299793645) and [here](https://github.com/apache/arrow/issues/39695#issuecomment-1912186637) for Python. I also found [this](https://github.com/llvm/llvm-project/issues/74671) issue regarding the symbols in the llvm project. The poster there believes that requiring the symbols is a bad design. I tend to agree but I'm not sure why it was done in the first place. The ORC symbol issue seems to stem from [https://github.com/apache/arrow/issues/37848](https://github.com/apache/arrow/issues/37848). We haven't had this problem at Dremio because we actually reverted that change in our local repo after I found a few llvm expression related test failures. I asked about that here [https://lists.apache.org/thread/xzrwx1t37dc88vo5yo5337l16ypqwcrd](https://lists.apache.org/thread/xzrwx1t37dc88vo5yo5337l16ypqwcrd). I spent considerable time looking into this issue but was never able to track it down. I'm not sure what to do at this point. One idea is reverting the JIT upgrade while also following up with the llvm community on the symbol issue. @niyue Mentioned following up with them here, not sure if he found anything: [https://github.com/apache/arrow/issues/39695#issuecomment-1918780143](https://github.com/apache/arrow/issues/39695#issuecomment-1918780143) -- 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]
