On Sun, Oct 7, 2018 at 11:37 PM Konstantin Boudnik <[email protected]> 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 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?
The way I see this is two-fold:
1. it could be useful to have a standalone pacakge with all the jar
dependencies
so that any component of Bigtop stack to use that instead of
whatever comes through
Maven dependencies. This will be similar to how we standardize on
zookeper deps
and such.
2. it could be useful to provide binary scripts in that package that
would automate/facilitate
some of these kinds of steps:
http://avro.apache.org/docs/current/gettingstartedjava.html#Compiling+the+schema
http://avro.apache.org/docs/current/gettingstartedpython.html
http://avro.apache.org/docs/current/idl.html
and anything like that.
Do you have any other usecases in mind, Cos?
Thanks,
Roman.
