Fixes and Enhancements in LinkedIn Camus never came across when Confluent Fork made

[michaelandrepearce]

It seems confluent fork is not containing many fixes and enhancements made in the linkedin repository. This makes migration from linkedin camus to confluent camus problematic if dependant on these.

As Confluent repo now seems to become the defecto maintainer need to ensure improvements made in linkedin are migrated across.

in my particular case affects our migration:
LinkedInAttic/camus@1fe6098

[michaelandrepearce]

It seems if whom ever owns this fork should be able to do this with relative ease
http://www.hpique.com/2013/09/updating-a-fork-directly-from-github/

[miguno]

Michael André Pearce (@michaelandrepearce):

As Confluent repo now seems to become the defecto maintainer need to ensure improvements made in linkedin are migrated across.

Unfortunately, we are not (and also don't see ourselves as) the de-facto maintainer of LinkedIn Camus. While we have been packaging Camus as part of the Confluent Platform, and have also been collaborating with the Camus project, we have not taken over the maintenance of Camus -- nor are we planning to.

In fact, the latest version of the Confluent Platform (v3.0.0) even deprecates Camus:

Deprecated since version 3.0.0: Camus in Confluent Platform is deprecated in Confluent Platform 3.0 and may be removed in a release after Confluent Platform 3.1. To export data from Kafka to HDFS and Hive, we recommend Kafka Connect with the Confluent HDFS connector as an alternative.

See http://docs.confluent.io/3.0.0/camus/docs/intro.html.