[jira] [Created] (KAFKA-6470) no continuous offset for function seek

chao.wu created KAFKA-6470: -- Summary: no continuous offset for function seek Key: KAFKA-6470 URL: https://issues.apache.org/jira/browse/KAFKA-6470 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6469) ISR change notification queue has a maximum size

Kyle Ambroff-Kao created KAFKA-6469: --- Summary: ISR change notification queue has a maximum size Key: KAFKA-6469 URL: https://issues.apache.org/jira/browse/KAFKA-6469 Project: Kafka Issue

[jira] [Created] (KAFKA-6468) Replication high watermark checkpoint file read for every LeaderAndIsrRequest

Kyle Ambroff-Kao created KAFKA-6468: --- Summary: Replication high watermark checkpoint file read for every LeaderAndIsrRequest Key: KAFKA-6468 URL: https://issues.apache.org/jira/browse/KAFKA-6468

Build failed in Jenkins: kafka-trunk-jdk7 #3110

See Changes: [wangguoz] MINOR: increase timeout for unstable [me] MINOR: Add async and different sync startup modes in connect service -- [...truncated 1.89 MB...]

Re: [VOTE] KIP-145: Expose Record Headers in Kafka Connect

+1 (binding) Just one minor comment. It seems a little surprising that HeaderConverter does not use the Header interface. I expected something like this: Header toConnectHeader(String topic, String headerKey, byte[] value); byte[] fromConnectHeader(String topic, Header header); Was there a

[jira] [Resolved] (KAFKA-6466) Kafka connect task sometimes fails on start-up

[ https://issues.apache.org/jira/browse/KAFKA-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-6466. -- Resolution: Duplicate > Kafka connect task sometimes fails on start-up >

Build failed in Jenkins: kafka-trunk-jdk9 #324

See Changes: [me] MINOR: Add async and different sync startup modes in connect service -- [...truncated 1.86 MB...]

Re: [VOTE] KIP-145: Expose Record Headers in Kafka Connect

+1 On Mon, Jan 22, 2018 at 2:48 PM, Gwen Shapira wrote: > +1 (binding) > > This is going to be HUGE! Thank you Randall. > > On Mon, Jan 22, 2018 at 1:18 PM Konstantine Karantasis < > konstant...@confluent.io> wrote: > > > Great addition! > > > > +1 (non-binding) > > > >

Build failed in Jenkins: kafka-trunk-jdk7 #3109

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

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

> > What if we want to have fetch sessions for non-incremental fetches in the > future, though? Also, we don't expect this configuration to be changed > often, so it doesn't really need to be short. Hmm.. But in that case, I'm not sure we'd need to distinguish the two cases. If the

[VOTE] KIP-212: Enforce set of legal characters for connector names

All, this KIP has been discussed for quite some time now and I believe we addressed all major concerns in the current revision, so I'd like to start a vote. KIP can be found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-212%3A+Enforce+set+of+legal+characters+for+connector+names

Build failed in Jenkins: kafka-trunk-jdk7 #3108

See Changes: [wangguoz] MINOR: update docs with regard to improved resilience of Kafka Streams -- [...truncated 1.90 MB...]

[jira] [Created] (KAFKA-6467) Enforce layout of dependencies within a Connect plugin to be deterministic

Konstantine Karantasis created KAFKA-6467: - Summary: Enforce layout of dependencies within a Connect plugin to be deterministic Key: KAFKA-6467 URL: https://issues.apache.org/jira/browse/KAFKA-6467

Build failed in Jenkins: kafka-trunk-jdk9 #323

See Changes: [wangguoz] MINOR: update docs with regard to improved resilience of Kafka Streams [wangguoz] MINOR: increase timeout for unstable -- [...truncated 1.86

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

On Mon, Jan 22, 2018, at 15:42, Jason Gustafson wrote: > Hi Colin, > > This is looking good to me. A few comments: > > 1. The fetch type seems unnecessary in the request and response schemas > since it can be inferred by the sessionId/epoch. Hi Jason, Fair enough... if we need it later, we can

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

Hi Colin, This is looking good to me. A few comments: 1. The fetch type seems unnecessary in the request and response schemas since it can be inferred by the sessionId/epoch. 2. I agree with Jun that a separate array for partitions to remove would be more intuitive. 3. I'm not super thrilled

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

See Changes: [wangguoz] MINOR: update docs with regard to improved resilience of Kafka Streams [wangguoz] MINOR: increase timeout for unstable [me] MINOR: Add async and different sync startup modes in connect

Re: [VOTE] KIP-229: DeleteGroups API

+1 (binding) On Mon, Jan 22, 2018 at 11:06 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Bumping this thread as this KIP requires only one more binding +1 to make > it to 1.1.0. > > Thanks. > --Vahid > > > > From: "Vahid S Hashemian" > To:

Re: [VOTE] KIP-145: Expose Record Headers in Kafka Connect

+1 (binding) This is going to be HUGE! Thank you Randall. On Mon, Jan 22, 2018 at 1:18 PM Konstantine Karantasis < konstant...@confluent.io> wrote: > Great addition! > > +1 (non-binding) > > Konstantine > > On Sun, Jan 21, 2018 at 7:26 PM, Ewen Cheslack-Postava > wrote: > >

[jira] [Resolved] (KAFKA-3988) KafkaConfigBackingStore assumes configs will be stored as schemaless maps

[ https://issues.apache.org/jira/browse/KAFKA-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3988. -- Resolution: Won't Fix Not going to fix since KIP-174 is deprecating the

Re: [DISCUSS] Release Plan for 1.0.1

Jeff, The initial email was just to get people looking at JIRAs. We still have one outstanding blocker, and Guozhang's PR has already been merged. Otherwise we have no blockers, but there are a couple marked "Critical" that are unresolved. I'll be following up on those JIRAs to get them either

Re: [VOTE] KIP-145: Expose Record Headers in Kafka Connect

Great addition! +1 (non-binding) Konstantine On Sun, Jan 21, 2018 at 7:26 PM, Ewen Cheslack-Postava wrote: > +1 (binding) > > Thanks for the work on this -- not a small upgrade to the Connect APIs! > > -Ewen > > On Fri, Jan 19, 2018 at 3:37 PM, Randall Hauch

Re: [VOTE] KIP-208: Add SSL support to Kafka Connect REST interface

Hi all, I will close the vote for this KIP. It received 4 binding +1 votes and is now approved. Thanks to everyone for voted and discussed this. The PR for this KIP is at https://github.com/apache/kafka/pull/4429 Thanks & Regards Jakub On Sat, Jan 20, 2018 at 12:07 AM, Jakub Scholz

Re: [DISCUSS] Release Plan for 1.0.1

Any update on this release? Haven't seen anything other than Guozhang's email... Waiting for it to drop so we can upgrade to 1.0 series... On Tue, Jan 16, 2018 at 1:32 PM, Guozhang Wang wrote: > Hello Ewen, > > Could you include one more notable changes in 1.0.1: >

Re: [VOTE] KIP-231: Improve the Required ACL of ListGroups API

And this one requires two more binding +1's :) Thanks. From: Ewen Cheslack-Postava To: dev@kafka.apache.org Date: 01/02/2018 09:50 PM Subject:Re: [VOTE] KIP-231: Improve the Required ACL of ListGroups API +1 (binding) Thanks for the KIP Vahid, nice

Re: [VOTE] KIP-229: DeleteGroups API

Bumping this thread as this KIP requires only one more binding +1 to make it to 1.1.0. Thanks. --Vahid From: "Vahid S Hashemian" To: dev@kafka.apache.org Date: 01/16/2018 10:41 AM Subject:Re: [VOTE] KIP-229: DeleteGroups API Thanks Colin. Your

Re: [VOTE] KIP-219 - Improve Quota Communication

Thanks for the discussion and voting. KIP-219 has passed with +3 binding votes (Becket, Jun, Rajini). On Thu, Jan 18, 2018 at 1:32 AM, Rajini Sivaram wrote: > Hi Becket, > > Thanks for the update. Yes, it does address my concern. > > +1 (binding) > > Regards, > >

Re: [VOTE] KIP-248: Create New ConfigCommand That Uses The New AdminClient

Hi all, I'd like to ask the dev community to vote on this KIP as the KIP freeze is very close (tomorrow) and this would be a relevant feature (mostly from the usability side) for KIP-226: Dynamic Broker Configuration

Re: offsetsForTimes API performance

Speaking of, has there been any talk of combining those two requests into a single API call? I’d assume that offsetForTimes + consumer seek is probably the most common use case of offsetForTimes. Maybe a round trip could be avoided if the broker could just auto-assign the consumer to the offset

offsetsForTimes API performance

Hi all, We use kafka as our store and every one of our record is associated with a timeStamp. We pull data from kafka by seeking to a timeStamp offset everytime and then get the records by polling. We use KafkaConsumer's offsetsForTimes (

[jira] [Created] (KAFKA-6466) Kafka connect task sometimes fails on start-up

Alexander Koval created KAFKA-6466: -- Summary: Kafka connect task sometimes fails on start-up Key: KAFKA-6466 URL: https://issues.apache.org/jira/browse/KAFKA-6466 Project: Kafka Issue Type:

Re: [VOTE] KIP-222 - Add "describe consumer group" to KafkaAdminClient

My bad, KIP is updated: ``` public class MemberDescription { private final String consumerId; private final String clientId; private final String host; private final MemberAssignment assignment; } public class MemberAssignment { private final List assignment; } ``` Cheers,