You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:02 UTC
[jira] [Updated] (BEAM-12391) WriteToAvro fails if fastavro loads its python implementation of writer
[ https://issues.apache.org/jira/browse/BEAM-12391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-12391:
-----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> WriteToAvro fails if fastavro loads its python implementation of writer
> -----------------------------------------------------------------------
>
> Key: BEAM-12391
> URL: https://issues.apache.org/jira/browse/BEAM-12391
> Project: Beam
> Issue Type: Bug
> Components: io-py-avro
> Affects Versions: 2.25.0, 2.26.0, 2.27.0, 2.28.0, 2.29.0
> Reporter: Chris Chandler
> Assignee: John Casey
> Priority: P3
> Labels: starter
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> It's possible for fastavro to fail to correctly load its cython implementation of the Writer class in which case it will silently fall back to a pure python implementation. If this happens there's no outward indication, but line 621 in io/avroio.py will fail because writer.fo is only present on the cython implementation.
> To reproduce you can modify fastavro's write.py to only use its fallback:
> {code}
> #from . import _write
> from . import _write_py as _write
> {code}
> And then run a workflow that sinks to WriteToAvro(use_fastavro=True).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)