Thank you for the prompt reply Wes. Just wanted to give a quick update, I no longer see the exception when using pyarrow installed via `conda` and using the `disable_server_verification` option.
Here are the details about the pyarrow build being used by conda. *# Name Version Build Channel* *pyarrow 2.0.0 py38h07f3135_5_cpu conda-forge* Regards, Keerat On Mon, Nov 2, 2020 at 1:14 PM Wes McKinney <wesmck...@gmail.com> wrote: > Supposedly we are building with grpc 1.29.1 in the manylinux wheels > (in conda-forge, we're at >= 1.33) > > > https://github.com/apache/arrow/blob/master/python/manylinux201x/scripts/build_grpc.sh > > So someone will need to take a closer look at the wheel (or conda) > builds to see what might be going wrong. > > On Mon, Nov 2, 2020 at 3:09 PM Keerat Singh <keer...@bitquilltech.com> > wrote: > > > > Hi, > > > > I see that the commit to add the support for > `*disable_server_verification`* > > was merged into the Arrow 2.0.0 release. > > > > - PR: https://github.com/apache/arrow/pull/8325 > > > > However, when trying to use the FlightClientOption > > `disable_server_verification` with TLS enabled using a Python > application, > > I see the following exception: > > > > - *pyarrow.lib.ArrowNotImplementedError: Using encryption with server > > verification disabled is unsupported. Please use a release of Arrow > Flight > > built with gRPC 1.27 or higher.* > > - I am using pyarrow version 2.0.0 installed via pip and have > confirmed > > via `pip freeze` that the version of pyarrow being used is indeed > 2.0.0. > > > > Is there something more that needs to be done to enable and use this > > feature with the Python application? Also, how do I determine the version > > of gRPC that the Arrow Flight 2.0.0 was built with? > > > > Regards, > > Keerat > -- *Keerat Singh* Senior Software Developer Bit Quill Technologies Inc. keer...@bitquilltech.com https://www.bitquilltech.com This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.
