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 ap
A serde package seems to be a right choice for me.
But I'm gonna ask in another angle: What's your use case? If we have a
specific use case to support, we have better chance to keep it on track
from release to release.
Konstantin Boudnik 於 2018年10月8日 週一 上午2:07寫道：
> Guys,
>
> I want to bounce a q
On Sun, Oct 7, 2018 at 11:37 PM Konstantin Boudnik wrote:
>
> 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 st
Thanks guys, something along these lines were forming in the back of
my head. Good to see sketchy thinking is sensible.
The use-case is pretty straight-forward: let the applications on top
of the stack to read/write Avro format to HBase (or else) without a
need to bundle the serde dependency in eac
