Jenkins build is back to normal : kafka_0.9.0_jdk7 #120

See

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

See Changes: [cshapi] KAFKA-3141: Add checks to catch invalid authorizer porperties [cshapi] KAFKA-3162: Added producer and consumer interceptors -- [...truncated 2822 lines...] kafka.log.FileM

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

See Changes: [cshapi] KAFKA-3141: Add checks to catch invalid authorizer porperties [cshapi] KAFKA-3162: Added producer and consumer interceptors -- Started by an SCM change [EnvInject] - Loadi

[jira] [Updated] (KAFKA-3162) KIP-42: Add Producer and Consumer Interceptors

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

[jira] [Commented] (KAFKA-3162) KIP-42: Add Producer and Consumer Interceptors

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

[GitHub] kafka pull request: KAFKA-3162: Added producer and consumer interc...

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

[jira] [Commented] (KAFKA-3141) kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid authorizer-property

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

[jira] [Updated] (KAFKA-3141) kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid authorizer-property

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

[GitHub] kafka pull request: KAFKA-3141: Add checks to catch invalid author...

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

[jira] [Updated] (KAFKA-2508) Replace UpdateMetadata{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2508: --- Status: Patch Available (was: Open) > Replace UpdateMetadata{Request,Response} with > org.apache.kaf

[jira] [Commented] (KAFKA-2508) Replace UpdateMetadata{Request,Response} with org.apache.kafka.common.requests equivalent

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

[GitHub] kafka pull request: KAFKA-2508: Replace UpdateMetadata{Request,Res...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/896 KAFKA-2508: Replace UpdateMetadata{Request,Response} with o.a.k.c.req… …uests equivalent You can merge this pull request into a Git repository by running: $ git pull https://github.com/gr

[jira] [Updated] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

[ https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3221: -- Status: Patch Available (was: Open) > kafka-acls.sh must verify if a user has sufficient privil

[jira] [Updated] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

[ https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3221: -- Fix Version/s: 0.9.0.1 > kafka-acls.sh must verify if a user has sufficient privileges to perfor

[jira] [Commented] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

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

[GitHub] kafka pull request: KAFKA-3221: Pass requesting user information t...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/895 KAFKA-3221: Pass requesting user information to authorizer to enable … …user authorization before modifying acls. You can merge this pull request into a Git repository by running: $ git p

[jira] [Updated] (KAFKA-2923) Improve 0.9.0 Upgrade Documents

[ https://issues.apache.org/jira/browse/KAFKA-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2923: --- Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Improve 0.9.0 Upgrade Documents >

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

Hi Becket, Good points. Some comments inline. On Tue, Feb 9, 2016 at 8:45 PM, Becket Qin wrote: > Good point on the upgrade path. The release plan says that 0.10.0.0 is > targeted in Q2, 2016. If that is accurate, there are 6-7 months between > 0.9.0.0 and 0.10.0.0, i.e. there are still about f

Build failed in Jenkins: kafka_0.9.0_jdk7 #119

See Changes: [junrao] KAFKA-3159; stale high watermark segment offset causes early fetch -- [...truncated 2270 lines...] kafka.server.OffsetCommitTest > testUpdateOffsets PASSED kafka.server.Of

[jira] [Commented] (KAFKA-2750) Sender.java: handleProduceResponse does not check protocol version

[ https://issues.apache.org/jira/browse/KAFKA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140105#comment-15140105 ] Joel Koshy commented on KAFKA-2750: --- [~felixgv] You mean retry with the older protocol?

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

See

[GitHub] kafka pull request: MINOR: add setUncaughtExceptionHandler to Kafk...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/894 MINOR: add setUncaughtExceptionHandler to KafkaStreams You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka minor Alternatively you c

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140054#comment-15140054 ] Ismael Juma commented on KAFKA-3159: Good news [~ra...@signalfx.com], thanks for repor

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140049#comment-15140049 ] Rajiv Kurian commented on KAFKA-3159: - I am running a patched broker with a consumer c

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

See Changes: [junrao] KAFKA-3159; stale high watermark segment offset causes early fetch -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (d

[GitHub] kafka pull request: HOTFIX: poll even when all partitions are paus...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/893 HOTFIX: poll even when all partitions are paused. handle concurrent cleanup * We need to poll periodically even when all partitions are paused in order to respond to a possible rebalance promptly.

[jira] [Updated] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

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

[GitHub] kafka pull request: KAFKA-3159: stale high watermark segment offse...

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

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

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

Stormkafka deploy error

Hi guys, I am a Kafka newbie. An error occurred when I run following command#sudo ./storm jar [jar-path] [topology class] [topology name]  The error tracking is here:**Exception in thread "main" java.lang.NoClassDefFoundError: storm/kafka/BrokerHosts       

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

See Changes: [me] HOTFIX: open window segments in order, add segment id check in -- [...truncated 82 lines...] /x1/jenkins/jenkins-slave/workspace/kafka-trunk-jdk8/core/src/main/scala/kafka/serve

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

See Changes: [me] HOTFIX: open window segments in order, add segment id check in -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-4 (dock

[jira] [Commented] (KAFKA-2375) Implement elasticsearch Copycat sink connector

[ https://issues.apache.org/jira/browse/KAFKA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139836#comment-15139836 ] Ewen Cheslack-Postava commented on KAFKA-2375: -- [~arttii] Great to hear you'r

[jira] [Updated] (KAFKA-3187) Make kafka-acls.sh help messages more generic.

[ https://issues.apache.org/jira/browse/KAFKA-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3187: -- Fix Version/s: 0.9.0.1 > Make kafka-acls.sh help messages more generic. > --

[jira] [Updated] (KAFKA-3187) Make kafka-acls.sh help messages more generic.

[ https://issues.apache.org/jira/browse/KAFKA-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3187: -- Affects Version/s: 0.9.0.0 > Make kafka-acls.sh help messages more generic. > --

[jira] [Commented] (KAFKA-3187) Make kafka-acls.sh help messages more generic.

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

[jira] [Updated] (KAFKA-3187) Make kafka-acls.sh help messages more generic.

[ https://issues.apache.org/jira/browse/KAFKA-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3187: -- Status: Patch Available (was: Open) > Make kafka-acls.sh help messages more generic. >

[GitHub] kafka pull request: KAFKA-3187: Make kafka-acls.sh help messages m...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/892 KAFKA-3187: Make kafka-acls.sh help messages more generic. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA-3187 Altern

[jira] [Commented] (KAFKA-2750) Sender.java: handleProduceResponse does not check protocol version

[ https://issues.apache.org/jira/browse/KAFKA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139784#comment-15139784 ] Felix GV commented on KAFKA-2750: - Shouldn't the producer automatically do a graceful degr

[GitHub] kafka pull request: HOTFIX: open window segments in order, add seg...

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

Re: [DISCUSS] KIP-46: Self Healing

Hi Neha, Thanks for the detailed reply and apologies for my late response. I do have a few comments. 1. Replica Throttling - I agree this is rather important to get done. However, it may also be argued that this problem is orthogonal. We do not have these protections currently yet we do run parti

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

Hi Ismael, Good point on the upgrade path. The release plan says that 0.10.0.0 is targeted in Q2, 2016. If that is accurate, there are 6-7 months between 0.9.0.0 and 0.10.0.0, i.e. there are still about five months before the next release. Our previous documentation only provides documentation on

[GitHub] kafka pull request: MINOR: Stabilize transient replication test fa...

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

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

See Changes: [cshapi] KAFKA-3216: "Modifying topics" section incorrectly says you can't change -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

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

See

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

See Changes: [me] KAFKA-3217: Close producers in unit tests [me] HOTFIX: Fix NPE after standby task reassignment [me] KAFKA-3189: Kafka server returns UnknownServerException for inherited [cshapi] KAFKA-3216: "Modifying topics" sect

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

Hi Becket, Thanks for starting the discussion. Given the significance of the changes, I think 0.10.0.0 is appropriate. However, I think we have to be careful about the fact that we will be releasing two major releases within a short period of time. This means that 0.10.0.0 may be out before many

[jira] [Commented] (KAFKA-3216) "Modifying topics" section incorrectly says you can't change replication factor.

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

[jira] [Updated] (KAFKA-3216) "Modifying topics" section incorrectly says you can't change replication factor.

[ https://issues.apache.org/jira/browse/KAFKA-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3216: Resolution: Fixed Fix Version/s: 0.9.1.0 0.9.0.1 Status: Resolve

[GitHub] kafka pull request: KAFKA-3216: "Modifying topics" section incorre...

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

[jira] [Updated] (KAFKA-3216) "Modifying topics" section incorrectly says you can't change replication factor.

[ https://issues.apache.org/jira/browse/KAFKA-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng updated KAFKA-3216: --- Status: Patch Available (was: Open) > "Modifying topics" section incorrectly says you can't change re

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

sure, why not :) On Tue, Feb 9, 2016 at 10:07 AM, Becket Qin wrote: > Hi All, > > Next Kafka release will have several significant important new > feature/changes such as Kafka Stream, Message Format Change, Client > Interceptors and several new consumer API changes, etc. We feel it is > better

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

+1 on 0.10.0.0 On Tue, Feb 9, 2016 at 10:09 AM, Stevo Slavić wrote: > +1 0.10.0.0 > > On Tue, Feb 9, 2016, 19:08 Becket Qin wrote: > > > Hi All, > > > > Next Kafka release will have several significant important new > > feature/changes such as Kafka Stream, Message Format Change, Client > > Int

[jira] [Commented] (KAFKA-3189) Kafka server returns UnknownServerException for inherited exceptions

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

[jira] [Updated] (KAFKA-3189) Kafka server returns UnknownServerException for inherited exceptions

[ https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3189: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[GitHub] kafka pull request: KAFKA-3189: Kafka server returns UnknownServer...

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

[GitHub] kafka pull request: HOTFIX: open window segments in order, add seg...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/891 HOTFIX: open window segments in order, add segment id check in getSegment * During window store initialization, we have to open segments in the segment id order and update ```currentSegmentId```, ot

Re: [POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

+1 0.10.0.0 On Tue, Feb 9, 2016, 19:08 Becket Qin wrote: > Hi All, > > Next Kafka release will have several significant important new > feature/changes such as Kafka Stream, Message Format Change, Client > Interceptors and several new consumer API changes, etc. We feel it is > better to make nex

[POLL] Make next Kafka Release 0.10.0.0 instead of 0.9.1.0

Hi All, Next Kafka release will have several significant important new feature/changes such as Kafka Stream, Message Format Change, Client Interceptors and several new consumer API changes, etc. We feel it is better to make next Kafka release 0.10.0.0 instead of 0.9.1.0. We would like to see what

[jira] [Assigned] (KAFKA-3093) Keep track of connector and task status info, expose it via the REST API

[ https://issues.apache.org/jira/browse/KAFKA-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-3093: -- Assignee: Jason Gustafson (was: jin xing) > Keep track of connector and task status in

[GitHub] kafka pull request: MINOR: Stabilize transient replication test fa...

GitHub user granders opened a pull request: https://github.com/apache/kafka/pull/890 MINOR: Stabilize transient replication test failures in 0.9.0 - ported timeout values in `produce_consume_validate.py` from trunk to 0.9.0 - ported `producer_throughput_value` in `replication_tes

[GitHub] kafka pull request: HOTFIX: fix NPE after standby task reassignmen...

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

[GitHub] kafka pull request: KAFKA-3217: Close producers in unit tests

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

[jira] [Commented] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

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

[jira] [Updated] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

[ https://issues.apache.org/jira/browse/KAFKA-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3217: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

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

See Changes: [me] MINOR: Use explicit type in AclCommand -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu ubuntu yahoo-not-h2

[GitHub] kafka pull request: HOTFIX: fix NPE after standby task reassignmen...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/889 HOTFIX: fix NPE after standby task reassignment Buffered records of change logs must be cleared upon reassignment of standby tasks. You can merge this pull request into a Git repository by running

[GitHub] kafka pull request: MINOR: Use explicit type in AclCommand

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

[jira] [Commented] (KAFKA-611) Migration tool and Mirror Maker ignore mirror.topics.whitelist in config

[ https://issues.apache.org/jira/browse/KAFKA-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139187#comment-15139187 ] Joe Hohertz commented on KAFKA-611: --- I've recently run into this in MirrorMaker, and am c

[DISCUSS] KIP-47 - Add timestamp-based log deletion policy

Hello, I just submitted KIP-47 for adding a new log deletion policy based on a minimum timestamp of messages to retain. https://cwiki.apache.org/confluence/display/KAFKA/KIP-47+-+Add+timestamp-based+log+deletion+policy I'm open to any comments or suggestions. Thanks, Bill Warshaw

[jira] [Updated] (KAFKA-3224) Add timestamp-based log deletion policy

[ https://issues.apache.org/jira/browse/KAFKA-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Warshaw updated KAFKA-3224: Description: One of Kafka's officially-described use cases is a distributed commit log (http://kafk

[jira] [Created] (KAFKA-3224) Add timestamp-based log deletion policy

Bill Warshaw created KAFKA-3224: --- Summary: Add timestamp-based log deletion policy Key: KAFKA-3224 URL: https://issues.apache.org/jira/browse/KAFKA-3224 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3055) JsonConverter mangles schema during serialization (fromConnectData)

[ https://issues.apache.org/jira/browse/KAFKA-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139051#comment-15139051 ] Kishore Senji commented on KAFKA-3055: -- Please look here: https://github.com/ksenji/

[jira] [Commented] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139026#comment-15139026 ] Joe O'Connor commented on KAFKA-3218: - Hi Rajini, Thanks for the suggested workaround,

[jira] [Resolved] (KAFKA-3222) SslProducerSendTest transient failure.

[ https://issues.apache.org/jira/browse/KAFKA-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3222. Resolution: Duplicate > SslProducerSendTest transient failure. > ---

[jira] [Commented] (KAFKA-3222) SslProducerSendTest transient failure.

[ https://issues.apache.org/jira/browse/KAFKA-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138753#comment-15138753 ] Ismael Juma commented on KAFKA-3222: Duplicate of KAFKA-3217. > SslProducerSendTest t

[jira] [Updated] (KAFKA-3223) Add System (ducktape) Test that asserts strict partition ordering despite node failure

[ https://issues.apache.org/jira/browse/KAFKA-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-3223: Description: Kafka provides strong ordering when max.inflight.requests.per.connection = 1. There cu

[jira] [Created] (KAFKA-3223) Add System (ducktape) Test that asserts strict partition ordering despite node failure

Ben Stopford created KAFKA-3223: --- Summary: Add System (ducktape) Test that asserts strict partition ordering despite node failure Key: KAFKA-3223 URL: https://issues.apache.org/jira/browse/KAFKA-3223 Pr

[jira] [Updated] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3218: -- Status: Patch Available (was: Open) The PR addresses the loading of default classes for configu

[jira] [Commented] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

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

[GitHub] kafka pull request: KAFKA-3218: Use static classloading for defaul...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/888 KAFKA-3218: Use static classloading for default config classes Static classloading is better for default classes used in config to ensure that the classes can be loaded in any environment (OSGi