[GitHub] kafka pull request #1376: KAFKA-3282: Change tools to use --new-consumer by ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1376 --- 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-3282) Change tools to use new consumer if zookeeper is not specified

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

[jira] [Updated] (KAFKA-3282) Change tools to use new consumer if zookeeper is not specified

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

[GitHub] kafka pull request #1905: MINOR: Remove no longer required --new-consumer sw...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1905 MINOR: Remove no longer required --new-consumer switch in docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka no-new-consumer-switch-

[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: 0.10.2.0 > Mark the old Scala consumer and related classes as deprecated >

[jira] [Updated] (KAFKA-2983) Remove old Scala clients and all related code, tests, and tools.

[ https://issues.apache.org/jira/browse/KAFKA-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2983: --- Fix Version/s: 0.11.0.0 > Remove old Scala clients and all related code, tests, and tools. > -

[jira] [Commented] (KAFKA-2983) Remove old Scala clients and all related code, tests, and tools.

[ https://issues.apache.org/jira/browse/KAFKA-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520486#comment-15520486 ] Ismael Juma commented on KAFKA-2983: Setting "Fix version" as 0.11.0.0 just for tracki

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

See Changes: [ismael] KAFKA-3282; Change tools to use new consumer if zookeeper is not -- [...truncated 1584 lines...] kafka.api.ClientIdQuotaTest > testProducerConsumerOverrideUnthrottled START

Build failed in Jenkins: kafka-0.10.1-jdk7 #9

See Changes: [ismael] KAFKA-3282; Change tools to use new consumer if zookeeper is not -- [...truncated 7398 lines...] kafka.coordinator.GroupCoordinatorResponseTest > testSyncGroupLeaderAfterFo

[jira] [Updated] (KAFKA-4216) Replication Throttling: Leader may not be throttled if it is not "moving"

[ https://issues.apache.org/jira/browse/KAFKA-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4216: Description: The current algorithm in kafka-reassign-partitions applies a throttle to all moving re

[DISCUSS] KIP-73: Replication Quotas

Hi All We’ve made an adjustment to KIP-73: Replication Quotas which I’d like to open up to the community for approval. Previously the admin passed a list of replicas to be throttled: quota.replication.throttled.replicas = [partId]:[replica],[partId]:[replica],[partId]:[replica] etc T

Help related to KStreams and Stateful event processing.

Hello there! I read about Kafka Streams recently, pretty interesting the way it solves the stream processing problem in a more cleaner way with less overheads and complexities. I work as a Software Engineer in a startup, and we are in the design stage for building a stream processing pipeline (if

[jira] [Commented] (KAFKA-4120) byte[] keys in RocksDB state stores do not work as expected

[ https://issues.apache.org/jira/browse/KAFKA-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521271#comment-15521271 ] Elias Levy commented on KAFKA-4120: --- {{o.a.k.common.utils.Bytes}} is not a documented cl

[jira] [Created] (KAFKA-4219) Permit setting of event time in stream processor

Elias Levy created KAFKA-4219: - Summary: Permit setting of event time in stream processor Key: KAFKA-4219 URL: https://issues.apache.org/jira/browse/KAFKA-4219 Project: Kafka Issue Type: Improvem

[jira] [Commented] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521287#comment-15521287 ] Elias Levy commented on KAFKA-4212: --- I should be noted that a variable-capacity memory-o

[jira] [Comment Edited] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521287#comment-15521287 ] Elias Levy edited comment on KAFKA-4212 at 9/25/16 7:17 PM: It

[jira] [Created] (KAFKA-4220) Clean up & provide better error message when incorrect argument types are provided in the command line client

Ishita Mandhan created KAFKA-4220: - Summary: Clean up & provide better error message when incorrect argument types are provided in the command line client Key: KAFKA-4220 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (KAFKA-4220) Clean up & provide better error message when incorrect argument types are provided in the command line client

[ https://issues.apache.org/jira/browse/KAFKA-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan updated KAFKA-4220: -- Description: When the argument provided to a command line statement is not of the right type, a

[GitHub] kafka pull request #1860: KAFKA-4055: System tests for secure quotas

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1860 --- 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-4055) Add system tests for secure quotas

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

[jira] [Updated] (KAFKA-4055) Add system tests for secure quotas

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

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

See Changes: [junrao] KAFKA-4055; System tests for secure quotas -- [...truncated 13433 lines...] org.apache.kafka.streams.kstream.internals.KTableFilterTest > testSendingOldValue STARTED org.a

Re: Help related to KStreams and Stateful event processing.

Hi Arvind, short answer, Kafka Streams does definitely help you! Long answer, Kafka Streams offers two layer to program your stream processing job. The low-level Processor API and the high level DSL. Please check the documentation to get further details: http://docs.confluent.io/3.0.1/streams/ind

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

See Changes: [junrao] KAFKA-4055; System tests for secure quotas -- [...truncated 5651 lines...] kafka.server.OffsetCommitTest > testCommitAndFetchOffsets PASSED kafka.server.OffsetCommitTest

[jira] [Resolved] (KAFKA-3383) Producer should not remove an in flight request before successfully parsing the response.

[ https://issues.apache.org/jira/browse/KAFKA-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-3383. - Resolution: Won't Fix Fix Version/s: (was: 0.10.1.0) 0.10.0.0 The pr

[jira] [Updated] (KAFKA-1196) java.lang.IllegalArgumentException Buffer.limit on FetchResponse.scala + 33

[ https://issues.apache.org/jira/browse/KAFKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1196: Resolution: Fixed Status: Resolved (was: Patch Available) This issue should have been resol

Build failed in Jenkins: kafka-0.10.1-jdk7 #10

See Changes: [junrao] KAFKA-4055; System tests for secure quotas -- [...truncated 12770 lines...] org.apache.kafka.streams.state.internals.InMemoryKeyValueStoreTest > testPutGetRange PASSED or

[jira] [Updated] (KAFKA-4216) Replication Quotas: Control Leader & Follower Throttled Replicas Separately

[ https://issues.apache.org/jira/browse/KAFKA-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4216: Summary: Replication Quotas: Control Leader & Follower Throttled Replicas Separately (was: Replicat