[jira] [Updated] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Gemela updated KAFKA-5154: Attachment: clio_reduced.gz > Kafka Streams throws NPE during rebalance >

[GitHub] kafka pull request #3050: (trunk) KAFKA-5232 Fix Log.parseTopicPartitionName...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3050 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] kafka pull request #3046: MINOR: Consolidate Topic classes

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3046 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010143#comment-16010143 ] Lukas Gemela commented on KAFKA-5154: - [~mjsax] logs attached (clio_reduced) It's just log from two

[jira] [Commented] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010146#comment-16010146 ] ASF GitHub Bot commented on KAFKA-5232: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4965: --- Fix Version/s: 0.10.2.2 > set internal.leave.group.on.close to false in KafkaStreams >

[jira] [Created] (KAFKA-5240) Make persistent checkpointedOffsets optionable

Lukas Gemela created KAFKA-5240: --- Summary: Make persistent checkpointedOffsets optionable Key: KAFKA-5240 URL: https://issues.apache.org/jira/browse/KAFKA-5240 Project: Kafka Issue Type:

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Thanks for the KIP. I'm not convinced on the `RichFunction` approach. Do we really want to give every DSL method access to the `ProcessorContext` ? It has a bunch of methods on it that seem in-appropriate for some of the DSL methods, i.e, `register`, `getStateStore`, `forward`, `schedule` etc. It

[GitHub] kafka pull request #3032: KAFKA-4965: set internal.leave.group.on.close to f...

Github user dguy closed the pull request at: https://github.com/apache/kafka/pull/3032 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010260#comment-16010260 ] ASF GitHub Bot commented on KAFKA-4965: --- Github user dguy closed the pull request at:

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

See Changes: [ismael] MINOR: Consolidate Topic classes -- [...truncated 863.93 KB...] kafka.utils.CommandLineUtilsTest > testParseEmptyArg PASSED

[jira] [Commented] (KAFKA-5025) FetchRequestTest should use batches with more than one message

[ https://issues.apache.org/jira/browse/KAFKA-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010242#comment-16010242 ] Umesh Chaudhary commented on KAFKA-5025: Hi [~ijuma], I executed the above test and observed that

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

See Changes: [ismael] KAFKA-5232; Fix Log.parseTopicPartitionName to handle deleted topics -- [...truncated 857.39 KB...] kafka.log.ProducerStateManagerTest >

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

See Changes: [ismael] KAFKA-5232; Fix Log.parseTopicPartitionName to handle deleted topics -- [...truncated 860.83 KB...] kafka.utils.CommandLineUtilsTest >

[jira] [Updated] (KAFKA-5118) Improve message for Kafka failed startup with non-Kafka data in data.dirs

[ https://issues.apache.org/jira/browse/KAFKA-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5118: --- Fix Version/s: 0.10.2.2 > Improve message for Kafka failed startup with non-Kafka data in data.dirs >

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

See Changes: [ismael] MINOR: Consolidate Topic classes -- [...truncated 859.32 KB...] kafka.log.ProducerStateManagerTest > testFirstUnstableOffsetAfterTruncation PASSED

[jira] [Commented] (KAFKA-5238) BrokerTopicMetrics can be recreated after topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010472#comment-16010472 ] ASF GitHub Bot commented on KAFKA-5238: --- Github user asfgit closed the pull request at:

[jira] [Created] (KAFKA-5241) GlobalKTable does not checkpoint offsets after restoring state

Tommy Becker created KAFKA-5241: --- Summary: GlobalKTable does not checkpoint offsets after restoring state Key: KAFKA-5241 URL: https://issues.apache.org/jira/browse/KAFKA-5241 Project: Kafka

[jira] [Commented] (KAFKA-5241) GlobalKTable does not checkpoint offsets after restoring state

[ https://issues.apache.org/jira/browse/KAFKA-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010389#comment-16010389 ] Tommy Becker commented on KAFKA-5241: - I have a patch for this and will take the issue, if someone can

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5232: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request #3054: KAFKA-5241: GlobalKTable does not checkpoint offse...

GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/3054 KAFKA-5241: GlobalKTable does not checkpoint offsets after restoring state Ensure checkpointable offsets for GlobalKTables are always written on close. You can merge this pull request into a Git

[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 it? >

[jira] [Updated] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Springer updated KAFKA-5226: Attachment: kafka.log Here's the full log file. > NullPointerException (NPE) in

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Damian Guy, could you let me know if you plan to review this further? There is no rush, but if you dont have any additional comments I could start the voting and finish my WIP PR. Thanks, Kyle On May 9, 2017 11:07 AM, "Kyle Winkelman" wrote: > Eno, is there anyone

[jira] [Commented] (KAFKA-5241) GlobalKTable does not checkpoint offsets after restoring state

[ https://issues.apache.org/jira/browse/KAFKA-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010417#comment-16010417 ] ASF GitHub Bot commented on KAFKA-5241: --- GitHub user twbecker opened a pull request:

[GitHub] kafka pull request #3042: MINOR: Fix one flaky test in MetricsTest and impro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3042 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Permission to edit Kafka wiki page

Hello Kafka developers, Could you give me permission to update Kafka System Tools page? https://cwiki.apache.org/confluence/display/KAFKA/System+Tools I am going to update this page in scope of https://github.com/apache/kafka/pull/3051 Arseniy

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

See

[jira] [Updated] (KAFKA-5200) If a replicated topic is deleted with one broker down, it can't be recreated

[ https://issues.apache.org/jira/browse/KAFKA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-5200: - Summary: If a replicated topic is deleted with one broker down, it can't be recreated (was:

[GitHub] kafka pull request #3055: Kip 138

GitHub user mihbor opened a pull request: https://github.com/apache/kafka/pull/3055 Kip 138 Test coverage is not satisfactory but I'd like to start getting feedback already. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-5242) state task directory locked forever

Lukas Gemela created KAFKA-5242: --- Summary: state task directory locked forever Key: KAFKA-5242 URL: https://issues.apache.org/jira/browse/KAFKA-5242 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010530#comment-16010530 ] Michal Borowiecki commented on KAFKA-3455: -- Hi [~bobbycalderwood], Can you please describe your

[jira] [Commented] (KAFKA-5200) Deleting topic when one broker is down will prevent topic to be re-creatable

[ https://issues.apache.org/jira/browse/KAFKA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010601#comment-16010601 ] Edoardo Comar commented on KAFKA-5200: -- Thanks [~huxi_2b] unfortunately such steps would imply

[GitHub] kafka pull request #3056: HOTFIX: AddOffsetsToTxnResponse using incorrect sc...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3056 HOTFIX: AddOffsetsToTxnResponse using incorrect schema in parse The parse method was incorrectly referring to `ApiKeys.ADD_PARTITIONS_TO_TXN` You can merge this pull request into a Git repository by

[jira] [Updated] (KAFKA-5240) Make persistent checkpointedOffsets optionable

[ https://issues.apache.org/jira/browse/KAFKA-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Gemela updated KAFKA-5240: Description: By looking at the ProcessorStateManager class kafka streams library tries to persist

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

See Changes: [ismael] MINOR: Fix one flaky test in MetricsTest and improve checks for another -- [...truncated 2.76 MB...] kafka.server.KafkaConfigTest >

[jira] [Reopened] (KAFKA-5182) Transient failure: RequestQuotaTest.testResponseThrottleTime

[ https://issues.apache.org/jira/browse/KAFKA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-5182: This is still happening: {code} java.util.concurrent.ExecutionException: java.lang.AssertionError:

[jira] [Comment Edited] (KAFKA-5182) Transient failure: RequestQuotaTest.testResponseThrottleTime

[ https://issues.apache.org/jira/browse/KAFKA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010645#comment-16010645 ] Ismael Juma edited comment on KAFKA-5182 at 5/15/17 2:57 PM: - This is still

Jenkins build is back to normal : kafka-0.10.2-jdk7 #163

See

[jira] [Comment Edited] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010974#comment-16010974 ] Lukas Gemela edited comment on KAFKA-5242 at 5/15/17 5:48 PM: -- [~mjsax] by

Re: KafkaStreams reports RUNNING even though all StreamThreads has crashed

Hi Andreas, This is not an intended behavior. Could you file a JIRA and describe your Kafka broker version / Streams API version, the logs / stack traces you saw in that ticket? I'd like to help investigate and walk you through the process to contribute a fix if you are interested and have time.

[jira] [Assigned] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5154: Assignee: Matthias J. Sax > Kafka Streams throws NPE during rebalance >

[jira] [Created] (KAFKA-5248) Remove retention time from TxnOffsetCommit RPC

Jason Gustafson created KAFKA-5248: -- Summary: Remove retention time from TxnOffsetCommit RPC Key: KAFKA-5248 URL: https://issues.apache.org/jira/browse/KAFKA-5248 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5248) Remove retention time from TxnOffsetCommit RPC

[ https://issues.apache.org/jira/browse/KAFKA-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011027#comment-16011027 ] ASF GitHub Bot commented on KAFKA-5248: --- GitHub user hachikuji opened a pull request:

[jira] [Resolved] (KAFKA-5206) RocksDBSessionStore doesn't use default aggSerde.

[ https://issues.apache.org/jira/browse/KAFKA-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5206. -- Resolution: Fixed Fix Version/s: 0.10.2.2 0.11.0.0 Issue resolved by

[jira] [Created] (KAFKA-5249) Transaction index recovery does not snapshot properly

Jason Gustafson created KAFKA-5249: -- Summary: Transaction index recovery does not snapshot properly Key: KAFKA-5249 URL: https://issues.apache.org/jira/browse/KAFKA-5249 Project: Kafka

[jira] [Created] (KAFKA-5245) KStream builder should capture serdes

Yeva Byzek created KAFKA-5245: - Summary: KStream builder should capture serdes Key: KAFKA-5245 URL: https://issues.apache.org/jira/browse/KAFKA-5245 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010959#comment-16010959 ] Apurva Mehta commented on KAFKA-5247: - Note that this is only an issue when we mix offset commits from

[jira] [Commented] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010974#comment-16010974 ] Lukas Gemela commented on KAFKA-5242: - [~mjsax] by multiple instances you mean multiple JVMs (nodes)

[jira] [Commented] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010990#comment-16010990 ] Jun Rao commented on KAFKA-5246: [~BigAndy], thanks for your interest. Just added you to Kafka

[GitHub] kafka pull request #3041: MINOR: Eliminate PID terminology from non test cod...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3041 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-5244) Tests which delete singleton metrics break subsequent metrics tests

[ https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010892#comment-16010892 ] Rajini Sivaram commented on KAFKA-5244: --- [~ijuma] Yes, that makes sense. Thank you. > Tests which

[jira] [Updated] (KAFKA-4850) RocksDb cannot use Bloom Filters

[ https://issues.apache.org/jira/browse/KAFKA-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-4850: -- Status: Patch Available (was: In Progress) > RocksDb cannot use Bloom Filters >

[jira] [Commented] (KAFKA-5203) Percentilles are calculated incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010987#comment-16010987 ] ASF GitHub Bot commented on KAFKA-5203: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #3059: KAFKA-5244: Refactor BrokerTopicStats and Controll...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3059 KAFKA-5244: Refactor BrokerTopicStats and ControllerStats so that they are classes This removes the need to force object initialisation via hacks to register the relevant metrics during start-up.

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

See Changes: [junrao] KAFKA-5203; Metrics: fix resetting of histogram sample -- [...truncated 860.42 KB...] kafka.server.KafkaConfigTest > testLogRollTimeMsProvided

Re: Can someone assign, or give me permission to assign myself to a Jira please?

Andy, I can see you now in the contributor list. Please feel free to assign JIRAs to yourself now. Guozhang On Mon, May 15, 2017 at 10:49 AM, Andrew Coates wrote: > Hi, > > I have a patch for KAFKA-5246 jira/browse/KAFKA-5246>, but don’t

[jira] [Updated] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5247: Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > Consumer GroupCoordinator should

[jira] [Updated] (KAFKA-5231) TransactinoCoordinator does not bump epoch when aborting open transactions

[ https://issues.apache.org/jira/browse/KAFKA-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5231: Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > TransactinoCoordinator does not bump

[GitHub] kafka pull request #3057: KAFKA-5182: Reduce session timeout in request quot...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3057 KAFKA-5182: Reduce session timeout in request quota test Reduce session timeouts for join requests to trigger throttling in the request quota test. You can merge this pull request into a Git

[jira] [Commented] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010948#comment-16010948 ] Andy Coates commented on KAFKA-5246: I've got a patch waiting for this is someone can assign this Jira

[GitHub] kafka pull request #3002: KAFKA-5203: Metrics: fix resetting of histogram sa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3002 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (KAFKA-5203) Percentilles are calculated incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5203. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3002

Re: [DISCUSS] KIP-148: Add a connect timeout for client

Hi David, I may be a bit confused before, just clarifying a few things: 1. As you mentioned, a client will always try to first establish the connection with a broker node before it tries to send any request to it. And after connection is established, it will either continuously send many

Can someone assign, or give me permission to assign myself to a Jira please?

Hi, I have a patch for KAFKA-5246 , but don’t yet have permissions to assign the Jira to myself. Would someone mind either assigning it, or giving me permissions to assign it to myself? Thanks, Andy

[jira] [Commented] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011025#comment-16011025 ] Matthias J. Sax commented on KAFKA-5242: Both should work. From a Streams perspective, it's no

[GitHub] kafka pull request #3058: KAFKA-5248: Remove unused/unneeded retention time ...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3058 KAFKA-5248: Remove unused/unneeded retention time in TxnOffsetCommitRequest You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Updated] (KAFKA-5249) Transaction index recovery does not snapshot properly

[ https://issues.apache.org/jira/browse/KAFKA-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5249: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > Transaction index recovery does

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

See Changes: [junrao] KAFKA-5203; Metrics: fix resetting of histogram sample -- [...truncated 1.66 MB...] org.apache.kafka.streams.processor.TopologyBuilderTest >

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

I'd rather not see the use of `ProcessorContext` spread any further than it currently is. So maybe we need another KIP that is done before this? Otherwise i think the scope of this KIP is becoming too large. On Mon, 15 May 2017 at 18:06 Matthias J. Sax wrote: > I agree

[jira] [Created] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

Apurva Mehta created KAFKA-5247: --- Summary: Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits Key: KAFKA-5247 URL:

[GitHub] kafka pull request #2971: Kafka-5206: Remove use of aggSerde in RocksDBSessi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2971 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Assigned] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates reassigned KAFKA-5246: -- Assignee: Andy Coates > Remove backdoor that allows any client to produce to internal topics

[GitHub] kafka pull request #2963: Kafka-5205: Removed use of keySerde in CachingSess...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2963 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-5249) Transaction index recovery does not snapshot properly

[ https://issues.apache.org/jira/browse/KAFKA-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011162#comment-16011162 ] ASF GitHub Bot commented on KAFKA-5249: --- GitHub user hachikuji opened a pull request:

[jira] [Commented] (KAFKA-5244) Tests which delete singleton metrics break subsequent metrics tests

[ https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010820#comment-16010820 ] Ismael Juma commented on KAFKA-5244: Good find [~rsivaram]. Note that in

[jira] [Created] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

Andy Coates created KAFKA-5246: -- Summary: Remove backdoor that allows any client to produce to internal topics Key: KAFKA-5246 URL: https://issues.apache.org/jira/browse/KAFKA-5246 Project: Kafka

[jira] [Resolved] (KAFKA-5205) CachingSessionStore doesn't use the default keySerde.

[ https://issues.apache.org/jira/browse/KAFKA-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5205. -- Resolution: Fixed Fix Version/s: 0.10.2.2 0.11.0.0 >

[jira] [Created] (KAFKA-5244) Tests which delete singleton metrics break subsequent metrics tests

Rajini Sivaram created KAFKA-5244: - Summary: Tests which delete singleton metrics break subsequent metrics tests Key: KAFKA-5244 URL: https://issues.apache.org/jira/browse/KAFKA-5244 Project: Kafka

[jira] [Commented] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010813#comment-16010813 ] Guozhang Wang commented on KAFKA-3514: -- Thanks [~mihbor] > Stream timestamp computation needs some

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010823#comment-16010823 ] Onur Karaman commented on KAFKA-3356: - I agree with [~jeffwidman]. > Remove ConsumerOffsetChecker,

[jira] [Commented] (KAFKA-5244) Tests which delete singleton metrics break subsequent metrics tests

[ https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010821#comment-16010821 ] Ismael Juma commented on KAFKA-5244: If you think the change makes sense, I could create a separate PR

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi, Sorry for super late response. Thanks for your comments. I am not an expert on Lambdas. Can you elaborate a little bit? I cannot > follow the explanation in the KIP to see what the problem is. - From [1] says "A functional interface is an interface that has just one abstract method, and

[GitHub] kafka pull request #3056: HOTFIX: AddOffsetsToTxnResponse using incorrect sc...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3056 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] kafka pull request #3060: KAFKA-5249: Fix incorrect producer snapshot offset...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3060 KAFKA-5249: Fix incorrect producer snapshot offsets when recovering segments You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Comment Edited] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010974#comment-16010974 ] Lukas Gemela edited comment on KAFKA-5242 at 5/15/17 5:50 PM: -- [~mjsax] by

[jira] [Comment Edited] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010974#comment-16010974 ] Lukas Gemela edited comment on KAFKA-5242 at 5/15/17 5:50 PM: -- [~mjsax] by

[jira] [Commented] (KAFKA-5244) Tests which delete singleton metrics break subsequent metrics tests

[ https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011053#comment-16011053 ] ASF GitHub Bot commented on KAFKA-5244: --- GitHub user ijuma opened a pull request:

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010801#comment-16010801 ] Jeff Widman commented on KAFKA-3356: Personally, I don't think we need feature parity for the

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

I agree that that `ProcessorContext` interface is too broad in general -- this is even true for transform/process, and it's also reflected in the API improvement list we want to do. https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams+Discussions So I am wondering, if you question the

[jira] [Commented] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010936#comment-16010936 ] Matthias J. Sax commented on KAFKA-5242: We fixed a couple of state directory lock issues in

[jira] [Commented] (KAFKA-5182) Transient failure: RequestQuotaTest.testResponseThrottleTime

[ https://issues.apache.org/jira/browse/KAFKA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010950#comment-16010950 ] ASF GitHub Bot commented on KAFKA-5182: --- GitHub user rajinisivaram opened a pull request:

[jira] [Updated] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Gemela updated KAFKA-5242: Attachment: clio_170511.log > add max_number _of_retries to exponential backoff strategy >

[jira] [Comment Edited] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011222#comment-16011222 ] Lukas Gemela edited comment on KAFKA-5242 at 5/15/17 7:48 PM: -- We used two

[jira] [Resolved] (KAFKA-5248) Remove retention time from TxnOffsetCommit RPC

[ https://issues.apache.org/jira/browse/KAFKA-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5248. Resolution: Fixed Issue resolved by pull request 3058

[GitHub] kafka pull request #3058: KAFKA-5248: Remove unused/unneeded retention time ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3058 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

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

See

[jira] [Updated] (KAFKA-5225) StreamsResetter doesn't allow custom Consumer properties

[ https://issues.apache.org/jira/browse/KAFKA-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-5225: -- Status: Patch Available (was: In Progress) > StreamsResetter doesn't allow custom

[jira] [Created] (KAFKA-5251) Producer should drop queued sends when transaction is aborted

Jason Gustafson created KAFKA-5251: -- Summary: Producer should drop queued sends when transaction is aborted Key: KAFKA-5251 URL: https://issues.apache.org/jira/browse/KAFKA-5251 Project: Kafka

[jira] [Updated] (KAFKA-5249) Transaction index recovery does not snapshot properly

[ https://issues.apache.org/jira/browse/KAFKA-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram Subramanian updated KAFKA-5249: -- Labels: exactly-once (was: ) > Transaction index recovery does not snapshot properly >

  1   2   >