; error. It could help identify what the problem is
more easily when debugging clients.
Of course, this is the kind of lever one would prefer never pulling, but when
you need it, you're better off having it than not, and if you end up having it
and never using it, it does not do much harm either
tretch for Voldemort to depend on all of Kafka
(or even Kafka clients...). The fork was just to iterate quicker at the
time we needed this, but it would be nice to bring it back together.
Let me know if I can help in any way.
--
*Felix GV*
Senior Software Engineer
Data Infrastructure
LinkedIn
f...@li
IMHO, I think Camus should probably be decoupled from Avro before the
simpler contribs are deleted.
We don't actually use the contribs, so I'm not saying this for our sake,
but it seems like the right thing to do to provide simple examples for this
type of stuff, no...?
--
Felix
On Wed, Jul 3,
The contrib code is simple and probably wouldn't require too much work to
fix, but it's a lot less robust than Camus, so you would ideally need to do
some work to make it solid against all edge cases, failure scenarios and
performance bottlenecks...
I would definitely recommend investing in Camus
Thanks Jun!
I hadn't been following the discussions regarding 0.8 and replication for a
little while and this was a great post to refresh my memory and get up to
speed on the current replication architecture's design.
--
Felix
On Tue, Feb 5, 2013 at 2:21 PM, Jun Rao wrote:
> I just posted the
[
https://issues.apache.org/jira/browse/KAFKA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139784#comment-15139784
]
Felix GV commented on KAFKA-2750:
-
Shouldn't the producer automatically do a
[
https://issues.apache.org/jira/browse/KAFKA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556958#comment-13556958
]
Felix GV commented on KAFKA-260:
It would be possible to have optional timestamps by u
