Guys, I want to bounce a question off the team: what would be the best way to bring Avro dependency into the stack? I don't think it deserves to be a separate component per se - after all it serves a niche purpose and doesn't stand on its own.
However, it makes sense to carry around in case an app needs such a serialization. I've been thinking of perhaps of packing it up as a Hadoop or HBase dependency, but it doesn't seem like the most straight forward idea, to be honest. Or may be we should introduce a separate helper package with serializers and such? What would be a preferred way from your stand point? -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing.
