Quilcate Otoya, Josep Prat, José
Armando García Sancio, Juan Gonzalez-Zurita, Jun Rao, Justin Mclean,
Justine Olshan, Kahn Cheny, Kalpesh Patel, Kamal Chandraprakash,
Konstantine Karantasis, Kowshik Prakasam, Leah Thomas, Lee Dongjin, Lev
Zemlyanov, Liu Qiang, Lucas Bradstreet, Luke Chen, Manikumar Reddy
github.com/izzyacademy/apache-kafka-release-party
>
> Please take a look at the resource and share any feedback that you may
> have.
>
> I plan to create a video tutorial that walks community members through how
> it can be used soon. Stay tuned
>
>
>
>
> On Wed, Sep 8
This vote passes with 6 +1 votes (out of which 4 binding votes) and no 0 or
-1 votes.
+1 votes
PMC Members:
* Bill Bejeck
* Colin McCabe
* Randall Hauch
* Konstantine Karantasis
Committers:
* No votes from additional committers
Community:
* Israel Ekpo
* Igor Soarez
0 votes
* No votes
-1
e release and the link for docs
> doesn't work.
>
> Thanks,
> Bill
>
> On Wed, Sep 8, 2021 at 5:59 PM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
> > Hello again Kafka users, developers and client-developers,
> >
> > This is the third candi
:34 PM Konstantine Karantasis <
kkaranta...@apache.org> wrote:
>
> Hello Kafka users, developers and client-developers,
>
> This is the second release candidate for Apache Kafka 3.0.0.
> It corresponds to a major release that includes many new features,
> including:
>
>
Hello again Kafka users, developers and client-developers,
This is the third candidate for release of Apache Kafka 3.0.0.
It is a major release that includes many new features, including:
* The deprecation of support for Java 8 and Scala 2.12.
* Kafka Raft support for snapshots of the metadata
, Aug 31, 2021 at 6:34 PM Konstantine Karantasis <
kkaranta...@apache.org> wrote:
>
> Hello Kafka users, developers and client-developers,
>
> This is the second release candidate for Apache Kafka 3.0.0.
> It corresponds to a major release that includes many new
Hello Kafka users, developers and client-developers,
This is the second release candidate for Apache Kafka 3.0.0.
It corresponds to a major release that includes many new features,
including:
* The deprecation of support for Java 8 and Scala 2.12.
* Kafka Raft support for snapshots of the
Congratulations Randall!
Konstantine
On Mon, Apr 19, 2021 at 1:14 AM Bruno Cadonna wrote:
> Congrats Randall! Well deserved!
>
> Bruno
>
> On 17.04.21 01:43, Matthias J. Sax wrote:
> > Hi,
> >
> > It's my pleasure to announce that Randall Hauch in now a member of the
> > Kafka PMC.
> >
> >
Congratulations Bill!
Konstantine
On Thu, Apr 8, 2021 at 2:42 AM Mickael Maison
wrote:
> Congratulations Bill!
>
> On Thu, Apr 8, 2021 at 10:06 AM David Jacot
> wrote:
> >
> > Congrats, Bill!
> >
> > On Thu, Apr 8, 2021 at 9:54 AM Tom Bentley wrote:
> >
> > > Congratulations Bill!
> > >
> >
Congratulations Bruno!
Konstantine
On Wed, Apr 7, 2021 at 8:08 PM Sophie Blee-Goldman
wrote:
> Congrats!
>
> On Wed, Apr 7, 2021 at 6:32 PM Luke Chen wrote:
>
> > Congrats Bruno!!
> >
> > Luke
> >
> > On Thu, Apr 8, 2021 at 9:18 AM Matthias J. Sax wrote:
> >
> > > Congrats Bruno! Very well
Well deserved! Congratulations Colin.
-Konstantine
On Wed, Sep 26, 2018 at 4:57 AM Srinivas Reddy
wrote:
> Congratulations Colin
>
> -
> Srinivas
>
> - Typed on tiny keys. pls ignore typos.{mobile app}
>
> On Tue 25 Sep, 2018, 16:39 Ismael Juma, wrote:
>
> > Hi all,
> >
> > The PMC for
Congrats Rajini!
-Konstantine
On Wed, Jan 17, 2018 at 2:18 PM, Becket Qin wrote:
> Congratulations, Rajini!
>
> On Wed, Jan 17, 2018 at 1:52 PM, Ismael Juma wrote:
>
> > Congratulations Rajini!
> >
> > On 17 Jan 2018 10:49 am, "Gwen Shapira"
You might find this connector useful for your use case:
https://github.com/jcustenborder/kafka-connect-cdc-mssql
Konstantine
On Tue, Dec 12, 2017 at 9:29 PM, harish reddy m
wrote:
> Hi Team,
>
> We have a requirement of replicating the data from MSSQL Source database
If I understand correctly, and your question refers to general fault
tolerance, the answer is yes, Kafka Connect offers fault tolerance in
distributed mode.
You may start several Connect workers and if a worker running one task with
your single producer fails unexpectedly, then this task will be
Indeed, there is no flattening operator in Kafka Connect's SMTs at the
moment. The 'apply' method in the Transformation interface accepts a single
record and returns another - transformed - record or null.
Konstantine.
On Wed, Dec 27, 2017 at 8:25 PM, Ziliang Chen wrote:
Have you tried the HDFS connector here?
https://github.com/confluentinc/kafka-connect-hdfs
Its master and 4.0.x branches contain export support for JSON in '.json'
text files.
Konstantine.
On Sat, Oct 28, 2017 at 11:51 PM, Alexander Atanasov <
alexandaratana...@gmail.com> wrote:
> Hello,
>
>
Are you producing any records after you start the consumer?
By default, Kafka consumer starts with auto.offset.reset == latest (
https://kafka.apache.org/documentation/#newconsumerconfigs), which means
that if the consumer doesn't find a previous offset for its consumer group
(e.g. the first time
Hi,
connector-plugins endpoint does not list the transformations classes
currently. However if you are using the latest Kafka version ( >= 0.11.0)
one way to see if your transform is discovered during startup in the given
classpath is to notice whether a log message such as the one below is
s to start up fine.
>
> i still wonder why its searching for gson. like... where does it get the
> idea for the start searching for gson? i dont use gson and neither does
> connect it seems?
>
> On Thu, Jul 6, 2017 at 8:09 PM, Konstantine Karantasis <
> konst
Hi Koert,
these warnings appear to be produced during the class scanning that Connect
is performing when it's starting up. Connect is using org.reflections to
discover plugins (Connectors, Transformations, Converters) in the various
locations that it's configured to search for plugins.
(such
nnect-log4j.properties
>
> log4j.rootLogger=INFO, stdout
>
> log4j.appender.stdout=org.apache.log4j.ConsoleAppender
> log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
> log4j.appender.stdout.layout.ConversionPattern=[%d] %p %m (%c)%n
>
> log4j.logger.org.reflections=INFO, stdout
> lo
Hi Stephane,
if you are using the docker images from confluent, a way to set the levels
to specific loggers is described here:
http://docs.confluent.io/3.1.1/cp-docker-images/docs/operations/logging.html#log4j-log-levels
For Connect, you would need to set the environment variable
Hi,
Still, the simplest way to do what you are asking for is to attach a remote
debugger (e.g. remote configuration in IntelliJ).
However to debug your Connector from the very start, you'll need to set in
addition the following two environment variables:
export KAFKA_DEBUG=y; export
The bug I was referring to was only in trunk for just a while. Thus, your
issue must be related to something else, even though the response statuses
are similar.
Let me know if you want to share a bigger and more detailed (DEBUG level at
least) snapshot of the parts of the logs that might be
Hi Phillip,
may I ask which Kafka version did you use?
trunk repo in Apache Kafka contained briefly a bug in Connect framework
(during the past week) that produced failures similar to the one you
describe (only in distributed mode). A fix has been pushed since yesterday.
3) Some useful
26 matches
Mail list logo