[
https://issues.apache.org/jira/browse/AVRO-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042646#comment-17042646
]
Erik Erlandson commented on AVRO-2748:
--------------------------------------
[~kojiromike] thanks for the heads up about py3! I'll have to move my dev on
AVRO-2474 to 'py'.
I'm not sure how to visibly reproduce besides adding print statements, but you
can see that the 'match_schemas' method is called in 'read_data' here:
[https://github.com/apache/avro/blob/master/lang/py/avro/io.py#L669]
And that's called, for example, on each iteration of '__next__':
[https://github.com/apache/avro/blob/master/lang/py/avro/datafile.py#L336]
> py3 schema resolution occurs on every read
> ------------------------------------------
>
> Key: AVRO-2748
> URL: https://issues.apache.org/jira/browse/AVRO-2748
> Project: Apache Avro
> Issue Type: Bug
> Components: python
> Affects Versions: 1.9.2
> Reporter: Erik Erlandson
> Priority: Minor
>
> In python, the schema resolution appears to be happening on each read
> operation. I'm not an avro expert but in my perusing through the py3 io code
> I haven't yet noticed a reason that the schema resolution couldn't happen
> once up front, during the construction of DataFileReader, when it first loads
> the write_schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
