`SerializableCoder` has the nice property of being able to encode and recover 
the identity of the class itself. I've done some testing with AvroCoder and it 
looks like that would limit us to picking a specific type. So an `IOException` 
would get encoded/decoded as `Exception`.

We could make exception type a parameter, so `Failure<T>` would become 
`Failure<E, V>`, but some exception subclasses don't provide a no-argument 
constructor, and thus would not be decodable by AvroCoder.

[ Full content available at: https://github.com/apache/beam/pull/6586 ]
This message was relayed via gitbox.apache.org for devnull@infra.apache.org

Reply via email to