cancel
Showing results for 
Search instead for 
Did you mean: 
Community Platform Discussions
Connect with fellow community members to discuss general topics related to the Databricks platform, industry trends, and best practices. Share experiences, ask questions, and foster collaboration within the community.
cancel
Showing results for 
Search instead for 
Did you mean: 

numpy.ndarray size changed, may indicate binary incompatibility

esi
New Contributor

Hi All,

I have installed the following libraries on my cluster (11.3 LTS that includes Apache Spark 3.3.0, Scala 2.12):

numpy==1.21.4
flair==0.12
 
on executing `from flair.models import TextClassifier`, I get the following error:
"numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject"

I have tried many things including updating numpy, downgrading numpy, changing the cluster specifications but all have failed. 

Any help would be greatly appreciated.
2 REPLIES 2

sean_owen
Databricks Employee
Databricks Employee

You have changed the numpy version, and presumably that is not compatible with other libraries in the runtime. If flair requires later numpy, then use a later DBR runtime for best results, which already has later numpy versions

Eddy123
New Contributor II

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group