Hello!

I'm looking for any discussion or reference why the Schema object isn't
serializable -- I'm pretty sure this must have already been discussed (but
the keywords +avro +serializable +schema have MANY results in all the
searches I did: JIRA, stack overflow, mailing list, web)

In particular, I was at a demo today where we were asked why Schemas needed
to be passed as strings to run in distributed tasks.  I remember running
into this problem years ago with MapReduce, and again in Spark, and again
in Beam...

Is there any downside to making a Schema implement java.lang.Serializable?
The only thing I can think of is that the schema _should not_ be serialized
with the data, and making it non-serializable loosely enforces this (at the
cost of continually writing different flavours of "Avro holders" for when
you really do want to serialize it).

Willing to create a JIRA and work on the implementation, of course!

All my best, Ryan

Reply via email to