[jira] [Commented] (KAFKA-6989) Support Async Processing in Streams

[ https://issues.apache.org/jira/browse/KAFKA-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625444#comment-16625444 ] sam commented on KAFKA-6989: This ticket is requesting something like this? {code:java} build

[jira] [Commented] (KAFKA-7432) API Method on Kafka Streams for processing chunks/batches of data

[ https://issues.apache.org/jira/browse/KAFKA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625446#comment-16625446 ] sam commented on KAFKA-7432: [~mjsax] I see the similarity in use case, but KAFKA-6988 seems

[jira] [Commented] (KAFKA-6989) Support Async Processing in Streams

[ https://issues.apache.org/jira/browse/KAFKA-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625477#comment-16625477 ] Virgil Palanciuc commented on KAFKA-6989: - num-stream-threads just allows you to

[jira] [Updated] (KAFKA-7417) Some topics lost / cannot recover their ISR status following broker crash

[ https://issues.apache.org/jira/browse/KAFKA-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khomenko updated KAFKA-7417: Summary: Some topics lost / cannot recover their ISR status following broker crash (was: S

[jira] [Comment Edited] (KAFKA-3268) Refactor existing CLI scripts to use KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625545#comment-16625545 ] Viktor Somogyi edited comment on KAFKA-3268 at 9/24/18 8:57 AM: ---

[jira] [Commented] (KAFKA-3268) Refactor existing CLI scripts to use KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625545#comment-16625545 ] Viktor Somogyi commented on KAFKA-3268: --- [~enothereska] I'll publish a KIP this wee

[jira] [Comment Edited] (KAFKA-3268) Refactor existing CLI scripts to use KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625545#comment-16625545 ] Viktor Somogyi edited comment on KAFKA-3268 at 9/24/18 8:58 AM: ---

[jira] [Updated] (KAFKA-5561) Java based TopicCommand to use the Admin client

[ https://issues.apache.org/jira/browse/KAFKA-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-5561: -- Summary: Java based TopicCommand to use the Admin client (was: Refactor TopicCommand to use th

[jira] [Commented] (KAFKA-5561) Java based TopicCommand to use the Admin client

[ https://issues.apache.org/jira/browse/KAFKA-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625590#comment-16625590 ] Viktor Somogyi commented on KAFKA-5561: --- [~ppatierno] if you don't mind I've rename

[jira] [Created] (KAFKA-7433) Introduce broker options in TopicCommand to use AdminClient

Viktor Somogyi created KAFKA-7433: - Summary: Introduce broker options in TopicCommand to use AdminClient Key: KAFKA-7433 URL: https://issues.apache.org/jira/browse/KAFKA-7433 Project: Kafka

[jira] [Updated] (KAFKA-7433) Introduce broker options in TopicCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-7433: -- Labels: kip (was: ) > Introduce broker options in TopicCommand to use AdminClient > --

[jira] [Updated] (KAFKA-7433) Introduce broker options in TopicCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-7433: -- Description: This task aim to add --bootstrap-servers and --admin.config options which enable T

[jira] [Updated] (KAFKA-7433) Introduce broker options in TopicCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-7433: -- Description: This task aim to add --bootstrap-servers and --admin.config options which enable

[jira] [Updated] (KAFKA-7433) Introduce broker options in TopicCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-7433: -- Component/s: (was: core) admin > Introduce broker options in TopicCommand

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625600#comment-16625600 ] M. Manna commented on KAFKA-1194: - The best thing to do is to check the following: 1) Se

[jira] [Commented] (KAFKA-7433) Introduce broker options in TopicCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625601#comment-16625601 ] ASF GitHub Bot commented on KAFKA-7433: --- viktorsomogyi opened a new pull request #5

[jira] [Comment Edited] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625600#comment-16625600 ] M. Manna edited comment on KAFKA-1194 at 9/24/18 10:11 AM: --- The

[jira] [Created] (KAFKA-7434) DeadLetterQueueReporter throws NPE if transform throws NPE

Michal Borowiecki created KAFKA-7434: Summary: DeadLetterQueueReporter throws NPE if transform throws NPE Key: KAFKA-7434 URL: https://issues.apache.org/jira/browse/KAFKA-7434 Project: Kafka

[jira] [Updated] (KAFKA-7434) DeadLetterQueueReporter throws NPE if transform throws NPE

[ https://issues.apache.org/jira/browse/KAFKA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Borowiecki updated KAFKA-7434: - Description: A NPE thrown from a transform in a connector configured with errors.deadlet

[jira] [Assigned] (KAFKA-7434) DeadLetterQueueReporter throws NPE if transform throws NPE

[ https://issues.apache.org/jira/browse/KAFKA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Borowiecki reassigned KAFKA-7434: Assignee: Michal Borowiecki > DeadLetterQueueReporter throws NPE if transform thro

[jira] [Updated] (KAFKA-7434) DeadLetterQueueReporter throws NPE if transform throws NPE

[ https://issues.apache.org/jira/browse/KAFKA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Borowiecki updated KAFKA-7434: - Description: A NPE thrown from a transform in a connector configured with errors.deadlet

[jira] [Updated] (KAFKA-7434) DeadLetterQueueReporter throws NPE if transform throws NPE

[ https://issues.apache.org/jira/browse/KAFKA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Borowiecki updated KAFKA-7434: - Description: A NPE thrown from a transform in a connector configured with errors.deadlet

[jira] [Commented] (KAFKA-5462) Add a configuration for users to specify a template for building a custom principal name

[ https://issues.apache.org/jira/browse/KAFKA-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625697#comment-16625697 ] ASF GitHub Bot commented on KAFKA-5462: --- omkreddy opened a new pull request #5684:

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625887#comment-16625887 ] shadi commented on KAFKA-1194: -- Thanks for the feedback. I tried to delete some log files b

[jira] [Commented] (KAFKA-7432) API Method on Kafka Streams for processing chunks/batches of data

[ https://issues.apache.org/jira/browse/KAFKA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625919#comment-16625919 ] John Roesler commented on KAFKA-7432: - Hi [~sams], This sounds like a valuable optim

[jira] [Commented] (KAFKA-6794) Support for incremental replica reassignment

[ https://issues.apache.org/jira/browse/KAFKA-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625935#comment-16625935 ] Sandor Murakozi commented on KAFKA-6794: [~viktorsomogyi] I think I won't be able

[jira] [Commented] (KAFKA-6794) Support for incremental replica reassignment

[ https://issues.apache.org/jira/browse/KAFKA-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625945#comment-16625945 ] Sandor Murakozi commented on KAFKA-6794: [~viktorsomogyi] you can build on my hal

[jira] [Created] (KAFKA-7435) Consider standardizing the config object pattern on interface/implementation.

John Roesler created KAFKA-7435: --- Summary: Consider standardizing the config object pattern on interface/implementation. Key: KAFKA-7435 URL: https://issues.apache.org/jira/browse/KAFKA-7435 Project: Ka

[jira] [Created] (KAFKA-7436) overriding auto.offset.reset to none for executor

Sanjay Kumar created KAFKA-7436: --- Summary: overriding auto.offset.reset to none for executor Key: KAFKA-7436 URL: https://issues.apache.org/jira/browse/KAFKA-7436 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6989) Support Async Processing in Streams

[ https://issues.apache.org/jira/browse/KAFKA-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626058#comment-16626058 ] sam commented on KAFKA-6989: [~virgilp]  > num-stream-threads just allows you to process mor

[jira] [Resolved] (KAFKA-2471) Replicas Order and Leader out of sync

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

[jira] [Commented] (KAFKA-7435) Consider standardizing the config object pattern on interface/implementation.

[ https://issues.apache.org/jira/browse/KAFKA-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626080#comment-16626080 ] Guozhang Wang commented on KAFKA-7435: -- John, thanks for the proposal. We did talk

[jira] [Commented] (KAFKA-7430) Improve Transformer interface JavaDoc

[ https://issues.apache.org/jira/browse/KAFKA-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626089#comment-16626089 ] ASF GitHub Bot commented on KAFKA-7430: --- guozhangwang closed pull request #5675: KA

[jira] [Assigned] (KAFKA-5462) Add a configuration for users to specify a template for building a custom principal name

[ https://issues.apache.org/jira/browse/KAFKA-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5462: Assignee: Manikumar > Add a configuration for users to specify a template for building a custom >

[jira] [Commented] (KAFKA-7435) Consider standardizing the config object pattern on interface/implementation.

[ https://issues.apache.org/jira/browse/KAFKA-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626117#comment-16626117 ] John Roesler commented on KAFKA-7435: - Thanks for the context, [~guozhang]. I agree

[jira] [Created] (KAFKA-7437) Store leader epoch in offset commit metadata

Jason Gustafson created KAFKA-7437: -- Summary: Store leader epoch in offset commit metadata Key: KAFKA-7437 URL: https://issues.apache.org/jira/browse/KAFKA-7437 Project: Kafka Issue Type: Im

[jira] [Assigned] (KAFKA-7437) Store leader epoch in offset commit metadata

[ https://issues.apache.org/jira/browse/KAFKA-7437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-7437: -- Assignee: Jason Gustafson > Store leader epoch in offset commit metadata > ---

[jira] [Updated] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-7403: --- Affects Version/s: (was: 2.1.0) > Offset commit failure after upgrading brokers past KIP-

[jira] [Updated] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-7403: --- Fix Version/s: 2.1.0 > Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[jira] [Updated] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-7403: --- Priority: Blocker (was: Major) > Offset commit failure after upgrading brokers past KIP-211/

[jira] [Commented] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626228#comment-16626228 ] Jason Gustafson commented on KAFKA-7403: [~vahid] I was looking at this as part o

[jira] [Commented] (KAFKA-7412) Bug prone response from producer.send(ProducerRecord, Callback) if Kafka broker is not running

[ https://issues.apache.org/jira/browse/KAFKA-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626414#comment-16626414 ] Suman B N commented on KAFKA-7412: -- Even I have used the same client, broker, and code,

[jira] [Commented] (KAFKA-7223) KIP-328: Add in-memory Suppression

[ https://issues.apache.org/jira/browse/KAFKA-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626419#comment-16626419 ] ASF GitHub Bot commented on KAFKA-7223: --- guozhangwang closed pull request #5567: KA

[jira] [Commented] (KAFKA-7277) Migrate Streams API to Duration instead of longMs times

[ https://issues.apache.org/jira/browse/KAFKA-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626440#comment-16626440 ] Nikolay Izhikov commented on KAFKA-7277: [~vvcephei] Tests now green. Please, rev

[jira] [Commented] (KAFKA-7223) KIP-328: Add in-memory Suppression

[ https://issues.apache.org/jira/browse/KAFKA-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626454#comment-16626454 ] ASF GitHub Bot commented on KAFKA-7223: --- vvcephei opened a new pull request #5687:

[jira] [Commented] (KAFKA-7223) KIP-328: Add in-memory Suppression

[ https://issues.apache.org/jira/browse/KAFKA-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626533#comment-16626533 ] ASF GitHub Bot commented on KAFKA-7223: --- vvcephei opened a new pull request #5688:

[jira] [Commented] (KAFKA-7437) Store leader epoch in offset commit metadata

[ https://issues.apache.org/jira/browse/KAFKA-7437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626625#comment-16626625 ] ASF GitHub Bot commented on KAFKA-7437: --- hachikuji opened a new pull request #5689:

[jira] [Commented] (KAFKA-7057) Consumer stop polling

[ https://issues.apache.org/jira/browse/KAFKA-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626677#comment-16626677 ] Bo Wang commented on KAFKA-7057: We also get the same problem. After the heartbeat thread

[jira] [Commented] (KAFKA-7432) API Method on Kafka Streams for processing chunks/batches of data

[ https://issues.apache.org/jira/browse/KAFKA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626682#comment-16626682 ] Matthias J. Sax commented on KAFKA-7432: I tend to agree with John, that batching

[jira] [Updated] (KAFKA-5863) Potential null dereference in DistributedHerder#reconfigureConnector()

[ https://issues.apache.org/jira/browse/KAFKA-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-5863: -- Description: Here is the call chain: {code} RestServer.httpRequest(reconfigUrl,

[jira] [Commented] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626774#comment-16626774 ] Vahid Hashemian commented on KAFKA-7403: [~hachikuji] Thanks for the pointer. I w

[jira] [Updated] (KAFKA-5066) KafkaMetricsConfig properties and description notably missing from documentation

[ https://issues.apache.org/jira/browse/KAFKA-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-5066: Fix Version/s: 2.1.0 > KafkaMetricsConfig properties and description notably missing from > documentation

[jira] [Commented] (KAFKA-5066) KafkaMetricsConfig properties and description notably missing from documentation

[ https://issues.apache.org/jira/browse/KAFKA-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626775#comment-16626775 ] ASF GitHub Bot commented on KAFKA-5066: --- lindong28 closed pull request #5563: KAFKA

[jira] [Commented] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626793#comment-16626793 ] ASF GitHub Bot commented on KAFKA-7403: --- vahidhashemian opened a new pull request #

[jira] [Updated] (KAFKA-7412) Bug prone response from producer.send(ProducerRecord, Callback) if Kafka broker is not running

[ https://issues.apache.org/jira/browse/KAFKA-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Turek updated KAFKA-7412: Attachment: both_metadata_and_exception.png > Bug prone response from producer.send(ProducerRecord,

[jira] [Commented] (KAFKA-7412) Bug prone response from producer.send(ProducerRecord, Callback) if Kafka broker is not running

[ https://issues.apache.org/jira/browse/KAFKA-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626825#comment-16626825 ] Michal Turek commented on KAFKA-7412: - Hmm, I have just tried to repeat it multiple t