Hi Antoine, I struggled a bit to put all my thoughts in an email format, that will be easily consumable. So, I wrote up a github markdown to add some more detail to the issue, we are facing.
Could you take a look, and let us know your thoughts? https://github.com/mathworks/matlab-arrow-support-files/blob/main/libarrowclash.md Regards, Tahsin From: Antoine Pitrou <anto...@python.org> Date: Tuesday, February 23, 2021 at 1:21 PM To: dev@arrow.apache.org <dev@arrow.apache.org> Subject: Re: [C++] libarrow isolation Hi Tahsin, I see. So the error happens when loading PyArrow into MATLAB, I suppose? What kind of error do you get? Regards Antoine. Le 23/02/2021 à 18:12, Tahsin Hassan a écrit : > Hi Antoine, > > MATLAB is using RTLD_GLOBAL. Hope that helps in clarifying the workflow. > > Regrards, > Tahsin > > ________________________________ > From: Antoine Pitrou <anto...@python.org> > Sent: Monday, February 22, 2021 9:41 AM > To: dev@arrow.apache.org <dev@arrow.apache.org> > Subject: Re: [C++] libarrow isolation > > > Le 22/02/2021 à 15:29, Tahsin Hassan a écrit : >> Hi all, >> >> MATLAB uses the Arrow C++ libraries (i.e. libarrow.so) to read and write >> Parquet files (https://www.mathworks.com/help/matlab/ref/parquetread.html) >> While exploring ways to integrate more tightly with Arrow, we've run into a >> symbol/library naming clash issue. >> >> When running pyarrow within the MATLAB process >> (https://www.mathworks.com/help/matlab/call-python-libraries.html?s_tid=CRUX_lftnav >> ), the libarrow.so loaded by pyarrow clashes with the libarrow.so shipping >> with MATLAB. > > For the record, Python loads extension modules (such as PyArrow) with > RTLD_LOCAL. I assume MATLAB doesn't? > > Regards > > Antoine. > >
