Flume package status for F21 and Rawhide
by Javi Roman
Hello I would like share with you the current status of Flume package.
Gil Cattaneo is working in many of the package dependencies, great
work!
The package builds with this assumptions (we are working on this issues):
1. The code is not ready for Thrift v0.9.1 available in Fedora 21,
however Flume code can builds using legacy Thrift built-in code
available in the upstream Flume TGZ.
2. Disable ElasticSearch Sink
3. Disable Morphline Solr Sink
4. Disable Twitter Source
5. Disable Kite Dataset Sink
In order to build Flume with full features those are the dependency
packages and status:
1. Package: irclib [https://bugzilla.redhat.com/show_bug.cgi?id=976049] (flume)
Pushed to the Fedora 21 testing repository.
2. Package: mapdb [https://bugzilla.redhat.com/show_bug.cgi?id=1178861] (flume)
submitted as an update for Fedora 21
3. Package: asynchbase (flume)
No added for revision in bugzilla.
4. Package: suasync (asynchbase)
No added for revision in bugzilla.
5. Package: parquet [https://bugzilla.redhat.com/show_bug.cgi?id=1073017] (kite)
Requesting review!
6. Package: parquet-format
[https://bugzilla.redhat.com/show_bug.cgi?id=1073014] (parquet)
Requesting review!
7. Package kite [https://bugzilla.redhat.com/show_bug.cgi?id=1179355] (flume)
The package need a patch in order to support Fedora Guava version.
8. maxmind-db-java [https://bugzilla.redhat.com/show_bug.cgi?id=1179309] (kite)
Pushed to the Fedora 21 testing repository.
9. Package ua-parser-java
[https://bugzilla.redhat.com/show_bug.cgi?id=1179342] (kite)
Pushed to the Fedora 21 testing repository.
Another question about default files in Flume package. Hortonworks and
Cloudera (Bigtop tools for packaging) are shipping default
configuration files in /etc/default, for example
/etc/default/flume-agent. I don't know if this is a good practice from
a Fedora packaging guidelines, what do you think?
A help with the package reviews are welcome!
Many thanks.
--
Javi Roman
9 years, 2 months
Advice about upstream using old libraries
by Javi Roman
Hello!
I'm working on some packages in my personal Github account [1] (Apache
Storm, Apache Kafka and Apache Flume). Maybe it could be useful for
this SIG when they are ready :-)
Meanwhile I have run into a problem and I need some advice:
The Apache Flume upstream code is using a old library (Apache Thrift
v0.8.0) however Fedora packages are using Apache Thrift 0.9.1 since
log time ago [2]. The problem is the v0.9.1 version breaks the
upstream building [3], and nobody is working in the issue right now.
The question is about the steps or procedure from a Fedora packager
point of view:
1. Try to fix the break code by myself, or working with the upstream
people in order to fix it (probably complex task).
2. Try to package the older version of the library and make it
available in the fedora packages repository.
any advice about this?
Many thanks!
[1] https://github.com/fedora-bigdata-rpms
[2] https://apps.fedoraproject.org/packages/thrift
[3] https://issues.apache.org/jira/browse/FLUME-2531
--
Javi Roman
es.linkedin.com/in/javiroman
9 years, 3 months