+1 (binding). Tested the quickstart with the source and binary (Scala 2.12)
artifacts, ran the tests on the source artifact and verified some
signatures and hashes on source and binary (Scala 2.12) artifacts.
Thanks for managing this release Rajini!
On Sat, Nov 11, 2017 at 12:37 AM, Rajini Sivara
Hi Jamie,
You should be able to use something like this:
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
storeKey=true
keyTab="/etc/security/keytabs/kafka_server.keytab"
principal="kafka/kafka1.hostname@example.com";
};
or this:
Client {
Hi,
I am using Kafka 0.10.0 version. In this version, zookeeper is required.
Recently we found by default zookeeper allows anonymous connect to its port and
for some this seems to be a security concern. So I'd like to disable
zookeeper's ability to support anonymous connect. I am wondering if I
Thanks!
On 11/15/17 7:57 AM, Matt Farmer wrote:
> Yes, in memory stores are backed by a changelog topic as far as I'm aware.
> I have filed https://issues.apache.org/jira/browse/KAFKA-6214
>
> On Tue, Nov 14, 2017 at 10:53 PM Matthias J. Sax
> wrote:
>
>> Thanks for reporting.
>>
>> Sounds like
I have a very simple Kafka Local server implementation (Kafka 1.0.0)
package com.lightbend.kafka
import java.io.File
import java.io.IOException
import java.nio.file.FileVisitOption
import java.nio.file.Files
import java.nio.file.Paths
import java.util.Properties
import org.apache.curator.test.Te
Yes, in memory stores are backed by a changelog topic as far as I'm aware.
I have filed https://issues.apache.org/jira/browse/KAFKA-6214
On Tue, Nov 14, 2017 at 10:53 PM Matthias J. Sax
wrote:
> Thanks for reporting.
>
> Sounds like a bug to me. Please file a Jira.
>
> Question: even if you use
I am going through the kafka official tutorial, and met a weird problem at
multibroker part.
I will list what I have done briefly:
* run local zookeeper on port 2181
* run three kafka brokers on ports 9092, 9093, 9094
* created a topic with one partition and three replicas:
m
Thanks .. It works ..
On Wed, Nov 15, 2017 at 4:44 PM, Damian Guy wrote:
> Yes, right, that would be because the default serializer is set to bytes.
> Sorry i should have spotted that. Your Materialized should look something
> like:
>
> Materialized.as[String, java.lang.Long, KeyValueStore[Bytes
Yes, right, that would be because the default serializer is set to bytes.
Sorry i should have spotted that. Your Materialized should look something
like:
Materialized.as[String, java.lang.Long, KeyValueStore[Bytes,
Array[Byte]]](ACCESS_COUNT_PER_HOST_STORE)
.withKeySerde(Serdes.String())
Thank
It's not working fine .. I get the following exception during runtime ..
Exception in thread
> "kstream-weblog-processing-c37a3bc1-31cc-4ccc-8427-d51314802f64-StreamThread-1"
> java.lang.ClassCastException: java.lang.String cannot be cast to [B
> at
> org.apache.kafka.common.serialization.ByteArra
Hi,
That shouldn't be a problem, the inner most store is of type
`KeyValueStore`, however the outer store will be
`KeyValueStore`.
It should work fine.
Thanks,
Damian
On Wed, 15 Nov 2017 at 08:37 Debasish Ghosh
wrote:
> Hello -
>
> In my Kafka Streams 0.11 application I have the following tran
Hello -
In my Kafka Streams 0.11 application I have the following transformation ..
val hosts: KStream[Array[Byte], String] = logRecords.mapValues(record
=> record.host)
// we are changing the key here so that we can do a groupByKey later
val hostPairs: KStream[String, String] = host
12 matches
Mail list logo