I lost a lot of time this morning debugging an issue that turned out to just be a trailing whitespace char at the end of an alias value. That seems like a good place to put extra validation in the record api; I can't imagine a legit use case where someone would intentionally put trailing or leading whitespaces in their aliases or name fields. Anyone see counter points on this? IMHO even if it's "legal Avro," I don't see a reason for us to be bound to that.
