I commented on the issue. I don't believe this is a pyarrow bug. It is an artifact of having conflicting versions of pyarrow in the environment. My comment on the issue:
I think this might be due to conflicting versions of arrow in the notebook > environment? I believe this is caused by python-bigquery starting to rely > on Arrow 1.0.1 features > <https://github.com/googleapis/python-bigquery/commit/8209203e967f0624ad306166c0af6f6f1027c550> > <https://github.com/googleapis/python-bigquery/commit/8209203e967f0624ad306166c0af6f6f1027c550>Please > see jupyter/docker-stacks#944 > <https://github.com/jupyter/docker-stacks/issues/944> which seems to give > instructions for replacing a version of Arrow (a Kernel restart is needed). Thanks, Micah On Monday, September 21, 2020, Wes McKinney <wesmck...@gmail.com> wrote: > The patch https://github.com/apache/arrow/pull/7169 in theory should > not have broken downstream projects. Can someone open a JIRA issue? > > On Mon, Sep 21, 2020 at 8:39 PM BG Srinivas <chiya...@gmail.com> wrote: > > > > Hi > > > > Is this a known issue ? Is there a fix for this issue planned on 1.0.1 ? > > > > https://github.com/GoogleCloudPlatform/python-docs-samples/issues/4573 < > https://github.com/GoogleCloudPlatform/python-docs-samples/issues/4573> > > > > Thanks > > BG Srinivas >
