[jira] [Created] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

Apurva Mehta created KAFKA-5366: --- Summary: Add cases for concurrent transactional reads and writes in system tests Key: KAFKA-5366 URL: https://issues.apache.org/jira/browse/KAFKA-5366 Project: Kafka

[jira] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5366: Description: Currently the transactions system test does a transactional copy while bouncing broker

[jira] [Updated] (KAFKA-5284) Add tools and metrics to diagnose problems with the idempotent producer and transactions

[ https://issues.apache.org/jira/browse/KAFKA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5284: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Add tools and metrics to diagnose pro

[jira] [Commented] (KAFKA-5284) Add tools and metrics to diagnose problems with the idempotent producer and transactions

[ https://issues.apache.org/jira/browse/KAFKA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034258#comment-16034258 ] Ismael Juma commented on KAFKA-5284: I'm moving this to 0.11.0.1 given the current tim

[jira] [Updated] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5026: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > DebuggingConsumerId and DebuggingMess

[jira] [Assigned] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5032: -- Assignee: (was: Ismael Juma) > Think through implications of max.message.size affecting rec

[jira] [Commented] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034259#comment-16034259 ] Ismael Juma commented on KAFKA-5026: Moving this to 0.11.0.1. If we somehow have time

[jira] [Assigned] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5032: -- Assignee: Ismael Juma > Think through implications of max.message.size affecting record batches

[jira] [Updated] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5032: --- Labels: documentation exactly-once (was: exactly-once) > Think through implications of max.message.si

[jira] [Updated] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4595: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Controller send thread can't stop whe

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034264#comment-16034264 ] Ismael Juma commented on KAFKA-4595: Bumping the fix version until we get confirmation

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

Thanks Matthias, I appreciate people are busy now preparing the 0.11 release. One thing I would also appreciate input on is perhaps a better name for the new TypedStores class, I just picked it quickly but don't really like it. Perhaps StateStores would make for a better name? Cheers, Micha

[jira] [Commented] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034279#comment-16034279 ] Ismael Juma commented on KAFKA-5032: I looked into the config change and it looks like

[jira] [Comment Edited] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034279#comment-16034279 ] Ismael Juma edited comment on KAFKA-5032 at 6/2/17 7:35 AM: I

[jira] [Updated] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5032: --- Description: It's worth noting that the new behaviour for uncompressed messages is the same as the ex

[jira] [Updated] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

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

[GitHub] kafka pull request #3202: KAFKA-5364: Don't fail producer if drained partiti...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3202 --- 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 enab

[jira] [Commented] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

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

[jira] [Updated] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

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

[GitHub] kafka pull request #3199: KAFKA-5311: Support ExtendedDeserializer in Kafka ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3199 --- 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 enab

[jira] [Commented] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

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

[jira] [Created] (KAFKA-5367) Producer should not expiry topic from metadata cache if accumulator still has data for this topic

Dong Lin created KAFKA-5367: --- Summary: Producer should not expiry topic from metadata cache if accumulator still has data for this topic Key: KAFKA-5367 URL: https://issues.apache.org/jira/browse/KAFKA-5367

[jira] [Created] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

Hamidreza Afzali created KAFKA-5368: --- Summary: Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid Key: KAFKA-5368 URL: https://issues.apache.org/jira/browse/KAFKA-536

[GitHub] kafka pull request #3203: KAFKA-5365: Fix regression in compressed message i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3203 --- 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 enab

[jira] [Commented] (KAFKA-5365) Fix regression in compressed message iteration affecting magic v0 and v1

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

[jira] [Resolved] (KAFKA-5365) Fix regression in compressed message iteration affecting magic v0 and v1

[ https://issues.apache.org/jira/browse/KAFKA-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5365. Resolution: Fixed > Fix regression in compressed message iteration affecting magic v0 and v1 > -

[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&focusedCommentId=16034356#comment-16034356 ] Lukas Gemela commented on KAFKA-5154: - [~guozhang] no worries, thank you for the fix,

Re: [VOTE] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

+1 (non binding) Thanks for the KIP On Thu, Jun 1, 2017 at 5:44 PM, Dong Lin wrote: > Hi all, > > Can you please vote for KIP-164? The KIP can be found at > https://cwiki.apache.org/confluence/display/KAFKA/KIP-164-+Add+UnderMinIsrPartitionCount+and+per-partition+UnderMinIsr+metrics > . > > Thank

[jira] [Commented] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

[ https://issues.apache.org/jira/browse/KAFKA-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034367#comment-16034367 ] Hamidreza Afzali commented on KAFKA-5368: - *Problem:* Skipped records sensor is u

Re: [VOTE] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

+1 (non binding) Thanks, Michał On 02/06/17 10:18, Mickael Maison wrote: +1 (non binding) Thanks for the KIP On Thu, Jun 1, 2017 at 5:44 PM, Dong Lin wrote: Hi all, Can you please vote for KIP-164? The KIP can be found at https://cwiki.apache.org/confluence/display/KAFKA/KIP-164-+Add+UnderM

[jira] [Updated] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

[ https://issues.apache.org/jira/browse/KAFKA-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5282: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Transactions integration test: Us

[GitHub] kafka pull request #3129: KAFKA-5282: Use a factory method to create produce...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3129 --- 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 enab

[jira] [Commented] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

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

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

I agree with what Matthias has said w.r.t failing fast. There are plenty of times when you don't want to fail-fast and must attempt to make progress. The dead-letter queue is exactly for these circumstances. Of course if every record is failing, then you probably do want to give up. On Fri, 2 Jun

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

See Changes: [jason] KAFKA-5364; Don't fail producer if drained partition is not yet in [ismael] KAFKA-5311: Support ExtendedDeserializer in Kafka Streams [ismael] KAFKA-5365; Fix regression in compressed messa

[GitHub] kafka pull request #3205: KAFKA-5236; Increase the block/buffer size when co...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3205 KAFKA-5236; Increase the block/buffer size when compressing with Snappy and Gzip We had originally increased Snappy’s block size as part of KAFKA-3704. However, we had some issues with excessiv

[jira] [Commented] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

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

[jira] [Updated] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

[ https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5236: --- Assignee: Ismael Juma Status: Patch Available (was: Open) > Regression in on-disk log size when

[jira] [Commented] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

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

[GitHub] kafka pull request #3206: KAFKA-5368 Kafka Streams skipped-records-rate sens...

GitHub user hrafzali opened a pull request: https://github.com/apache/kafka/pull/3206 KAFKA-5368 Kafka Streams skipped-records-rate sensor bug This resolved the issue with Kafka Streams skipped records sensor reporting wrong values. Jira ticket: https://issues.apache.org/ji

[jira] [Commented] (KAFKA-5304) Kafka Producer throwing infinite NullPointerExceptions

[ https://issues.apache.org/jira/browse/KAFKA-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034486#comment-16034486 ] Rajini Sivaram commented on KAFKA-5304: --- [~prchaudh] What is the security protocol o

[jira] [Assigned] (KAFKA-5325) Connection Lose during Kafka Kerberos Renewal process

[ https://issues.apache.org/jira/browse/KAFKA-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-5325: - Assignee: Rajini Sivaram > Connection Lose during Kafka Kerberos Renewal process > --

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Jan, you have a choice to Fail fast if you want. This is about giving people options and there are times when you don't want to fail fast. On Fri, 2 Jun 2017 at 11:00 Jan Filipiak wrote: > Hi > > 1. > That greatly complicates monitoring. Fail Fast gives you that when you > monitor only the lag

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

See Changes: [ismael] KAFKA-5282; Use a factory method to create producers/consumers and close -- [...truncated 908.86 KB...] kafka.admin.ConfigCommandTest > shouldNotUp

[GitHub] kafka pull request #2328: KAFKA-3264: Deprecate the old Scala consumer (KIP-...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2328 --- 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 enab

[jira] [Updated] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3264: --- Resolution: Fixed Fix Version/s: 0.11.1.0 Status: Resolved (was: Patch Available) I

[jira] [Commented] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

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

[jira] [Updated] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3264: --- Fix Version/s: (was: 0.11.1.0) > Mark the old Scala consumer and related classes as deprecated > -

[GitHub] kafka pull request #3207: MINOR: Fix flaky testHWCheckpointWithFailuresSingl...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3207 MINOR: Fix flaky testHWCheckpointWithFailuresSingleLogSegment It was incorrectly passing `oldLeaderOpt` to `waitUntilLeaderIsElectedOrChanged` as can be seen by the subsequent assertion. This star

[jira] [Commented] (KAFKA-5123) Refactor ZkUtils readData* methods

[ https://issues.apache.org/jira/browse/KAFKA-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034575#comment-16034575 ] Balint Molnar commented on KAFKA-5123: -- How to refactor zkUtils.readData method: * mo

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

See

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

See Changes: [ismael] KAFKA-3264; Deprecate the old Scala consumer (KIP-109) -- [...truncated 948.20 KB...] kafka.integration.PrimitiveApiTest > testMultiProduce PASSED k

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

> On Jun 2, 2017, at 12:54 AM, Matthias J. Sax wrote: > > With regard to backward compatibility, we should not change the current > interface, but add a new interface that extends the current one. > ++1

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

This makes much more sense to me. +1 > On Jun 1, 2017, at 10:33 AM, Kyle Winkelman wrote: > > I have updated the KIP and my PR. Let me know what you think. > To created a cogrouped stream just call cogroup on a KgroupedStream and > supply the initializer, aggValueSerde, and an aggregator. Then c

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

See

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Hi 1. That greatly complicates monitoring. Fail Fast gives you that when you monitor only the lag of all your apps you are completely covered. With that sort of new application Monitoring is very much more complicated as you know need to monitor fail % of some special apps aswell. In my opini

[GitHub] kafka pull request #3208: KAFKA-5325: Avoid and handle exceptions for Kerber...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3208 KAFKA-5325: Avoid and handle exceptions for Kerberos re-login You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka KAFKA-53

[jira] [Commented] (KAFKA-5325) Connection Lose during Kafka Kerberos Renewal process

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

[GitHub] kafka pull request #3209: KAFKA-5345; Close KafkaClient when streams client ...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3209 KAFKA-5345; Close KafkaClient when streams client is closed Cherry-pick KAFKA-5345 to 0.10.2 You can merge this pull request into a Git repository by running: $ git pull https://github.co

[jira] [Commented] (KAFKA-5345) Some socket connections not closed after restart of Kafka Streams

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

[GitHub] kafka pull request #3209: KAFKA-5345; Close KafkaClient when streams client ...

Github user rajinisivaram closed the pull request at: https://github.com/apache/kafka/pull/3209 --- 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

[jira] [Commented] (KAFKA-5345) Some socket connections not closed after restart of Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034805#comment-16034805 ] ASF GitHub Bot commented on KAFKA-5345: --- Github user rajinisivaram closed the pull r

[jira] [Updated] (KAFKA-5345) Some socket connections not closed after restart of Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-5345: -- Fix Version/s: 0.10.2.2 > Some socket connections not closed after restart of Kafka Streams > --

[GitHub] kafka pull request #3210: [WIP] KAFKA-5272: Improve validation for Describe/...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3210 [WIP] KAFKA-5272: Improve validation for Describe/Alter Configs (KIP-133) You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-5272-

[jira] [Commented] (KAFKA-5272) Improve validation for Describe/Alter Configs (KIP-133)

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

Android app produces data in Kafka

> Hi. > > I am going to do a project in the University in order to finish my master in > IoT. > > I need to know if it is posible connect an android app with Kafka. I want > that my mobile android takes data with its sensors and produces the data in > Kafka logs. > If that is posible, where c

[jira] [Updated] (KAFKA-5363) Add ability to batch restore and receive restoration stats.

[ https://issues.apache.org/jira/browse/KAFKA-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5363: --- Summary: Add ability to batch restore and receive restoration stats. (was: Add restoreAll functionali

[jira] [Updated] (KAFKA-5363) Add ability to batch restore and receive restoration stats.

[ https://issues.apache.org/jira/browse/KAFKA-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5363: --- Description: Currently, when restoring a state store in a Kafka Streams application, we put one key-v

Re: 0.11.0.0 Release Update

Hi all, So will Exactly Once Semantics be reason enough to bump version to 1.0? Or is the leading zero here to stay indefinitely? :-) Cheers, Michal On 05/05/17 04:28, Ismael Juma wrote: Hi all, We're quickly approaching our next time-based release. If you missed any of the updates on the

Re: 0.11.0.0 Release Update

Hi Michal, We would like to allow for at least one stabilisation cycle after exactly-once lands before we consider the 1.0 release. Soon after the 0.11.0.0 release, a release manager for the subsequent release will hopefully volunteer and we can then discuss the details. While on the subject, I w

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Guozhang, Matthias, Thanks for the comments. I have updated the KIP, (JIRA title and description as well). I had thought about introducing a separate interface altogether, but extending the current one makes more sense. As for intermediate callbacks based on time or number of records, I think t

Re: [DISCUSS] KIP-138: Change punctuate semantics

Hi Matthias, Apologies, somehow I totally missed this email earlier. Wrt ValueTransformer, I added it to the the list of deprecated methods (PR is up to date). Wrt Cancellable vs Cancelable: I'm not fluent enough to have spotted this nuance, but having googled for it, you are right. On th

[jira] [Created] (KAFKA-5369) Producer hangs on metadata fetch from broker in security authorization related failures and no meaningful exception is thrown

Koelli Mungee created KAFKA-5369: Summary: Producer hangs on metadata fetch from broker in security authorization related failures and no meaningful exception is thrown Key: KAFKA-5369 URL: https://issues.apache.o

[jira] [Updated] (KAFKA-5164) SetSchemaMetadata does not replace the schemas in structs correctly

[ https://issues.apache.org/jira/browse/KAFKA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5164: - Resolution: Fixed Fix Version/s: 0.11.1.0 0.11.0.0

[GitHub] kafka pull request #3198: KAFKA-5164 Ensure SetSchemaMetadata updates key or...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3198 --- 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 enab

[jira] [Commented] (KAFKA-5164) SetSchemaMetadata does not replace the schemas in structs correctly

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

[jira] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5366: Labels: exactly-once (was: ) > Add cases for concurrent transactional reads and writes in system te

[jira] [Updated] (KAFKA-5292) Update authorization checks in AdminClient and add authorization tests

[ https://issues.apache.org/jira/browse/KAFKA-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5292: --- Summary: Update authorization checks in AdminClient and add authorization tests (was: Authori

[GitHub] kafka pull request #3211: Minor: make flush no-op as we don't need to call f...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/3211 Minor: make flush no-op as we don't need to call flush on commit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbejeck/kafka MINOR_no_flush_o

[jira] [Resolved] (KAFKA-5327) Console Consumer should only poll for up to max messages

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

[GitHub] kafka pull request #3148: KAFKA-5327: ConsoleConsumer should manually commit...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3148 --- 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 enab

[jira] [Commented] (KAFKA-5327) Console Consumer should only poll for up to max messages

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

[jira] [Resolved] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

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

[GitHub] kafka pull request #3206: KAFKA-5368 Kafka Streams skipped-records-rate sens...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3206 --- 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 enab

[jira] [Commented] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

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

[jira] [Updated] (KAFKA-3982) Issue with processing order of consumer properties in console consumer

[ https://issues.apache.org/jira/browse/KAFKA-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3982: - Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available

[GitHub] kafka pull request #1655: KAFKA-3982: Fix processing order of some of the co...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1655 --- 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 enab

[jira] [Commented] (KAFKA-3982) Issue with processing order of consumer properties in console consumer

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

[jira] [Commented] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

[ https://issues.apache.org/jira/browse/KAFKA-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035344#comment-16035344 ] Matthias J. Sax commented on KAFKA-5368: Could we add a test for this? I think thi

[GitHub] kafka pull request #3205: KAFKA-5236; Increase the block/buffer size when co...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3205 --- 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 enab

[jira] [Commented] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

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

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035365#comment-16035365 ] Onur Karaman commented on KAFKA-1595: - Sounds good. > Remove deprecated and slower sc

[GitHub] kafka pull request #3212: KAFKA-5019: Upgrades notes for idempotent/transact...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3212 KAFKA-5019: Upgrades notes for idempotent/transactional features and new message format You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachi

[jira] [Commented] (KAFKA-5019) Exactly-once upgrade notes

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

[jira] [Commented] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

[ https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035404#comment-16035404 ] Nick Travers commented on KAFKA-5236: - Thanks for the patch [~ijuma]! I ran the same t

[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5019: --- Status: Patch Available (was: In Progress) > Exactly-once upgrade notes > ---

[jira] [Commented] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

[ https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035417#comment-16035417 ] Ismael Juma commented on KAFKA-5236: Thanks for verifying [~nickt]. > Regression in o

[GitHub] kafka pull request #3213: KAFKA-5359: Make future exception the exception ca...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/3213 KAFKA-5359: Make future exception the exception cause on the client side Instead of throwing `future.exception()` on the client side, throw an exception with `future.exception()` as the cause

[jira] [Commented] (KAFKA-5359) Exceptions from RequestFuture lack parts of the stack trace

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

[jira] [Updated] (KAFKA-5359) Exceptions from RequestFuture lack parts of the stack trace

[ https://issues.apache.org/jira/browse/KAFKA-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-5359: --- Status: Patch Available (was: Open) > Exceptions from RequestFuture lack parts of the stack t

  1   2   >