parquet-dotnet: Unable to load shared library nironcompress (Macbook Pro Intel, Azure Function)

Version: Parquet.Net v4.1.2 Runtime Version: .NET 6 OS: MacOSX (Intel)

Expected behavior

Expected Parquet.NET to load all necessary dependencies

Actual behavior

I get the following error when running the function locally:

System.Private.CoreLib: Exception while executing function: MyFunctionName. IronCompress: Unable to load shared library 'nironcompress' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable: dlopen(libnironcompress, 0x0001): tried: 'libnironcompress' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibnironcompress' (no such file), '/usr/lib/libnironcompress' (no such file, not in dyld cache), 'libnironcompress' (no such file), '/usr/local/lib/libnironcompress' (no such file), '/usr/lib/libnironcompress' (no such file, not in dyld cache).

Steps to reproduce the behavior

  1. Create the example from the getting started section
  2. Run it inside an Azure Function on MacOSX

Thank you for any help on this!

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 35 (16 by maintainers)

Most upvoted comments

Ok, but reading fails on ironcompress. Btw I had no issues with version 3.7

בתאריך יום ב׳, 23 בינו׳ 2023, 15:44, מאת Ivan G @.***>:

No, encoding and compression are unrelated.

— Reply to this email directly, view it on GitHub https://github.com/aloneguid/parquet-dotnet/issues/207#issuecomment-1400374189, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGEHUAOQWBRQM5ZOIUQ4GFDWT2DMNANCNFSM6AAAAAAS7YCEVQ . You are receiving this because you were mentioned.Message ID: @.***>

@aloneguid is doing all the work here, so kudo’s to him!

Yep I encountered this afree updating to new versions also. I use Parquet.Net exclusively in serverless background processes that run as Azure Functions.

I’ll try checking the bitness of my Function App as noted by @rustyswayne and report back if that resolves it…

@josdeweger Thanks for posting this issue and all the details in the thread! Saved me a lot of time trying to sort out what this error was all about! 🙏