<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32370#M23580</link>
    <description>&lt;P&gt;@Janani Mohan​&amp;nbsp;- Does the information that Atanu provided help?  If yes, would you be happy to mark it as best so that other members can find the solution more quickly?&lt;/P&gt;</description>
    <pubDate>Wed, 26 Jan 2022 16:17:02 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2022-01-26T16:17:02Z</dc:date>
    <item>
      <title>ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject</title>
      <link>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32367#M23577</link>
      <description>&lt;P&gt;After the new release of numpy 1.22.0 on Dec 31st, Databricks failed with this error for my existing Databricks Notebook Version 10.1 and numpy 1.20.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qn: Why did the earlier releases after 1.20.0 uptil 1.22.0 did not raise the same exception. ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 16:41:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32367#M23577</guid>
      <dc:creator>JananiMohan</dc:creator>
      <dc:date>2022-01-03T16:41:50Z</dc:date>
    </item>
    <item>
      <title>Re: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject</title>
      <link>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32368#M23578</link>
      <description>&lt;P&gt;@Janani Mohan​&amp;nbsp;- Hi there, and welcome to the community! Before we step in, let's give the other members a chance to reply. &lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 23:19:16 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32368#M23578</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-01-03T23:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject</title>
      <link>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32369#M23579</link>
      <description>&lt;P&gt;@Janani Mohan​&amp;nbsp; there are some changes I can see from &lt;A href="https://numpy.org/devdocs/release/1.22.0-notes.html" target="test_blank"&gt;https://numpy.org/devdocs/release/1.22.0-notes.html&lt;/A&gt;  release note from numpy end. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jan 2022 04:00:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32369#M23579</guid>
      <dc:creator>Atanu</dc:creator>
      <dc:date>2022-01-12T04:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject</title>
      <link>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32370#M23580</link>
      <description>&lt;P&gt;@Janani Mohan​&amp;nbsp;- Does the information that Atanu provided help?  If yes, would you be happy to mark it as best so that other members can find the solution more quickly?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2022 16:17:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32370#M23580</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-01-26T16:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject</title>
      <link>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32371#M23581</link>
      <description>&lt;P&gt;Hi @Janani Mohan​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you are doing well.&lt;/P&gt;&lt;P&gt;Just wanted to check in if you were able to resolve your issue or do you need more help? We'd love to hear from you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 15:21:36 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/valueerror-numpy-ndarray-size-changed-may-indicate-binary/m-p/32371#M23581</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-05-19T15:21:36Z</dc:date>
    </item>
  </channel>
</rss>

