[jira] [Commented] (KAFKA-3964) Metadata update requests are sometimes received after LeaderAndIsrRequests

[ https://issues.apache.org/jira/browse/KAFKA-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489237#comment-15489237 ] Krishna commented on KAFKA-3964: We are facing similar issue, did we find any workaround Broker 211

Re: [VOTE] KIP-79 - ListOffsetRequest v1 and search by timestamp methods in new consumer.

+1 and thanks for the great proposal! On Fri, Sep 9, 2016 at 4:38 PM, Becket Qin wrote: > Hi all, > > I'd like to start the voting for KIP-79 > > In short we propose to : > 1. add a ListOffsetRequest/ListOffsetResponse v1, and > 2. add earliestOffsts(), latestOffsets() and

[jira] [Commented] (KAFKA-4161) Allow connectors to request flush via the context

[ https://issues.apache.org/jira/browse/KAFKA-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489179#comment-15489179 ] Ewen Cheslack-Postava commented on KAFKA-4161: -- [~shikhar] Probably worth clarifying whether

Re: [VOTE] 0.10.1 Release Plan

+1 (non-binding) On Tue, Sep 13, 2016 at 5:33 PM, Dana Powers wrote: > +1 >

Re: [DISCUSS] KIP-79 - ListOffsetRequest v1 and offsetForTime() method in new consumer.

Thanks Becket. I don't have a strong preference for *And* naming convention, I just thought it was a little weird to have two offset APIs in the same class which used a different convention. I'll go either way if others disagree. The rest sounds good to me. -Jason On Tue, Sep 13, 2016 at 5:43

Re: [DISCUSS] KIP-79 - ListOffsetRequest v1 and offsetForTime() method in new consumer.

Thanks for the review Jason. I am fine with either name. I was thinking that our Scala class names are in the format of *And* pattern while the Java class is more concise. e.g TopicAndPartition vs TopicPartition. But it seems not a general convention. OffsetAndTimestamp sounds good to me. I just

[jira] [Assigned] (KAFKA-4108) Improve DumpLogSegments offsets-decoder output format

[ https://issues.apache.org/jira/browse/KAFKA-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4108: -- Assignee: Vahid Hashemian > Improve DumpLogSegments offsets-decoder output format >

[jira] [Resolved] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

[ https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-4158. --- Resolution: Fixed Pushed to trunk. Not sure if we need this in 0.9 since there is an easy work-around

[jira] [Commented] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

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

[jira] [Created] (KAFKA-4161) Allow connectors to request flush via the context

Shikhar Bhushan created KAFKA-4161: -- Summary: Allow connectors to request flush via the context Key: KAFKA-4161 URL: https://issues.apache.org/jira/browse/KAFKA-4161 Project: Kafka Issue

[GitHub] kafka pull request #1851: KAFKA-4158; Reset quota to default value if quota ...

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

Re: [VOTE] 0.10.1 Release Plan

+1

[jira] [Commented] (KAFKA-4148) KIP-79 add ListOffsetRequest v1 and search by timestamp interface to consumer.

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

[GitHub] kafka pull request #1852: KAFKA-4148: KIP-79 ListOffsetRequest v1 and add se...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1852 KAFKA-4148: KIP-79 ListOffsetRequest v1 and add search offsets by timestamp in consumer You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-4160) Consumer onPartitionsRevoked should not be invoked while holding the coordinator lock

Jason Gustafson created KAFKA-4160: -- Summary: Consumer onPartitionsRevoked should not be invoked while holding the coordinator lock Key: KAFKA-4160 URL: https://issues.apache.org/jira/browse/KAFKA-4160

[jira] [Commented] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488853#comment-15488853 ] Jason Gustafson commented on KAFKA-: Admittedly, the line may not be totally clear, but we

Re: [VOTE] KIP-54: Sticky Partition Assignment Strategy

Thanks for the KIP. +1 from me. On Tue, Sep 13, 2016 at 12:05 PM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Hi all, > > Thanks for providing feedback on this KIP so far. > The KIP was discussed during the KIP meeting today and there doesn't seem > to be any unaddressed issue at

Re: [VOTE] 0.10.1 Release Plan

+1 (non-binding) Thanks. --Vahid From: Ashish Singh To: "dev@kafka.apache.org" Date: 09/13/2016 04:13 PM Subject:Re: [VOTE] 0.10.1 Release Plan +1 (non-binding) On Tue, Sep 13, 2016 at 3:53 PM, Joel Koshy

Re: [VOTE] 0.10.1 Release Plan

+1 (non-binding) On Tue, Sep 13, 2016 at 3:53 PM, Joel Koshy wrote: > +1 > > On Tue, Sep 13, 2016 at 2:40 PM, Jason Gustafson > wrote: > > > Hi All, > > > > I'd like to start a vote on the release plan documented here: > >

[jira] [Updated] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

[ https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-4158: -- Fix Version/s: 0.10.1.0 > Reset quota to default value if quota override is deleted for a given

Re: [VOTE] 0.10.1 Release Plan

+1 On Tue, Sep 13, 2016 at 2:40 PM, Jason Gustafson wrote: > Hi All, > > I'd like to start a vote on the release plan documented here: > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. I > went ahead and included KIP-55 since Jun said it may have a

[jira] [Comment Edited] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488682#comment-15488682 ] Vahid Hashemian edited comment on KAFKA-4126 at 9/13/16 10:43 PM: --

[jira] [Commented] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488682#comment-15488682 ] Vahid Hashemian commented on KAFKA-4126: [~balazs.barnabas] [~omkreddy] When I try this use case

Re: Kafka KIP meeting Sep 13 at 11:00am PST

The following are the notes from today's KIP discussion: - KIP-54 (Sticky Partition Assignment): aims to minimise partition movement so that resource reinitialisation (e.g. caches) is minimised. It is partially sticky and partially fair. Some concerns around the fact that user code for

[jira] [Commented] (KAFKA-2307) Drop ConsumerOffsetChecker completely

[ https://issues.apache.org/jira/browse/KAFKA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488674#comment-15488674 ] Jason Gustafson commented on KAFKA-2307: Sounds good. I'll kick this to the next release then. >

[jira] [Updated] (KAFKA-2307) Drop ConsumerOffsetChecker completely

[ https://issues.apache.org/jira/browse/KAFKA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2307: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Drop ConsumerOffsetChecker

Re: [VOTE] 0.10.1 Release Plan

+1 (binding) > On Sep 13, 2016, at 3:03 PM, Guozhang Wang wrote: > > +1 (binding) > >> On Tue, Sep 13, 2016 at 2:53 PM, Ismael Juma wrote: >> >> +1 (binding) >> >>> On Tue, Sep 13, 2016 at 10:52 PM, Gwen Shapira wrote: >>> >>> +1

Re: [DISCUSS] KIP-79 - ListOffsetRequest v1 and offsetForTime() method in new consumer.

Hey Becket, I looked at the most recent version and it's looking good to me. One very minor question on naming: do you think OffsetAndTimestamp would be a more consistent name than TimestampOffset given some of our other naming (e.g. OffsetAndMetadata)? I put the "Offset" first since the name

Re: [VOTE] 0.10.1 Release Plan

+1 (binding) On Tue, Sep 13, 2016 at 2:53 PM, Ismael Juma wrote: > +1 (binding) > > On Tue, Sep 13, 2016 at 10:52 PM, Gwen Shapira wrote: > > > +1 (binding) - yay for a new release! > > > > On Tue, Sep 13, 2016 at 2:40 PM, Jason Gustafson

Re: [VOTE] 0.10.1 Release Plan

+1 binding -Ewen On Tue, Sep 13, 2016 at 2:53 PM, Ismael Juma wrote: > +1 (binding) > > On Tue, Sep 13, 2016 at 10:52 PM, Gwen Shapira wrote: > > > +1 (binding) - yay for a new release! > > > > On Tue, Sep 13, 2016 at 2:40 PM, Jason Gustafson

Re: [VOTE] 0.10.1 Release Plan

+1 (binding) On Tue, Sep 13, 2016 at 10:52 PM, Gwen Shapira wrote: > +1 (binding) - yay for a new release! > > On Tue, Sep 13, 2016 at 2:40 PM, Jason Gustafson > wrote: > > > Hi All, > > > > I'd like to start a vote on the release plan documented here: >

Re: [VOTE] 0.10.1 Release Plan

+1 (binding) - yay for a new release! On Tue, Sep 13, 2016 at 2:40 PM, Jason Gustafson wrote: > Hi All, > > I'd like to start a vote on the release plan documented here: > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. I > went ahead and included

[VOTE] 0.10.1 Release Plan

Hi All, I'd like to start a vote on the release plan documented here: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. I went ahead and included KIP-55 since Jun said it may have a chance, but note that in-progress KIPs will only be included if they are ready by the feature

[jira] [Commented] (KAFKA-2359) New consumer - partitions auto assigned only on poll

[ https://issues.apache.org/jira/browse/KAFKA-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488276#comment-15488276 ] Ed Tyrrill commented on KAFKA-2359: --- Hi Elias, Calling pause() causes the same IllegalArgumentException

[VOTE] KIP-54: Sticky Partition Assignment Strategy

Hi all, Thanks for providing feedback on this KIP so far. The KIP was discussed during the KIP meeting today and there doesn't seem to be any unaddressed issue at this point. So I would like to initiate the voting process. The KIP can be found here:

[jira] [Commented] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

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

Kafka producer batching improvements.

Hi All, We are running a 10 node kafka cluster with a theoretical peak message handling rate of more than 2 million (1KB) messages per second, but we are running into bottlenecks on Kafka producer scaling it beyond 150K request per sec. *Our Configuration* We have a 10 node kafka cluster on

[GitHub] kafka pull request #1851: KAFKA-4158; Reset quota to default value if quota ...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/1851 KAFKA-4158; Reset quota to default value if quota override is deleted You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kafka

[jira] [Commented] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487885#comment-15487885 ] Alexey Ozeritskiy commented on KAFKA-2063: -- Thanks Andrey, I agree with you. > Bound fetch

[jira] [Created] (KAFKA-4159) Allow overriding producer & consumer properties at the connector level

Shikhar Bhushan created KAFKA-4159: -- Summary: Allow overriding producer & consumer properties at the connector level Key: KAFKA-4159 URL: https://issues.apache.org/jira/browse/KAFKA-4159 Project:

[jira] [Updated] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

[ https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4158: Description: If user set a quota override and delete it override, Kafka will still use the quota override.

[jira] [Created] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

Dong Lin created KAFKA-4158: --- Summary: Reset quota to default value if quota override is deleted for a given clientId Key: KAFKA-4158 URL: https://issues.apache.org/jira/browse/KAFKA-4158 Project: Kafka

Re: Kafka KIP meeting Sep 13 at 11:00am PST

Sure, done. Ismael On Mon, Sep 12, 2016 at 5:31 PM, Renu Tewari wrote: > Hi Ismael > Could you please add me to the invite. > > rtew...@linkedin.com > > regards > Renu > > > On Mon, Sep 12, 2016 at 8:39 AM, Ismael Juma wrote: > > > Hi, Everyone, > > > >

[jira] [Commented] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

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

[GitHub] kafka pull request #1850: KAFKA-2000: Delete topic should also delete consum...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1850 KAFKA-2000: Delete topic should also delete consumer offsets. You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka KAFKA-2700-DELETE

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

the specific memory pool implementation i wrote will allocate _any_ amount you request if it has _any_ memory available (so if it has 1 byte available and you ask for 1MB you will get 1MB and the counter will go negative). this was done to avoid issues with starvation of large requests. other

[jira] [Commented] (KAFKA-4155) Remove WorkerGroupMember from Connect

[ https://issues.apache.org/jira/browse/KAFKA-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487618#comment-15487618 ] Ewen Cheslack-Postava commented on KAFKA-4155: -- [~hachikuji] One drawback I see is that we

[jira] [Commented] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487428#comment-15487428 ] Andrey Neporada commented on KAFKA-2063: Alexey, current PR

[GitHub] kafka pull request #1849: KAFKA-4157: Transient system test failure in repli...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1849 KAFKA-4157: Transient system test failure in replica_verification_tes… …t.test_replica_lags You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-4157) Transient system test failure in replica_verification_test.test_replica_lags

Grant Henke created KAFKA-4157: -- Summary: Transient system test failure in replica_verification_test.test_replica_lags Key: KAFKA-4157 URL: https://issues.apache.org/jira/browse/KAFKA-4157 Project:

[jira] [Updated] (KAFKA-4157) Transient system test failure in replica_verification_test.test_replica_lags

[ https://issues.apache.org/jira/browse/KAFKA-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-4157: --- Status: Patch Available (was: Open) > Transient system test failure in

[jira] [Commented] (KAFKA-4157) Transient system test failure in replica_verification_test.test_replica_lags

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

[jira] [Updated] (KAFKA-3930) IPv6 address can't used as ObjectName

[ https://issues.apache.org/jira/browse/KAFKA-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3930: -- Status: Patch Available (was: Open) > IPv6 address can't used as ObjectName >

[GitHub] kafka pull request #1848: KAFKA-3930: Replace colon in ipv6 addresses used i...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1848 KAFKA-3930: Replace colon in ipv6 addresses used in metrics tags You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

[jira] [Commented] (KAFKA-3930) IPv6 address can't used as ObjectName

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

[jira] [Commented] (KAFKA-3913) Old consumer's metrics error when using IPv6

[ https://issues.apache.org/jira/browse/KAFKA-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487235#comment-15487235 ] Rajini Sivaram commented on KAFKA-3913: --- Fixing under KAFKA-3930. > Old consumer's metrics error

[jira] [Commented] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487219#comment-15487219 ] Stephen Powis commented on KAFKA-: -- I'm not advocating for *replacing* the existing

[jira] [Assigned] (KAFKA-3930) IPv6 address can't used as ObjectName

[ https://issues.apache.org/jira/browse/KAFKA-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-3930: - Assignee: Rajini Sivaram > IPv6 address can't used as ObjectName >

[jira] [Commented] (KAFKA-2307) Drop ConsumerOffsetChecker completely

[ https://issues.apache.org/jira/browse/KAFKA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487141#comment-15487141 ] Ismael Juma commented on KAFKA-2307: I think the plan is to do all removals when we do the next major

Kafka Consumer Partition Logic

Hi, I want to know how kafka consumer consumes from partitions to which it is connected,which logic it follows ,when kafka consumer is connected to more than one partition and i have given only one stream for connection

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

Is there any value in allowing the 4-byte size to be read even when the request memory limit has been reached? If not, you can disable OP_READ interest for all channels that are ready inside Selector.poll() when memory limit has been reached and re-enable before returning from poll(). Perhaps a

[jira] [Updated] (KAFKA-4079) Document quota configuration changes from KIP-55

[ https://issues.apache.org/jira/browse/KAFKA-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4079: -- Status: Patch Available (was: Open) > Document quota configuration changes from KIP-55 >

[jira] [Commented] (KAFKA-4079) Document quota configuration changes from KIP-55

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

[GitHub] kafka pull request #1847: KAFKA-4079: Documentation for secure quotas

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1847 KAFKA-4079: Documentation for secure quotas Details in KIP-55. You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

Re: Agenda item for next KIP meeting

Sure, done. Ismael On Tue, Sep 13, 2016 at 6:08 AM, Becket Qin wrote: > Hey Ismael, > > I probably replied too late, but is it possible to add KIP-79 to the agenda > as well? > > Jiangjie (Becket) Qin > > On Fri, Sep 9, 2016 at 9:57 AM, radai

[jira] [Assigned] (KAFKA-438) Code cleanup in MessageTest

[ https://issues.apache.org/jira/browse/KAFKA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Singh reassigned KAFKA-438: -- Assignee: Chetan Singh > Code cleanup in MessageTest > --- > >

[jira] [Updated] (KAFKA-438) Code cleanup in MessageTest

[ https://issues.apache.org/jira/browse/KAFKA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Singh updated KAFKA-438: --- Assignee: (was: Chetan Singh) > Code cleanup in MessageTest > --- > >

Re: Not able to download tests jar of kafka and kafka-streams from maven repo.

adding missing classifier parameter.. org.apache.kafka kafka-streams 0.10.0.0 test-jar test On Tue, Sep 13, 2016 at 12:07 PM, Manikumar Reddy wrote: > Hi, > > Kafka uses "test" as classifier (default is "tests" ) for test jars. > We can add test parameter to

Re: Not able to download tests jar of kafka and kafka-streams from maven repo.

Hi, Kafka uses "test" as classifier (default is "tests" ) for test jars. We can add test parameter to dependency tag to resolve the error. org.apache.kafka kafka-streams 0.10.0.0 test-jar test Thanks Manikumar On Tue, Sep

[jira] [Commented] (KAFKA-4156) Not able to download tests jar of kafka and kafka-streams from maven repo.

[ https://issues.apache.org/jira/browse/KAFKA-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486424#comment-15486424 ] Satish Duggana commented on KAFKA-4156: --- It works fine when classifier with value as test is used

[jira] [Updated] (KAFKA-4156) Not able to download tests jar of kafka and kafka-streams from maven repo.

[ https://issues.apache.org/jira/browse/KAFKA-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated KAFKA-4156: -- Priority: Major (was: Blocker) > Not able to download tests jar of kafka and kafka-streams

[jira] [Updated] (KAFKA-4156) Not able to download tests jar of kafka and kafka-streams from maven repo.

[ https://issues.apache.org/jira/browse/KAFKA-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated KAFKA-4156: -- Description: Below dependency is added in one of our repos to use EmbeddedKafkaCluster but

Not able to download tests jar of kafka and kafka-streams from maven repo.

Hi, Below dependency is added in one of our repos to use EmbeddedKafkaCluster but dependency installation fails with an error mentioned later. org.apache.kafka kafka-streams 0.10.0.0 test-jar test This fails with an

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

See

[jira] [Created] (KAFKA-4156) Not able to download tests jar of kafka and kafka-streams from maven repo.

Satish Duggana created KAFKA-4156: - Summary: Not able to download tests jar of kafka and kafka-streams from maven repo. Key: KAFKA-4156 URL: https://issues.apache.org/jira/browse/KAFKA-4156 Project:

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

See