I agree with Stephen, it would be really unfortunate to see the Scala api
go away.
On Wed, Jan 28, 2015 at 11:57 AM, Stephen Boesch wrote:
> The scala API going away would be a minus. As Koert mentioned we could use
> the java api but it is less .. well .. functional.
>
> Kafka is included in t
Gary,
That is certainly a valid use case. What Zijing was saying is that you can
only have 1 consumer per consumer application per partition.
I think that what it boils down to is how you want your information grouped
inside your timeframes. For example, if you want to have everything for a
spe
ssages on the topic just directly insert into Cassandra then and avoid
> this extra hop?
>
>
>
> On 12 February 2015 at 09:01, David McNelis
> wrote:
>
> > Gary,
> >
> > That is certainly a valid use case. What Zijing was saying is that you
> can
> > only ha
; rework the design so that no consumer would assume it's getting all the
> messages in the topic.
>
> When you say central producer stack, this is something you built outside of
> kafka I assume.
>
> On 12 February 2015 at 09:40, David McNelis
> wrote:
>
> >
12, 2015 at 12:15 PM, Gary Ogden wrote:
> Thanks.
>
> I was under the impression that you can't process the data as each record
> comes into the topic? That Kafka doesn't support pushing messages to a
> consumer like a traditional message queue?
>
> On 12
G’day,
*Kafka_2.12-2.3.0 is the version I’m running and compiling for.
I’m a bit confused as to some of the behavior of building a custom
AuthenticateCallbackHandler implementation / extending the
PlainServerCallbackHandler. I have the following config:
sasl.enabled.mechanisms=PLAIN
sasl.mecha
G’day,
I’m a bit confused as to some of the behavior of building a custom
AuthenticateCallbackHandler implementation / extending the
PlainServerCallbackHandler. I have the following config:
sasl.enabled.mechanisms=PLAIN
sasl.mechanism.inter.broker.protocol=PLAIN
security.inter.broker.protoc
