Re: [DISCUSS] KIP-108: Create Topic Policy

where there is a separate endpoint <https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/resources/ConnectorPluginsResource.java#L49-L58> to attempt to validate a connect configuration without actually creating the connector. than

Re: [VOTE] KIP-151: Expose Connector type in REST API (first attempt :)

here we are, only 72hrs later and we have reached agreement. +4 binding from Guozhang, Ismael, Ram, and Ewen. +2 non binding from Bharat and Konstantine. thanks everyone who voted/commented. dan On Wed, May 10, 2017 at 11:38 AM, Guozhang Wang <wangg...@gmail.com> wrote: > +1 > &

Re: [VOTE] KIP-146: Isolation of dependencies and classes in Kafka Connect (restarted voting thread)

+1 (non binding) thanks Konstantine :thumbsup: On Mon, May 8, 2017 at 3:24 PM, Guozhang Wang wrote: > +1 > > On Mon, May 8, 2017 at 1:36 PM, Stephane Maarek < > steph...@simplemachines.com.au> wrote: > > > +1 > > Thanks heaps I can’t wait! > > > > > > On 9/5/17, 4:48 am,

Re: [DISCUSS] KIP 151 - Expose Connector type in REST API

thanks for the feedback, it all sounds good. i have made the changes to the pr and the kip. dan On Fri, May 5, 2017 at 9:29 AM, Konstantine Karantasis < konstant...@confluent.io> wrote: > Thank you for the KIP. It's a nice improvement. > > Two small suggestions: > > 1) L

[DISCUSS] KIP 151 - Expose Connector type in REST API

://github.com/apache/kafka/pull/2960 thanks dan

[VOTE] KIP-151: Expose Connector type in REST API (first attempt :)

thread will stay active for a minimum of 72 hours. thanks dan

Re: [DISCUSS] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

for another kip. dan On Thu, May 4, 2017 at 2:36 PM, Colin McCabe <cmcc...@apache.org> wrote: > On Thu, May 4, 2017, at 13:46, Magnus Edenhill wrote: > > Hey Colin, > > > > good KIP! > > > > Some comments: > > > > 1a. For operation, permission_type an

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

updated to be more explicit On Mon, Dec 4, 2017 at 9:55 AM, Ted Yu <yuzhih...@gmail.com> wrote: > In the example, resources is derived from ConfigResource. > It would be clearer if you show the derivation. > > Cheers > > On Mon, Dec 4, 2017 at 9:51 AM, dan <dan.norw..

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

I added sample usage as well as a WIP commit to the KIP. dan On Mon, Dec 4, 2017 at 9:36 AM, Ted Yu <yuzhih...@gmail.com> wrote: > Can you add some code snippet showing how ConfigResource delivers topic > defaults with the proposed change ? > > > Cheers > > On Mon,

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

Dong, i added a section on current state and workarounds along with my arguments for why they are less than optimal to the wiki. but the jist of it is you can end up with messages in your topic in an incorrect/invalid state if you do this. thanks, dan On Mon, Dec 4, 2017 at 10:53 AM, Dong Lin

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

updated again :) by having users always set all configs you lose the ability to use the broker defaults as intended, since topic configs are overlaid. example in the kip doc. dan On Mon, Dec 4, 2017 at 11:47 AM, Dong Lin <lindon...@gmail.com> wrote: > Hey Dan, > > Thanks for the

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

for topics. right now a user is left to either decide configs a priori and lose this functionality, or guess/check what they need to set and end in a possibly bad situation until they can get their *live* topic configured. dan On Mon, Dec 4, 2017 at 2:50 PM, Dong Lin <lindon...@gmail.com> wrote:

[DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

I would like to start a discussion about KIP-234 https://cwiki.apache.org/confluence/display/KAFKA/KIP-234%3A+add+support+for+getting+topic+defaults+from+AdminClient thanks dan

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

this info for all describeTopics() calls. not sure of the ramifications/overhead here. dan On Wed, Dec 13, 2017 at 10:10 AM, Colin McCabe <cmcc...@apache.org> wrote: > On Wed, Dec 13, 2017, at 10:00, dan wrote: > > > Why not just return > > > org.apache.kafk

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

eplica mappings it would create (i have no idea if this is actually possible) dan On Wed, Dec 13, 2017 at 9:55 AM, Colin McCabe <cmcc...@apache.org> wrote: > On Tue, Dec 12, 2017, at 19:02, Ewen Cheslack-Postava wrote: > > re: API versions, I actually wasn't sure if we neede

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

Colin/Ewen, i will add changes to bump the API version. any preferences on the return type for the new method? tbh it seems like returning a NewTopic could make sense because the ConfigResource for a TOPIC type does not let me encode `numPartitions` thanks dan On Mon, Dec 11, 2017 at 7:22 PM

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

Jorge, Would you consider also adding `listGroupOffsets` to this KIP? thanks dan On Tue, Dec 12, 2017 at 9:39 AM, Jason Gustafson <ja...@confluent.io> wrote: > Hi Colin, > > They do share the same namespace. We have a "protocol type" field in the > JoinGroup r

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

in the KIP, another option would be to have the `CreateTopicsOptions.validateOnly=true` version return data, but seems more invasive/questionable. dan On Wed, Dec 6, 2017 at 5:10 AM, Rajini Sivaram <rajinisiva...@gmail.com> wrote: > Hi Dan, > > Thank you for the KIP. KIP-226 (https://c

Re: [DISCUSS] KIP-234: add support for getting topic defaults from AdminClient

better for them. since the person maintaining the actual cluster has put thought in to this config. and as the maintainer keeps working on making the cluster run better they can change and tune things on the cluster level as needed. dan On Wed, Dec 6, 2017 at 11:51 AM, Dong Lin <lin

Re: [VOTE] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

After 80 hours, the results of the voting: +3 binding +1 non-binding (+1 from me too :) I'll update this wiki to show this KIP as approved. 拾 thanks dan On Thu, May 9, 2019 at 8:11 AM Rajini Sivaram wrote: > Hi Dan, > > Thanks for the KIP, +1 (binding) > > Regards, > >

[DISCUSS] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

The intent of this KIP is to add a consolidate endpoint to connect that gives consumers of the api a one stop shop for all their connector info needs. https://cwiki.apache.org/confluence/display/KAFKA/KIP-465%3A+Add+Consolidated+Connector+Endpoint+to+Connect+REST+API thanks, dan

Re: [DISCUSS] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

;: 0 } ], "type": "source" }, "status": { "name": "blah", "connector": { "state": "RUNNING", "worker_id": "10.200.25.241:8083" },

[VOTE] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

I would like to start voting for https://cwiki.apache.org/confluence/display/KAFKA/KIP-465%3A+Add+Consolidated+Connector+Endpoint+to+Connect+REST+API thanks dan

[jira] [Commented] (KAFKA-4979) Handcrafted JoinGroupRequest makes consumers on the same group to exit abruptly

[ https://issues.apache.org/jira/browse/KAFKA-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971068#comment-15971068 ] Dan commented on KAFKA-4979: Thank you for the reply! I created the same request and got the SchemaException

[jira] [Commented] (KAFKA-4979) Handcrafted JoinGroupRequest makes consumers on the same group to exit abruptly

[ https://issues.apache.org/jira/browse/KAFKA-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968803#comment-15968803 ] Dan commented on KAFKA-4979: How is the JoinGroupRequest Handcrafted? > Handcrafted JoinGroupRequest ma

[jira] [Created] (KAFKA-5115) Use bootstrap.servers to refresh metadata

Dan created KAFKA-5115: -- Summary: Use bootstrap.servers to refresh metadata Key: KAFKA-5115 URL: https://issues.apache.org/jira/browse/KAFKA-5115 Project: Kafka Issue Type: Improvement Affects

[jira] [Commented] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899299#comment-15899299 ] Dan commented on KAFKA-4845: I checked 0.10.2.0 again and it was indeed fixed. Thanks a lot

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899306#comment-15899306 ] Dan commented on KAFKA-4834: No. I found in another broker's log that it changed the same partition from New

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896740#comment-15896740 ] Dan commented on KAFKA-4834: By invoking AdminUtils.deleteTopic(zkUtils, topic). It seemed something wrong

[jira] [Updated] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan updated KAFKA-4845: --- Status: Patch Available (was: Open) > KafkaConsumer.seekToEnd cannot take effect when integrating with sp

[jira] [Updated] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan updated KAFKA-4845: --- Status: Open (was: Patch Available) > KafkaConsumer.seekToEnd cannot take effect when integrating with sp

[jira] [Created] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

Dan created KAFKA-4845: -- Summary: KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming Key: KAFKA-4845 URL: https://issues.apache.org/jira/browse/KAFKA-4845 Project: Kafka

[jira] [Created] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

Dan created KAFKA-4834: -- Summary: Kafka cannot delete topic with ReplicaStateMachine went wrong Key: KAFKA-4834 URL: https://issues.apache.org/jira/browse/KAFKA-4834 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5587) Processor got uncaught exception: NullPointerException

Dan created KAFKA-5587: -- Summary: Processor got uncaught exception: NullPointerException Key: KAFKA-5587 URL: https://issues.apache.org/jira/browse/KAFKA-5587 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3984) Broker doesn't retry reconnecting to an expired Zookeeper connection

[ https://issues.apache.org/jira/browse/KAFKA-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010436#comment-16010436 ] Dan commented on KAFKA-3984: We encountered the same problem in 0.10.1.1. Is there any plan to fix

Expiring record(s) for topic: 30011 ms has passed since last append

Hi, I'm running an app on Kafka Streams 1.0.0, and in the past day a lot of nodes are failing and I see this in the log. These appear to be failures when attempting to update the changelog. Any ideas on what I should do to work around this? Should I configure separate retry and timeouts for

[jira] [Created] (KAFKA-6547) group offset reset and begin_offset ignored/no effect

Dan created KAFKA-6547: -- Summary: group offset reset and begin_offset ignored/no effect Key: KAFKA-6547 URL: https://issues.apache.org/jira/browse/KAFKA-6547 Project: Kafka Issue Type: Bug

Streams - retry configuration publishing changelog updates?

more retries for changelog publishing? Thanks! Dan

Odd behaviour (bug?) - seek with "latest" offset reset strategy

/missing something, or is there a bug, and if so, what should I do (file a jira, add a fix to the pr, open a new pr?). What is the desired behaviour? Is it to get message at offset 11 in both cases? Thanks, Dan

Odd behaviour (bug?) - seek with "latest" offset reset strategy

/missing something, or is there a bug, and if so, what should I do (file a jira, add a fix to the pr, open a new pr?). What is the desired behaviour? Is it to get message at offset 11 in both cases? Thanks, Dan

Re: Ci stability

fixed recently, so hopefully stability will improve a bit. See KAFKA-14433 > for details. > > best, > Colin > > On Thu, Nov 24, 2022, at 12:48, John Roesler wrote: > > Hi Dan, > > > > I’m not sure if there’s a consistently used tag, but I’ve gotten good > > mil

Re: Ci stability

Thanks for the reply John! Is there a jira tag or view or something that can be used to find all the failing tests and maybe even try to fix them (even if fix just means extending a timeout)? On Thu, Nov 24, 2022, 16:03 John Roesler wrote: > Hi Dan, > > Thanks for pointing this o

Ci stability

is not the only one. I was wondering if there is a place where all the flaky tests are being tracked, and if it makes sense to fix (or at least temporarily disable) them so that confidence in new PRs could be increased. Thanks, Dan

Re: [DISCUSS] KIP-886 Add Client Producer and Consumer Builders

? Should I simply wait for discussion comments or votes (I've gotten no votes yet)? Thanks so much, Dan On Fri, Nov 11, 2022 at 1:30 AM Knowles Atchison Jr wrote: > This would be helpful. For our own client library wrappers we implemented > this functionality for any type with de

[DISCUSS] KIP-886 Add Client Producer and Consumer Builders

be added to the builder's withXYZ methods. Please let me know if you have any comments, questions, or suggestions! https://cwiki.apache.org/confluence/display/KAFKA/KIP-886%3A+Add+Client+Producer+and+Consumer+Builders Thanks, Dan

[VOTE] KIP-886 Add Client Producer and Consumer Builders

be added to the builder's withXYZ methods. Please let me know if you have any comments, questions, or suggestions in the discussion thread, or vote here! https://cwiki.apache.org/confluence/display/KAFKA/KIP-886 %3A+Add+Client+Producer+and+Consumer+Builders Thanks, Dan

review request: #12753 (small pr)

://github.com/apache/kafka/pull/12753 Thank you, Dan

request to contribute to kafka

Hello, I would like to contribute to kafka, my wiki id, jira id, and github username are all "scanteianu" Thanks, Dan

Review request - PR#12753

, Dan

Re: Should the mock consumer call the consumer rebalance listener on rebalance?

. On Thu, Mar 23, 2023, 18:17 Philip Nee wrote: > Hey Dan, > > Thanks for looking into this. Are you talking about MockConsumer? If you > invoke subscribe(Collection topics), it actually registers a Noop > callback. Perhaps this is what you are seeing? > > P > > On Thu, M

Should the mock consumer call the consumer rebalance listener on rebalance?

Hello all, It seems to me based on reading the code, that the consumer rebalance listener that is passed into the mock consumer when subscribing to a topic is not actually called when a rebalance is simulated. My understanding is that the consumer rebalance listener is called from the consumer

Re: Should the mock consumer call the consumer rebalance listener on rebalance?

I'll pick it up, thanks! On Thu, Mar 23, 2023, 19:27 Philip Nee wrote: > Hey Dan, > > Your analysis looks right. I do see TODO item there to implement the > rebalance callback. Would you like to create a jira issue and work on that? > > Thanks, > P > > On Thu, Mar

Re: Should the mock consumer call the consumer rebalance listener on rebalance?

I have created the jira, the PR will follow within the next few days. https://issues.apache.org/jira/browse/KAFKA-14841 Thanks again On Thu, Mar 23, 2023 at 7:33 PM Philip Nee wrote: > Awesome! > > On Thu, Mar 23, 2023 at 12:31 PM Dan S wrote: > > > I'll pick it up, thanks! &

Re: Should the mock consumer call the consumer rebalance listener on rebalance?

I have also created the pull request for the behaviour change. https://github.com/apache/kafka/pull/13455 Thanks again, Dan On Thu, Mar 23, 2023 at 11:40 PM Dan S wrote: > I have created the jira, the PR will follow within the next few days. > https://issues.apache.org/jira/browse/KAFKA

[jira] [Created] (KAFKA-881) Kafka broker not respecting log.roll.hours

Dan F created KAFKA-881: --- Summary: Kafka broker not respecting log.roll.hours Key: KAFKA-881 URL: https://issues.apache.org/jira/browse/KAFKA-881 Project: Kafka Issue Type: Bug Components

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646405#comment-13646405 ] Dan F commented on KAFKA-881: - Note: it would be useful for us to have the files roll over

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647912#comment-13647912 ] Dan F commented on KAFKA-881: - Someone pointed out a particularly easy fix: don't reuse files

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651225#comment-13651225 ] Dan F commented on KAFKA-881: - There would be major issues for us switching versions. I am

[jira] [Updated] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan F updated KAFKA-881: Attachment: kafka_roll.patch I attach a patch to 0.7.2. It passes the unit tests. I added a unit test for a 2nd

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651487#comment-13651487 ] Dan F commented on KAFKA-881: - Testing on my own server looks pretty good: - start server

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652447#comment-13652447 ] Dan F commented on KAFKA-881: - We are going to roll this out. Is anyone willing to look

[jira] [Updated] (KAFKA-975) Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[ https://issues.apache.org/jira/browse/KAFKA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Swanson updated KAFKA-975: -- Summary: Leader not local for partition when partition is leader

[jira] [Commented] (KAFKA-975) Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[ https://issues.apache.org/jira/browse/KAFKA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709845#comment-13709845 ] Dan Swanson commented on KAFKA-975: --- I have also tried using IP instead of host names

[jira] [Created] (KAFKA-975) Leader not local for partition when partition is leader

Dan Swanson created KAFKA-975: - Summary: Leader not local for partition when partition is leader Key: KAFKA-975 URL: https://issues.apache.org/jira/browse/KAFKA-975 Project: Kafka Issue Type

[jira] [Updated] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan F updated KAFKA-881: Status: Patch Available (was: Open) Kafka broker not respecting log.roll.hours

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721956#comment-13721956 ] Dan F commented on KAFKA-881: - Sure. I did: I did the below, then submitted kafka

[jira] [Updated] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan F updated KAFKA-881: Status: Open (was: Patch Available) Kafka broker not respecting log.roll.hours

[jira] [Comment Edited] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721956#comment-13721956 ] Dan F edited comment on KAFKA-881 at 7/28/13 2:41 PM: -- Sure. I did

[jira] [Comment Edited] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721956#comment-13721956 ] Dan F edited comment on KAFKA-881 at 7/28/13 2:42 PM: -- Sure. I did

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725974#comment-13725974 ] Dan F commented on KAFKA-881: - I am not necessarily opposed, but I don't understand what

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728571#comment-13728571 ] Dan F commented on KAFKA-881: - Sam: Thanks for that. It would be comforting to know if/when we

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749430#comment-13749430 ] Dan F commented on KAFKA-881: - 1. No, I believe that is the bug. lastAppendTime does

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786084#comment-13786084 ] Dan F commented on KAFKA-881: - Any word on whether this will be accepted into 0.7 and 0.8

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786925#comment-13786925 ] Dan F commented on KAFKA-881: - Sure enough, that's a race condition. Practically speaking

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144108#comment-14144108 ] Dan Hoffman commented on KAFKA-1367: I'd also add that having the broker being able

[jira] [Commented] (KAFKA-1419) cross build for scala 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14150693#comment-14150693 ] Dan Di Spaltro commented on KAFKA-1419: --- [~herriojr] It looks like the patchfile

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

dan norwood created KAFKA-4717: -- Summary: connect jars are missing LICENSE/NOTICE files Key: KAFKA-4717 URL: https://issues.apache.org/jira/browse/KAFKA-4717 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-4987) Topic creation allows invalid config values on running brokers

dan norwood created KAFKA-4987: -- Summary: Topic creation allows invalid config values on running brokers Key: KAFKA-4987 URL: https://issues.apache.org/jira/browse/KAFKA-4987 Project: Kafka

[jira] [Updated] (KAFKA-4987) Topic creation allows invalid config values on running brokers

[ https://issues.apache.org/jira/browse/KAFKA-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan norwood updated KAFKA-4987: --- Affects Version/s: 0.10.0.1 > Topic creation allows invalid config values on running brok

[jira] [Updated] (KAFKA-4987) Topic creation allows invalid config values on running brokers

[ https://issues.apache.org/jira/browse/KAFKA-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan norwood updated KAFKA-4987: --- Affects Version/s: (was: 0.10.2.0) > Topic creation allows invalid config values on runn

[jira] [Commented] (KAFKA-4987) Topic creation allows invalid config values on running brokers

[ https://issues.apache.org/jira/browse/KAFKA-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951490#comment-15951490 ] dan norwood commented on KAFKA-4987: this was a custom client based on 0.10.2.0 making

[jira] [Created] (KAFKA-5658) adminclient will stop working after some amount of time

dan norwood created KAFKA-5658: -- Summary: adminclient will stop working after some amount of time Key: KAFKA-5658 URL: https://issues.apache.org/jira/browse/KAFKA-5658 Project: Kafka Issue Type

[jira] [Commented] (KAFKA-5213) IllegalStateException in ensureOpenForRecordAppend

[ https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005651#comment-16005651 ] dan norwood commented on KAFKA-5213: awesome we found a real problem. i did run this locally

[jira] [Updated] (KAFKA-5213) IllegalStateException in ensureOpenForRecordAppend

[ https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan norwood updated KAFKA-5213: --- Description: i have a streams app that was working recently while pointing at trunk. this morning i

[jira] [Created] (KAFKA-5213) IllegalStateException in ensureOpenForRecordAppend

dan norwood created KAFKA-5213: -- Summary: IllegalStateException in ensureOpenForRecordAppend Key: KAFKA-5213 URL: https://issues.apache.org/jira/browse/KAFKA-5213 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5213) IllegalStateException in ensureOpenForRecordAppend

[ https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005525#comment-16005525 ] dan norwood commented on KAFKA-5213: turns out i was running trunk client against 0.10.2.1 brokers

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016718#comment-16016718 ] dan norwood commented on KAFKA-5275: it would be nice to have a default {{describeTopics

[jira] [Assigned] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan norwood reassigned KAFKA-4343: -- Assignee: dan norwood > Connect REST API should expose whether each connector is a sou

[jira] [Created] (KAFKA-5979) kip-120 changed internal streams topic naming

dan norwood created KAFKA-5979: -- Summary: kip-120 changed internal streams topic naming Key: KAFKA-5979 URL: https://issues.apache.org/jira/browse/KAFKA-5979 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6309) add support for getting topic defaults from AdminClient

dan norwood created KAFKA-6309: -- Summary: add support for getting topic defaults from AdminClient Key: KAFKA-6309 URL: https://issues.apache.org/jira/browse/KAFKA-6309 Project: Kafka Issue Type

[jira] [Created] (KAFKA-6418) adminclient throws timeoutexception when there is a SchemaException

dan norwood created KAFKA-6418: -- Summary: adminclient throws timeoutexception when there is a SchemaException Key: KAFKA-6418 URL: https://issues.apache.org/jira/browse/KAFKA-6418 Project: Kafka

[jira] [Created] (KAFKA-7713) producer io-wait-ratio > 1

dan norwood created KAFKA-7713: -- Summary: producer io-wait-ratio > 1 Key: KAFKA-7713 URL: https://issues.apache.org/jira/browse/KAFKA-7713 Project: Kafka Issue Type: Bug Affects Versi

[jira] [Created] (KAFKA-8414) org.apache.kafka.common.metrics.MetricsTest.testConcurrentReadUpdateReport hang

dan norwood created KAFKA-8414: -- Summary: org.apache.kafka.common.metrics.MetricsTest.testConcurrentReadUpdateReport hang Key: KAFKA-8414 URL: https://issues.apache.org/jira/browse/KAFKA-8414 Project

[jira] [Created] (KAFKA-8309) KIP-465: Add Consolidated Connector Endpoint to Connect REST API

dan norwood created KAFKA-8309: -- Summary: KIP-465: Add Consolidated Connector Endpoint to Connect REST API Key: KAFKA-8309 URL: https://issues.apache.org/jira/browse/KAFKA-8309 Project: Kafka