Did this mailing list ever get created? Was there consensus that it did or
didn't need created?
-Mark
> On Jul 18, 2014, at 14:34, Jay Kreps wrote:
>
> A question was asked in another thread about what was an effective way
> to contribute to the Kafka project for people who weren't very
> enth
Hi all,
As a client engineer on the python client, I would really appreciate a
separate mailing list for client implementation discussion and a language
agnostic test suite. What might also be really useful is an enumerated
list of error conditions and the expected behavior to come out of them.
The certified client test suite really will benefit all the client developers,
as writing a Kafka client often is not just talking protocol but to be able to
handle correctly all the cases, errors and situations, but also performance.
From my experience writing a C# client definitely feel that a
Basically my thought with getting a separate mailing list was to have
a place specifically to discuss issues around clients. I don't see a
lot of discussion about them on the main list. I thought perhaps this
was because people don't like to ask questions which are about
adjacent projects/code base
Another important part of eco-system could be around the adaptors of
getting data from other systems into Kafka and vice versa. So, for the
ingestion part, this can include things like getting data from mysql,
syslog, apache server log, etc. For the egress part, this can include
putting Kafka data
A question was asked in another thread about what was an effective way
to contribute to the Kafka project for people who weren't very
enthusiastic about writing Java/Scala code.
I wanted to kind of advocate for an area I think is really important
and not as good as it could be--the client ecosyste
