[ https://issues.apache.org/jira/browse/BEAM-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949810#comment-16949810 ]
Wes McKinney commented on BEAM-8368: ------------------------------------ It seems very likely that the grpc wheel statically links Protobuf. I just posted a patch for ARROW-6860 to move the protobuf symbols out of the {{import pyarrow.parquet}} import path. If you {{import pyarrow.flight}} (which includes gRPC statically linked), you will still have problems. We're going to try to make a 0.15.1 release once we fix some other bugs that have surfaced since 0.15.0 was released > [Python] libprotobuf-generated exception when importing apache_beam > ------------------------------------------------------------------- > > Key: BEAM-8368 > URL: https://issues.apache.org/jira/browse/BEAM-8368 > Project: Beam > Issue Type: Bug > Components: sdk-py-core > Affects Versions: 2.15.0, 2.17.0 > Reporter: Ubaier Bhat > Assignee: Ahmet Altay > Priority: Blocker > Fix For: 2.17.0 > > Attachments: error_log.txt > > Time Spent: 20m > Remaining Estimate: 0h > > Unable to import apache_beam after upgrading to macos 10.15 (Catalina). > Cleared all the pipenvs and but can't get it working again. > {code} > import apache_beam as beam > /Users/***/.local/share/virtualenvs/beam-etl-ims6DitU/lib/python3.7/site-packages/apache_beam/__init__.py:84: > UserWarning: Some syntactic constructs of Python 3 are not yet fully > supported by Apache Beam. > 'Some syntactic constructs of Python 3 are not yet fully supported by ' > [libprotobuf ERROR google/protobuf/descriptor_database.cc:58] File already > exists in database: > [libprotobuf FATAL google/protobuf/descriptor.cc:1370] CHECK failed: > GeneratedDatabase()->Add(encoded_file_descriptor, size): > libc++abi.dylib: terminating with uncaught exception of type > google::protobuf::FatalException: CHECK failed: > GeneratedDatabase()->Add(encoded_file_descriptor, size): > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)