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

See Changes: [jason] MINOR: Update docs for KIP-229 (#4499) -- [...truncated 410.76 KB...] kafka.log.LogCleanerIntegrationTest >

[jira] [Resolved] (KAFKA-6370) MirrorMakerIntegrationTest#testCommaSeparatedRegex may fail due to NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-6370. --- Resolution: Cannot Reproduce Although it's harmless to add some defensive checks, this issue should have not

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

On Thu, Jan 25, 2018, at 16:10, Colin McCabe wrote: > On Thu, Jan 25, 2018, at 02:23, Mickael Maison wrote: > > I'm late to the party but +1 and thanks for the KIP > > Thanks > > > > > On Thu, Jan 25, 2018 at 12:36 AM, Ismael Juma wrote: > > > Agreed, Jun. > > > > > > Ismael

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

See

Re: Please add me to the contributor list

Found the user ("Robert Yokota") and added to JIRA contributors. On Thu, Feb 1, 2018 at 4:58 PM Guozhang Wang wrote: > Hello Robert, > > What's your apache id? > > > Guozhang > > On Thu, Feb 1, 2018 at 4:37 PM, Robert Yokota wrote: > > > Hi, > > > > Can

[jira] [Created] (KAFKA-6522) Retrying leaderEpoch request for partition xxx as the leader reported an error: UNKNOWN_SERVER_ERROR

Wang Shuxiao created KAFKA-6522: --- Summary: Retrying leaderEpoch request for partition xxx as the leader reported an error: UNKNOWN_SERVER_ERROR Key: KAFKA-6522 URL: https://issues.apache.org/jira/browse/KAFKA-6522

[jira] [Resolved] (KAFKA-6492) LogSemgent.truncateTo() should always resize the index file

[ https://issues.apache.org/jira/browse/KAFKA-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6492. Resolution: Fixed Assignee: Jason Gustafson Fix Version/s: (was: 1.2.0)

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

Thanks. I updated the KIP accordingly and started work on the PR to see if this `To` interface work nicely. -Matthias On 2/1/18 4:00 PM, Ted Yu wrote: > Yeah. > Cleaner in this formation. > > On Thu, Feb 1, 2018 at 3:59 PM, Bill Bejeck wrote: > >> `To` works for me. >> >>

Re: Please add me to the contributor list

Hello Robert, What's your apache id? Guozhang On Thu, Feb 1, 2018 at 4:37 PM, Robert Yokota wrote: > Hi, > > Can someone please add me to the contributor list? I want to assign > KAFKA-2925 to myself so I can close it out. > > Thanks, > Robert Yokota > -- --

Please add me to the contributor list

Hi, Can someone please add me to the contributor list? I want to assign KAFKA-2925 to myself so I can close it out. Thanks, Robert Yokota

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

Yeah. Cleaner in this formation. On Thu, Feb 1, 2018 at 3:59 PM, Bill Bejeck wrote: > `To` works for me. > > Thanks, > Bill > > On Thu, Feb 1, 2018 at 6:47 PM, Matthias J. Sax > wrote: > > > @Paolo: > > > > The timestamp will be used to set the

Re: Vote for KIP-245: Use Properties instead of StreamsConfig in KafkaStreams constructor

I am closing this vote. The KIP is accepted with 3 non-binding (Ted, Bill, Satish) and 3 binding (Guozhang, Damian, Matthias) votes. Thanks a lot for the discussion and voting. -Matthias On 1/16/18 10:08 AM, Matthias J. Sax wrote: > ATM, StreamsConfig is immutable. Thus, it's just boiler

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

`To` works for me. Thanks, Bill On Thu, Feb 1, 2018 at 6:47 PM, Matthias J. Sax wrote: > @Paolo: > > The timestamp will be used to set the message/record metadata timestamp > on `Producer.send(new ProducerRecord(...,timestamp,...))`. > > @Bill,Ted: > > Might be a good

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

Don't forget to update the wiki page now that the vote has passed--it currently says this KIP is "under discussion": https://cwiki.apache.org/confluence/display/KAFKA/KIP-222+-+Add+Consumer+Group+operations+to+Admin+API Also, should the JIRA ticket be tagged with 1.1.0 (provided this is merged by

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

@Paolo: The timestamp will be used to set the message/record metadata timestamp on `Producer.send(new ProducerRecord(...,timestamp,...))`. @Bill,Ted: Might be a good idea. I was thinking about the name, and came up with `To`: > context.forward(key, value,

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

See Changes: [becket.qin] KAFKA-6489; Fetcher.retrieveOffsetsByTimes() should batch the metadata -- [...truncated 3.25 MB...] kafka.network.SocketServerTest >

[jira] [Created] (KAFKA-6521) Store record timestamps in KTable stores

Matthias J. Sax created KAFKA-6521: -- Summary: Store record timestamps in KTable stores Key: KAFKA-6521 URL: https://issues.apache.org/jira/browse/KAFKA-6521 Project: Kafka Issue Type:

Re: Kafka Consumers not rebalancing.

Any help would be appreciated! Hi All, I was experimenting on the new consumer API and have a question regarding the rebalance process. I start a consumer group with single thread and make the Thread sleep while processing the records retrieved from the first consumer.poll call, i was making

Jenkins build is back to normal : kafka-trunk-jdk7 #3142

See

Re: [DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets

Thanks James for sharing that scenario. I agree it makes sense to be able to remove offsets for the topics that are no longer "active" in the group. I think it becomes important to determine what constitutes that a topic is no longer active: If we use per-partition expiration we would manually

[jira] [Created] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

Michael Kohout created KAFKA-6520: - Summary: When a Kafka Stream can't communicate with the server, it's Status stays RUNNING Key: KAFKA-6520 URL: https://issues.apache.org/jira/browse/KAFKA-6520

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

See Changes: [becket.qin] KAFKA-6489; Fetcher.retrieveOffsetsByTimes() should batch the metadata -- [...truncated 412.13 KB...]

[jira] [Created] (KAFKA-6519) Change log level from ERROR to WARN for not leader for this partition exception

Antony Stubbs created KAFKA-6519: Summary: Change log level from ERROR to WARN for not leader for this partition exception Key: KAFKA-6519 URL: https://issues.apache.org/jira/browse/KAFKA-6519

[jira] [Resolved] (KAFKA-6499) Avoid creating dummy checkpoint files with no state stores

[ https://issues.apache.org/jira/browse/KAFKA-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6499. -- Resolution: Fixed Fix Version/s: 1.2.0 1.1.0 > Avoid creating dummy

[jira] [Resolved] (KAFKA-6489) Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata refresh topics set.

[ https://issues.apache.org/jira/browse/KAFKA-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-6489. - Resolution: Fixed > Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata >

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

Hi, They are few deployments using IPv6. It is good to support IPv6 also. I think KAFKA-5713 is about adding regular expression support to resource names (topic. consumer etc..). Yes, wildcards (*) in hostname doesn't makes sense. Range and subnet support will give us the flexibility. On Thu,

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

I like Bill's idea (pending a better name for the Forwarded). Cheers On Thu, Feb 1, 2018 at 7:47 AM, Bill Bejeck wrote: > Hi Matthias, > > Thanks for the KIP! > > Could we consider taking an approach similar to what was done in KIP-182 > with regards to overloading? > >

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

See

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

Hi Matthias, Thanks for the KIP! Could we consider taking an approach similar to what was done in KIP-182 with regards to overloading? Meaning we could add a "Forwarded" object (horrible name I know) with methods withTimestamp, withChildName, and withChildIndex. To handle the case when both a

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

See Changes: [github] Bump trunk versions to 1.2-SNAPSHOT (#4505) -- [...truncated 44.63 MB...] at com.sun.proxy.$Proxy74.onOutput(Unknown Source) at

[jira] [Created] (KAFKA-6518) Kafka broker get stops after configured log retention time and throws I/O exception in append to log

Rajendra Jangir created KAFKA-6518: -- Summary: Kafka broker get stops after configured log retention time and throws I/O exception in append to log Key: KAFKA-6518 URL:

[jira] [Resolved] (KAFKA-6516) KafkaProducer retries indefinitely to authenticate on SaslAuthenticationException

[ https://issues.apache.org/jira/browse/KAFKA-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar resolved KAFKA-6516. -- Resolution: Won't Fix thanks, [~rsivaram] so my expectation was invalid then > KafkaProducer

[jira] [Created] (KAFKA-6517) ZooKeeperClient holds a lock while waiting for responses, blocking shutdown

Rajini Sivaram created KAFKA-6517: - Summary: ZooKeeperClient holds a lock while waiting for responses, blocking shutdown Key: KAFKA-6517 URL: https://issues.apache.org/jira/browse/KAFKA-6517 Project:

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

Hi Manikumar, the current proposal indeed leaves out IPv6 addresses, as I was unsure whether Kafka fully supports that yet to be honest. But it would be fairly easy to add these to the proposal - I'll update it over the weekend. Regarding KAFKA-5713, I simply listed it as related, since it is

[jira] [Created] (KAFKA-6516) KafkaProducer retries indefinitely to authenticate on SaslAuthenticationException

Edoardo Comar created KAFKA-6516: Summary: KafkaProducer retries indefinitely to authenticate on SaslAuthenticationException Key: KAFKA-6516 URL: https://issues.apache.org/jira/browse/KAFKA-6516

New release branch 1.1

Hello Kafka developers and friends, We now have a release branch for the 1.1 release (with 1.1.0 as the version). Trunk has been bumped to 1.2.0-SNAPSHOT. I'll be going over the JIRAs to move every non-blocker from this release to the next release. >From this point, most changes should go to

Re: 1.1 release progress

Hi Guozhang and Damian, I have a couple of issues marked for 1.1.0 but the PR isn't reviewed since a long time and both of them should be ready. They are : KAFKA-5919 KAFKA-5532 Maybe you can

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

Hi, 1. Do we support IPv6 CIDR/ranges? 2. KAFKA-5713 is mentioned in Related JIRAs section. But there is no mention of wildcard support in the KIP. Thanks, On Thu, Feb 1, 2018 at 4:05 AM, Sönke Liebau < soenke.lie...@opencore.com.invalid> wrote: > Hey everybody, > > following a brief inital

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

Hi Matthias, just a question : what will be the timestamp "type" in the new message on the wire ? Thanks, Paolo. From: Matthias J. Sax Sent: Wednesday, January 31, 2018 2:06 AM To: dev@kafka.apache.org Subject: [DISCUSS] KIP-251: Allow

Re: [DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets

Vahid, Under rejected alternatives, we had decided that we did NOT want to do per-partition expiration, and instead we wait until the entire group is empty and then (after the right time has passed) expire the entire group at once. I thought of one scenario that might benefit from

[jira] [Created] (KAFKA-6515) Add toString() method to kafka connect Field class

Bartłomiej Tartanus created KAFKA-6515: -- Summary: Add toString() method to kafka connect Field class Key: KAFKA-6515 URL: https://issues.apache.org/jira/browse/KAFKA-6515 Project: Kafka