Build failed in Jenkins: kafka-trunk-jdk8 #2956

See Changes: [lindong28] KAFKA-7096 : Clear buffered data for partitions that are explicitly -- [...truncated 2.36 MB...] org.apache.kafka.streams.test.OutputVerifierTest

Re: [DISCUSS] KIP-358: Migrate Streams API to Duration instead of long ms times

Hello, Guozhang, Bill. > 1) I'd suggest keeping `Punctuator#punctuate(long timestamp)` as is I am agree with you. Currently, `Punctuator` edits are not included in KIP. > 2) I'm fine with keeping KeyValueStore extending ReadOnlyKeyValueStore Great, currently, there is no suggested API change

Re: [EXTERNAL] [VOTE] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Looks great Randall +1 (non-binding) > On Sep 9, 2018, at 7:17 PM, Gwen Shapira wrote: > > +1 > Useful improvement, thanks Randall. > > > On Fri, Sep 7, 2018, 3:28 PM Randall Hauch wrote: > >> I believe the feedback on KIP-158 has been addressed. I'd like to start a >> vote. >> >> KIP: >>

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Hi Adam, give me some time, will make such a chart. last time i didn't get along well with giphy and ruined all your charts. Hopefully i can get it done today On 08.09.2018 16:00, Adam Bellemare wrote: Hi Jan I have included a diagram of what I attempted on the KIP.

Re: [ANNOUNCE] Kafka Committers Guidelines

Hello, guys. Can you, please, share non trivial tickets(improvement ideas) that waiting for a brave contributor? Which area of documentation needs to be improved? пн, 10 сент. 2018 г., 10:53 Dongjin Lee : > Comprehensive, Clear and Helpful. Thanks for your great work! > > Best, > Dongjin > >

Re: [VOTE] KIP-365: Materialized, Serialized, Joined, Consumed and Produced with implicit Serde

Ok, so this is now accepted. Binding votes: +5 Non-binding votes: +2 Thanks On Wed, 5 Sep 2018 at 21:38 John Roesler wrote: > Hi Joan, > > Damian makes 3 binding votes, and the vote has been open longer than 72 > hours, so your KIP vote has passed! > > It's customary for you to send a final

Re: [VOTE] KIP-354 Time-based log compaction policy

+1 (non binding) from on 0 then, and on the KIP. Where do we go from here? More votes? On Tue, Sep 11, 2018 at 5:34 AM Colin McCabe wrote: > On Mon, Sep 10, 2018, at 11:44, xiongqi wu wrote: > > Thank you for comments. I will use '0' for now. > > > > If we create topics through admin client in

Re: [EXTERNAL] [VOTE] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

+1 (non-binding) Thanks for the KIP! On Tue, Sep 11, 2018 at 8:40 AM McCaig, Rhys wrote: > > Looks great Randall > +1 (non-binding) > > > On Sep 9, 2018, at 7:17 PM, Gwen Shapira wrote: > > > > +1 > > Useful improvement, thanks Randall. > > > > > > On Fri, Sep 7, 2018, 3:28 PM Randall Hauch

Jenkins build is back to normal : kafka-trunk-jdk10 #468

See

Jenkins build is back to normal : kafka-trunk-jdk8 #2957

See

[jira] [Created] (KAFKA-7396) KIP-365: Materialized, Serialized, Joined, Consumed and Produced with implicit Serde

Joan Goyeau created KAFKA-7396: -- Summary: KIP-365: Materialized, Serialized, Joined, Consumed and Produced with implicit Serde Key: KAFKA-7396 URL: https://issues.apache.org/jira/browse/KAFKA-7396

Build failed in Jenkins: kafka-trunk-jdk10 #469

See -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

Re: [VOTE] KIP-310: Add a Kafka Source Connector to Kafka Connect

Hi All, Bumping this again. Can I get feedback from some binding vote holders on this KIP? I think its fairly straightforward KIP and worthwhile addition to Kafka Connect. Cheers, Rhys > On Sep 4, 2018, at 12:32 PM, McCaig, Rhys wrote: > > Bumping this thread. > >> On Aug 14, 2018, at

Jenkins build is back to normal : kafka-trunk-jdk10 #470

See

[jira] [Created] (KAFKA-7397) Ability to apply DSL stateless transformation on a global table

Frederic Tardif created KAFKA-7397: -- Summary: Ability to apply DSL stateless transformation on a global table Key: KAFKA-7397 URL: https://issues.apache.org/jira/browse/KAFKA-7397 Project: Kafka

[jira] [Created] (KAFKA-7402) Kafka Streams should implement AutoCloseable where appropriate

John Roesler created KAFKA-7402: --- Summary: Kafka Streams should implement AutoCloseable where appropriate Key: KAFKA-7402 URL: https://issues.apache.org/jira/browse/KAFKA-7402 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk10 #473

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

[jira] [Created] (KAFKA-7404) SourceConnector backpressure

Oleg Kuznetsov created KAFKA-7404: - Summary: SourceConnector backpressure Key: KAFKA-7404 URL: https://issues.apache.org/jira/browse/KAFKA-7404 Project: Kafka Issue Type: Improvement

Build failed in Jenkins: kafka-trunk-jdk8 #2959

See Changes: [jason] KAFKA-7044; Fix Fetcher.fetchOffsetsByTimes and NPE in describe consumer [wangguoz] KAFKA-7396: Materialized, Serialized, Joined, Consumed and Produced with

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

@Jun Rao I made the recent config changes after thinking about the default behavior for adopting this KIP. I think there are basically two options: 1. By default, the behavior proposed in this KIP is turned off, and operators can turn it on by adding the "controller.listener.name" config and

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Randall, I have some concerns with this proposal. Firstly, I don't believe it is the job of a connector to configure topics, generally, nor for topic-specific settings to hang out in connector configurations. Automatic creation of topics with default settings is an established pattern elsewhere,

[jira] [Created] (KAFKA-7403) Offset commit failure after broker upgrade to 2.0

Jon Lee created KAFKA-7403: -- Summary: Offset commit failure after broker upgrade to 2.0 Key: KAFKA-7403 URL: https://issues.apache.org/jira/browse/KAFKA-7403 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-362: Dynamic Session Window Support

Thanks for explaining your understanding. And thanks for providing more details about the use-case. Maybe you can add this to the KIP? First one general comment. I guess that my and Guozhangs understanding about gap/close/gracePeriod is the same as yours -- we might not have use the term

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Hi Ryanne, Thanks for the feedback! Can you explain a bit more what you mean by "if we allow connectors to make this decision, they should have full control of the process."? I assume you mean, something like: Rather than go though the connect framework, connectors should just create their own

[jira] [Resolved] (KAFKA-7386) Streams Scala wrapper should not cache serdes

[ https://issues.apache.org/jira/browse/KAFKA-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7386. -- Resolution: Fixed > Streams Scala wrapper should not cache serdes >

Jenkins build is back to normal : kafka-trunk-jdk10 #474

See

Build failed in Jenkins: kafka-trunk-jdk10 #475

See Changes: [github] KAFKA-3514: Part III, Refactor StreamThread main loop (#5428) [wangguoz] KAFKA-7386: streams-scala should not cache serdes (#5622) [github] KAFKA-3514, Documentations: Add out of ordering

Build failed in Jenkins: kafka-trunk-jdk8 #2958

See Changes: [github] MINOR: Missing throttle time in OffsetsForLeaderEpoch response (#5635) -- [...truncated 583.43 KB...] kafka.api.SaslSslAdminClientIntegrationTest >

Build failed in Jenkins: kafka-trunk-jdk8 #2960

See Changes: [github] KAFKA-3514: Part III, Refactor StreamThread main loop (#5428) [wangguoz] KAFKA-7386: streams-scala should not cache serdes (#5622) [github] KAFKA-3514, Documentations: Add out of ordering

How to setting https to the Kafka connector worker

Hi: I am using the Kafka connector version is 2.0.0 and below is setting the Kafka connector worker for https protocol. 1. Create the SSL key keytool -keystore kafka.server.keystore.jks -alias localhost -validity 365 -genkey openssl req -new -x509 -keyout ca-key -out ca-cert -days 365 keytool

[jira] [Resolved] (KAFKA-2194) Produce request failure after Kafka + Zookeeper restart

[ https://issues.apache.org/jira/browse/KAFKA-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2194. -- Resolution: Auto Closed Closing inactive issue. Please reopen if the issue still exists in newer

Re: [EXTERNAL] [VOTE] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

+1 (non binding) On Tue., 11 Sep. 2018, 10:48 am Mickael Maison, wrote: > +1 (non-binding) > Thanks for the KIP! > On Tue, Sep 11, 2018 at 8:40 AM McCaig, Rhys > wrote: > > > > Looks great Randall > > +1 (non-binding) > > > > > On Sep 9, 2018, at 7:17 PM, Gwen Shapira wrote: > > > > > > +1 >

[jira] [Created] (KAFKA-7399) FunctionConversions in Streams-Scala should be private

John Roesler created KAFKA-7399: --- Summary: FunctionConversions in Streams-Scala should be private Key: KAFKA-7399 URL: https://issues.apache.org/jira/browse/KAFKA-7399 Project: Kafka Issue

Speakers needed for Apache DC Roadshow

We need your help to make the Apache Washington DC Roadshow on Dec 4th a success. What do we need most? Speakers! We're bringing a unique DC flavor to this event by mixing Open Source Software with talks about Apache projects as well as OSS CyberSecurity, OSS in Government and and OSS Career

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Hi Guozhang Current highwater mark implementation would grow endlessly based on primary key of original event. It is a pair of (, ). This is used to differentiate between late arrivals and new updates. My newest proposal would be to replace it with a Windowed state store of Duration N. This would

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Hi all, after some time we updated KIP-302 to reuse the config key introduced by KIP-235, with a different value to avoid conflicts between the two. Also clarified the use of multiple IPs only of the same type (IPv4/IPv6). We'd appreciate a further review and discussion. Thanks! Edo On Fri, 25

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

please remove me from this group On Tue, Sep 11, 2018 at 1:29 PM Jan Filipiak wrote: > Hi Adam, > > give me some time, will make such a chart. last time i didn't get along > well with giphy and ruined all your charts. > Hopefully i can get it done today > > On 08.09.2018 16:00, Adam Bellemare

[jira] [Created] (KAFKA-7398) Transient test failure: SaslAuthenticatorFailureDelayTest.testInvalidPasswordSaslPlain

Manikumar created KAFKA-7398: Summary: Transient test failure: SaslAuthenticatorFailureDelayTest.testInvalidPasswordSaslPlain Key: KAFKA-7398 URL: https://issues.apache.org/jira/browse/KAFKA-7398

Re: [ANNOUNCE] Kafka Committers Guidelines

Search for tickets with labels "newbie", "newbie++", "beginner" or "docs" -Matthias On 9/11/18 12:48 AM, Nikolay Izhikov wrote: > Hello, guys. > > Can you, please, share non trivial tickets(improvement ideas) that waiting > for a brave contributor? > > Which area of documentation needs to be

[jira] [Created] (KAFKA-7401) Broker fails to start when recovering a segment from before the log start offset

Bob Barrett created KAFKA-7401: -- Summary: Broker fails to start when recovering a segment from before the log start offset Key: KAFKA-7401 URL: https://issues.apache.org/jira/browse/KAFKA-7401 Project:

Re: [DISCUSS] KIP-358: Migrate Streams API to Duration instead of long ms times

I talked to John offline about his last suggestions, that I originally did not fully understand. His proposal is, to deprecate existing methods on `ReadOnlyWindowStore` and `ReadOnlySessionStore` and add them to `WindowStore` and `SessionStore` (note, all singular -- not to be confused with

Re: [VOTE] KIP-365: Materialized, Serialized, Joined, Consumed and Produced with implicit Serde

I only count 3 binding votes (Guozhang, Matthias, Damian). Plus 4 non-binding (John, Ted, Bill, Dongjin) -- or 5 if you vote your own KIP :) -Matthias On 9/11/18 12:53 AM, Joan Goyeau wrote: > Ok, so this is now accepted. > > Binding votes: +5 > Non-binding votes: +2 > > Thanks > > On Wed, 5

[jira] [Resolved] (KAFKA-7044) kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors

[ https://issues.apache.org/jira/browse/KAFKA-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7044. Resolution: Fixed Fix Version/s: 2.0.1 1.1.2 >

[jira] [Created] (KAFKA-7400) Compacted topic segments that precede the log start offset are not cleaned up

Bob Barrett created KAFKA-7400: -- Summary: Compacted topic segments that precede the log start offset are not cleaned up Key: KAFKA-7400 URL: https://issues.apache.org/jira/browse/KAFKA-7400 Project:

Re: [VOTE] KIP-354 Time-based log compaction policy

Yes, more votes and code review. Xiongqi (Wesley) Wu On Mon, Sep 10, 2018 at 11:37 PM Brett Rann wrote: > +1 (non binding) from on 0 then, and on the KIP. > > Where do we go from here? More votes? > > On Tue, Sep 11, 2018 at 5:34 AM Colin McCabe wrote: > > > On Mon, Sep 10, 2018, at 11:44,

[jira] [Resolved] (KAFKA-7396) KIP-365: Materialized, Serialized, Joined, Consumed and Produced with implicit Serde

[ https://issues.apache.org/jira/browse/KAFKA-7396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7396. -- Resolution: Fixed > KIP-365: Materialized, Serialized, Joined, Consumed and Produced with >