Jenkins build is back to normal : kafka-trunk-jdk11 #663

See

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

See Changes: [wangguoz] KAFKA-8356: add static membership info to round robin assignor (#6815) [wangguoz] KAFKA-8538 (part of KIP-345): add group.instance.id to DescribeGroup --

Re: [DISCUSS] KIP-477: Add PATCH method for connector config in Connect REST API

Thank you for your feedback Ryanne! These are all surely valid concerns and PATCH isn't really necessary or suitable for normal production configuration management. However, there are cases where quick patching of the configuration is useful, such as hot fixes of production or in development. Over

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hi George, I think we might want to move the discussion to KIP-455 as this KIP is very tightly coupled to it. One issue I see is when controller failover occurs, the new controller > will need to read the active reassignments by scanning the > /brokers/topics//, for some clusters with hundred+

[jira] [Created] (KAFKA-8611) Make topic optional when using through() operations in DSL

Levani Kokhreidze created KAFKA-8611: Summary: Make topic optional when using through() operations in DSL Key: KAFKA-8611 URL: https://issues.apache.org/jira/browse/KAFKA-8611 Project: Kafka

[DISCUSS] KIP-485 Make topic optional when using through() operations in DSL

Hello, I would like to start discussion about KIP-485 Make topic optional when using through() operations in DSL Regards, Levani

[jira] [Created] (KAFKA-8612) Broker removes consumers from CG, Streams app gets stuck

Di Campo created KAFKA-8612: --- Summary: Broker removes consumers from CG, Streams app gets stuck Key: KAFKA-8612 URL: https://issues.apache.org/jira/browse/KAFKA-8612 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8613) Set default grace period to 0

Bruno Cadonna created KAFKA-8613: Summary: Set default grace period to 0 Key: KAFKA-8613 URL: https://issues.apache.org/jira/browse/KAFKA-8613 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP-213: Second follow-up on Foreign Key Joins

Hi Matthias Yes, thanks for the questions - I know it's hard to keep up with all of the various KIPs and everything. The instructions are not stored anywhere, but are simply a way of letting the RHS know how to handle the subscription and reply accordingly. The only case where we send an unneces

Re: [DISCUSS] KIP-213: Second follow-up on Foreign Key Joins

Just some thoughts around the versioning. I'm trying to work out a more elegant way to handle it than what I've come up with so far below. *1) I'm planning to use an enum for the versions, but I am not sure how to tie the versions to any particular release. For instance, something like this is do

Re: [DISCUSS] KIP-435: Internal Partition Reassignment Batching

Hey there Viktor, Thanks for working on this KIP! I agree with the notion that reliability, stability and predictability of a reassignment should be a core feature of Kafka. Let me first explicitly confirm my understanding of the configs and the algorithm: * reassignment.parallel.replica.count -

Re: [DISCUSS] KIP-485 Make topic optional when using through() operations in DSL

Levani, Thanks for the KIP! As mentioned on the Jira, I think we should discard this KIP and subsume it in KIP-221. Nobody is actively working on KIP-221, so feel free to pick it up and we move the discussion to the other thread. -Matthias On 6/28/19 2:58 AM, Levani Kokhreidze wrote: > Hello, >

[jira] [Created] (KAFKA-8614) Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs

Bob Barrett created KAFKA-8614: -- Summary: Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs Key: KAFKA-8614 URL: https://issues.apache.org/jira/browse/KAFKA-8614 Proje

Re: [VOTE] KIP-429: Kafka Consumer Incremental Rebalance Protocol

It is now! Also updated the KIP to reflect that we will be adding a new CooperativeStickyAssignor rather than making the existing StickyAssignor cooperative to prevent users who already use the StickyAssignor from blindly upgrading and hitting potential problems during a rolling bounce On Thu, Jun

Re: Request for Permission to Create KIP

Hi, Maulin, Thanks for your interest. Just gave you the wiki permission. Jun On Thu, Jun 27, 2019 at 7:16 PM Maulin Vasavada wrote: > Hi > > Can you please give me permission to Create KIP? > > My username: maulin.vasavada > > Thank you. > Maulin >

Re: [DISCUSS] KIP-478 Strongly Typed Processor API

Sorry for coming late to the party. As for the naming I'm in favor of RecordProcessor as well. I agree that we should not take on doing all of the package movements as part of this KIP, especially as John has pointed out, it will be an opportunity to discuss some clean-up on individual classes wh

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

See Changes: [github] MINOR: Add compatibility tests for 2.3.0 (#6995) -- [...truncated 2.55 MB...] org.apache.kafka.connect.json.JsonConverterTest > stringHeaderToConnec

[jira] [Created] (KAFKA-8615) Change to track partition time breaks TimestampExtractor

Bill Bejeck created KAFKA-8615: -- Summary: Change to track partition time breaks TimestampExtractor Key: KAFKA-8615 URL: https://issues.apache.org/jira/browse/KAFKA-8615 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-8492) Modify ConsumerCoordinator Algorithm with incremental protocol (part 2)

[ https://issues.apache.org/jira/browse/KAFKA-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8492. Resolution: Fixed Fix Version/s: 2.4.0 > Modify ConsumerCoordinator Algorithm with i

Re: [DISCUSS] KIP-213: Second follow-up on Foreign Key Joins

Woah. It's your turn to make my head hurt! I think we can make one simplifying assumption: we will probably never need a second version. We're just hedging in case we do. Recursively, if we need a second one, then we'll probably never need a third one, etc. In other words, I wouldn't worry too muc

Re: [DISCUSS] KIP-480 : Sticky Partitioner

Hi all, I made some changes to the KIP. The idea is to clean up the code, make behavior more explicit, provide more flexibility, and to keep default behavior the same. Now we will change the partition in onNewBatch, and specify the conditions for this function call (non-keyed values, no explicit p

[jira] [Created] (KAFKA-8616) Replace ApiVersionsRequest request/response with automated protocol

Boyang Chen created KAFKA-8616: -- Summary: Replace ApiVersionsRequest request/response with automated protocol Key: KAFKA-8616 URL: https://issues.apache.org/jira/browse/KAFKA-8616 Project: Kafka

Build failed in Jenkins: kafka-2.3-jdk8 #57

See Changes: [cmccabe] MINOR: add upgrade text (#7013) -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-2 (ubuntu trus

Re: [DISCUSS] KIP-484: Expose metrics for group and transaction metadata loading duration

Hey, Thank you for proposing this! Sounds really useful - we have definitely seem some difficult to explain pauses in consumer activity and this metric will let us correlate those. Few questions: 1. Did you consider adding both Max and Avg metrics? Many of our metrics have both (batch-size and me

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

See

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

See Changes: [bbejeck] remove cs (#6950) -- [...truncated 2.55 MB...] org.apache.kafka.connect.util.KafkaBasedLogTest > testReloadOnStartWithNoNewRecordsPresent STARTED