This is such a great proposal. Parallel/Cooperative consumption is a long
missing pattern in Apache Kafka and it is a viable solution for the common
head-of-line-blocking problem. Developers have long attempted to solve this
with bespoke consumer proxies that state manage the inflight payloads, so
Hi Team
I tried upgrading it to 2.13_2.8.0 but still have these vulnerabilities.
[cid:image003.jpg@01D79F3D.5BA06A20]
What is your suggestion on this?
Thanks
Ashish
From: Jake Murphy Smith
Sent: 01 September 2021 09:31
To: Ashish Patil
Subject: RE: [EXTERNAL] Re: Security vulnerabilities in
we have any plan to fix this in the coming version or any suggestions around
this?
Thanks
Ashish
Ashish Surana created KAFKA-10608:
-
Summary: Add support for rolling upgrade with topology changes
Key: KAFKA-10608
URL: https://issues.apache.org/jira/browse/KAFKA-10608
Project: Kafka
ASHISH M VYAS created KAFKA-8596:
Summary: Kafka topic pre-creation error message needs to be passed
to application as an exception
Key: KAFKA-8596
URL: https://issues.apache.org/jira/browse/KAFKA-8596
Ashish Surana created KAFKA-7149:
Summary: Reduce assignment data size to improve kafka streams
scalability
Key: KAFKA-7149
URL: https://issues.apache.org/jira/browse/KAFKA-7149
Project: Kafka
Ashish Surana created KAFKA-6642:
Summary: Rack aware replica assignment in kafka streams
Key: KAFKA-6642
URL: https://issues.apache.org/jira/browse/KAFKA-6642
Project: Kafka
Issue Type: New
Ashish Surana created KAFKA-6555:
Summary: Making state store queryable during restoration
Key: KAFKA-6555
URL: https://issues.apache.org/jira/browse/KAFKA-6555
Project: Kafka
Issue Type
Ashish Kumar created KAFKA-5504:
---
Summary: Kafka controller is not getting elected
Key: KAFKA-5504
URL: https://issues.apache.org/jira/browse/KAFKA-5504
Project: Kafka
Issue Type: Bug
Bc
Sent from my iPhone
B
> On 25-Apr-2017, at 10:21, ASF GitHub Bot (JIRA) wrote:
>
>This message is eligible for Automatic Cleanup! (j...@apache.org) Add
> cleanup rule | More info
>
>[
> https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetab
Hi Team,
I would like to subscribe to Kafka dev group
Thanks,
Ashish Singh
[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752982#comment-15752982
]
Ashish K Singh commented on KAFKA-4541:
---
Yes, it will.
> Add capability to
Ashish K Singh created KAFKA-4542:
-
Summary: Add authentication based on delegation token.
Key: KAFKA-4542
URL: https://issues.apache.org/jira/browse/KAFKA-4542
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749769#comment-15749769
]
Ashish K Singh commented on KAFKA-1696:
---
[~omkreddy] I had to convert this
[
https://issues.apache.org/jira/browse/KAFKA-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-4544:
--
Description: Add system tests for delegation token based authentication.
(was: Add capability
[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh reassigned KAFKA-4541:
-
Assignee: Ashish K Singh
> Add capability to create delegation to
[
https://issues.apache.org/jira/browse/KAFKA-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-4544:
--
Summary: Add system tests for delegation token based authentication (was:
Add capability to
Ashish K Singh created KAFKA-4543:
-
Summary: Add capability to renew/expire delegation tokens.
Key: KAFKA-4543
URL: https://issues.apache.org/jira/browse/KAFKA-4543
Project: Kafka
Issue Type
Ashish K Singh created KAFKA-4544:
-
Summary: Add capability to renew/expire delegation tokens.
Key: KAFKA-4544
URL: https://issues.apache.org/jira/browse/KAFKA-4544
Project: Kafka
Issue Type
Ashish K Singh created KAFKA-4541:
-
Summary: Add capability to create delegation token
Key: KAFKA-4541
URL: https://issues.apache.org/jira/browse/KAFKA-4541
Project: Kafka
Issue Type: Sub
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-1696:
--
Issue Type: New Feature (was: Sub-task)
Parent: (was: KAFKA-1682)
> Kafka sho
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746886#comment-15746886
]
Ashish K Singh commented on KAFKA-1696:
---
[~omkreddy] as I indicated on discuss
with the following:
>
> 1. Protocol and Config changes
>
> 2. format of the data stored in ZK.
>
> 3. Changes to Java Clients/Usage of SASL SCRAM mechanism
>
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
>
> 48+Delegation+token+support+f
e). So Kerberos and SSL are not required (although commonly used).
>
> Ismael
>
> On Fri, Dec 9, 2016 at 6:59 PM, Ashish Singh wrote:
>
> > Hey,
> >
> > No it does not. Without kerberos or ssl, all requests will appear to come
> > from anonymous user, and
upport ACL's with out kerberos/SSL?
>
> Any info on this would be greatly helpful.
>
>
> Thanks
>
--
Regards,
Ashish
On Wed, Nov 30, 2016, at 11:17, Colin McCabe wrote:
> > Thanks, Ashish. I think the idea of having the client make an
> > ApiVersionRequest call when it starts up is a good one. This idea is
> > described in both KIP-97, and the KAFKA-3600 patches. I also think we
> > ought
Ashish K Singh created KAFKA-4482:
-
Summary: Kafka streams test failure and hang causing PR builds to
fail
Key: KAFKA-4482
URL: https://issues.apache.org/jira/browse/KAFKA-4482
Project: Kafka
happy to
rebase KAFKA-3600 on trunk. However, any comments/ feedback on KAFKA-3600's
approach on maintaining api version info for each connected broker is
highly welcome.
On Wed, Nov 30, 2016 at 5:47 AM, Ismael Juma wrote:
> Thanks Colin, I think this is a good improvement.
>
> Ashis
[
https://issues.apache.org/jira/browse/KAFKA-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh resolved KAFKA-3309.
---
Resolution: Duplicate
> Update Protocol Documentation WIP pa
On Tue, Nov 29, 2016 at 4:11 PM, Colin McCabe wrote:
> On Tue, Nov 29, 2016, at 11:39, Ashish Singh wrote:
> > Hello Colin,
> >
> > In the KIP you mentioned that currently the client uses supported api
> > versions information to check if the server supports its de
icy. If you're interested, please check out:
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 97%3A+Improved+Kafka+Compatibility+Policy
> >
> > cheers,
> > Colin
>
--
Regards,
Ashish
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706209#comment-15706209
]
Ashish K Singh commented on KAFKA-1696:
---
[~omkreddy] would you be able to pro
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706077#comment-15706077
]
Ashish K Singh commented on KAFKA-1696:
---
It has been a while, since any prog
Please subscribe me to this group
ntalapani
> wrote:
> > The only pending update for the KIP is to write up the protocol changes
> like
> > we've it KIP-4. I'll update the wiki.
> >
> >
> > On Thu, Sep 15, 2016 at 4:27 PM Ashish Singh
> wrote:
> >>
> >> I think we dec
ssion was dead for a while. Are there still contentious
> points? If not, why are there no votes?
>
> On Tue, Aug 23, 2016 at 1:26 PM, Jun Rao wrote:
> > Ashish,
> >
> > Yes, I will send out a KIP invite for next week to discuss KIP-48 and
> other
> > remaining
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 freeze date (Sep. 17). We'll evaluate KIP-79 once we see Becket's
> > patch.
> >
> > Thanks,
> > Jason
> >
>
--
Regards,
Ashish
[
https://issues.apache.org/jira/browse/KAFKA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478402#comment-15478402
]
Ashish K Singh commented on KAFKA-4145:
---
+1, testFlush has been one of the
contributed numerous patches to a wide range of areas,
> > > notably
> > > > > within the new consumer and the Kafka Connect layers. He has
> > displayed
> > > > > great taste and judgement which has been apparent through his
> > > involvement
> > > > > across the board from mailing lists, JIRA, code reviews to
> > contributing
> > > > > features, bug fixes and code and documentation improvements.
> > > > >
> > > > > Thank you for your contribution and welcome to Apache Kafka, Jason!
> > > > > --
> > > > > Thanks,
> > > > > Neha
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
--
Ashish 🎤h
[
https://issues.apache.org/jira/browse/KAFKA-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457099#comment-15457099
]
Ashish K Singh commented on KAFKA-3148:
---
[~revans2] since you have figured out
harder to find than files on disk.
- The perms also protect the executable.
- The file sits on an ephemeral disk that’s mounted to memory, so
stealing a physical disk won’t result in getting even the encrypted
password.
On Thu, Aug 25, 2016 at 9:07 AM, Gwen Shapira wrote:
Hi Ashish
he.org/jira/browse/KAFKA-2629
POC: https://github.com/apache/kafka/pull/1770
Thanks
--
Regards,
Ashish
KIP-48 delegation token : Ashish will ping Harsh to see if this is
still active.
Harsha just replied and he will be willing to join in next KIP call to
discuss more about KIP-48.
On Tue, Aug 23, 2016 at 1:22 PM, Jun Rao wrote:
The following are the notes from today's KIP discu
10 PM, Harsha Chintalapani
wrote:
> Ashish,
> Yes we are working on it. Lets discuss in the next KIP meeting.
> I'll join.
> -Harsha
>
> On Tue, Aug 23, 2016 at 12:07 PM Ashish Singh wrote:
>
> > Hello Harsha,
> >
> > Are you still working on thi
Hello Harsha,
Are you still working on this? Wondering if we can discuss this in next KIP
meeting, if you can join.
On Mon, Jul 18, 2016 at 9:51 AM, Harsha Chintalapani
wrote:
> Hi Grant,
> We are working on it. Will add the details to KIP about the
> request protocol.
>
> Thanks,
> H
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431725#comment-15431725
]
Ashish K Singh commented on KAFKA-2629:
---
[~bharatviswa] just posted a WIP p
; Kafka
> > > PMC.
> > >
> > > Congratulations, Gwen!
> > >
> > > Jun
> > >
> >
>
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> gr...@cloudera.com | twitter.com/gchenke |
> linkedin.com/in/granthenke
>
--
Ashish 🎤h
[
https://issues.apache.org/jira/browse/KAFKA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-4052:
--
Status: Patch Available (was: Open)
> Allow passing properties file to ProducerPerforma
Ashish K Singh created KAFKA-4052:
-
Summary: Allow passing properties file to ProducerPerformance
Key: KAFKA-4052
URL: https://issues.apache.org/jira/browse/KAFKA-4052
Project: Kafka
Issue
reviewer here) who understands and agrees with
> the design improves the discussion a lot.
>
> Gwen
>
> On Mon, Aug 15, 2016 at 8:27 AM, Ashish Singh wrote:
> > Hello Dana,
> >
> > Thanks for the feedback.
> >
> > Kafka-3600 is not intended to address bac
ersion
> necessary? These aren't used in the kafka-python implementation, so
> from my perspective the answer is no. But maybe the java community has
> some interesting ideas for improvement where these are key
> ingredients. In any case, I think it would probably help substantially
>
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418943#comment-15418943
]
Ashish K Singh commented on KAFKA-2629:
---
[~harsha_ch] any thoughts?
>
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418941#comment-15418941
]
Ashish K Singh commented on KAFKA-2629:
---
[~bharatviswa] the way we do it is
why I responded as I did...
>
> Verification is good, but it looked like there was much complexity
> added toward very little benefits.
>
> On Thu, Aug 11, 2016 at 3:37 PM, Ashish Singh wrote:
> > Hey Gwen,
> >
> > I think this was more than a verification
applications of incompatible broker versions, I think that is some value
add. In future, the api versions info can be used to take smarter decisions.
On Wed, Aug 10, 2016 at 11:04 PM, Gwen Shapira wrote:
> I hate doing this, because Ashish has really been good about following
> up on the P
Provided wrong link to PR, here is the PR
<https://github.com/apache/kafka/pull/1251> for KAFKA-3600.
On Tue, Aug 9, 2016 at 9:45 AM, Ashish Singh wrote:
> Hey Guys,
>
> KAFKA-3600 <https://issues.apache.org/jira/browse/KAFKA-3600> was part of
> KIP-35's
nder review. Here is the PR
<https://github.com/apache/kafka/pull/986>
I have addressed all review comments and have been waiting for further
reviews/ this to go in for quite some time. I will really appreciate if a
committer can help with making progress on this.
--
Regards,
Ashish
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413738#comment-15413738
]
Ashish K Singh commented on KAFKA-2629:
---
[~bharatviswa] I would like this to g
[
https://issues.apache.org/jira/browse/KAFKA-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412553#comment-15412553
]
Ashish K Singh commented on KAFKA-2630:
---
[~vahid] apologies for the del
[
https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373182#comment-15373182
]
Ashish K Singh commented on KAFKA-3252:
---
[~junrao] [~omkreddy] what should be
[
https://issues.apache.org/jira/browse/KAFKA-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353497#comment-15353497
]
Ashish K Singh commented on KAFKA-3822:
---
[~hachikuji] while working out a PO
[
https://issues.apache.org/jira/browse/KAFKA-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351574#comment-15351574
]
Ashish K Singh commented on KAFKA-3822:
---
[~hachikuji] yeah makes sense. Will ha
e a `server` package
> in a `clients` jar, but that is just making explicit what is happening
> either way (we are adding a server-only interface to the `clients` jar).
>
> Thoughts?
>
> Ismael
>
> On Fri, Apr 22, 2016 at 10:56 PM, Ashish Singh
> wrote:
>
> > He
Ashish K Singh created KAFKA-3896:
-
Summary: Unstable test
KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
Key: KAFKA-3896
URL: https://issues.apache.org/jira/browse/KAFKA-3896
[
https://issues.apache.org/jira/browse/KAFKA-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh reassigned KAFKA-3822:
-
Assignee: Ashish K Singh
> Kafka Consumer close() hangs indefinitely if Kafka Bro
[
https://issues.apache.org/jira/browse/KAFKA-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347092#comment-15347092
]
Ashish K Singh commented on KAFKA-3822:
---
Turns out KAFKA-3879 is a dup of this,
[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347069#comment-15347069
]
Ashish K Singh commented on KAFKA-3879:
---
Sure [~hachikuji], linking the J
[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh resolved KAFKA-3879.
---
Resolution: Duplicate
> KafkaConsumer with auto commit enabled gets stuck when killed af
[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345609#comment-15345609
]
Ashish K Singh commented on KAFKA-3879:
---
[~hachikuji] yeah KAFKA-3822 is poin
[
https://issues.apache.org/jira/browse/KAFKA-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3849:
--
Summary: Avoid polling every second in MirrorMaker if no data is available.
(was: Make
[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340283#comment-15340283
]
Ashish K Singh commented on KAFKA-3879:
---
[~hachikuji] did you guys ever hit thi
Ashish K Singh created KAFKA-3879:
-
Summary: KafkaConsumer with auto commit enabled gets stuck when
killed after broker is dead
Key: KAFKA-3879
URL: https://issues.apache.org/jira/browse/KAFKA-3879
[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3879:
--
Affects Version/s: 0.10.0.0
> KafkaConsumer with auto commit enabled gets stuck when kil
[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3879:
--
Fix Version/s: 0.10.0.1
> KafkaConsumer with auto commit enabled gets stuck when killed af
[
https://issues.apache.org/jira/browse/KAFKA-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3849:
--
Status: Patch Available (was: Open)
> Make consumer poll time in MirrorMaker configura
Ashish K Singh created KAFKA-3849:
-
Summary: Make consumer poll time in MirrorMaker configurable.
Key: KAFKA-3849
URL: https://issues.apache.org/jira/browse/KAFKA-3849
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3400:
--
Resolution: Cannot Reproduce
Status: Resolved (was: Patch Available)
Resolving this as
> >> > > > >
> >> > > > > Kafka's KEYS file containing PGP keys we use to sign the
> release:
> >> > > > > http://kafka.apache.org/KEYS
> >> > > > >
> >> > > > > * Release artifacts to be voted upon (source and binary):
> >> > > > > http://home.apache.org/~gwenshap/0.10.0.0-rc6/
> >> > > > >
> >> > > > > * Maven artifacts to be voted upon:
> >> > > > > https://repository.apache.org/content/groups/staging/
> >> > > > >
> >> > > > > * java-doc
> >> > > > > http://home.apache.org/~gwenshap/0.10.0.0-rc6/javadoc/
> >> > > > >
> >> > > > > * tag to be voted upon (off 0.10.0 branch) is the 0.10.0.0 tag:
> >> > > > >
> >> > > > >
> >> > >
> >> >
> >>
>
> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=065899a3bc330618e420673acf9504d123b800f3
>
> >> > > > >
> >> > > > > * Documentation:
> >> > > > > http://kafka.apache.org/0100/documentation.html
> >> > > > >
> >> > > > > * Protocol:
> >> > > > > http://kafka.apache.org/0100/protocol.html
> >> > > > >
> >> > > > > /**
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > Gwen
> >> > > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > -- Guozhang
> >> >
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Ewen
> >>
>
>
>
>
>
>
--
Ashish 🎤h
[
https://issues.apache.org/jira/browse/KAFKA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3699:
--
Status: Patch Available (was: Open)
> Update protocol page on website to explain how KIP
[
https://issues.apache.org/jira/browse/KAFKA-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh resolved KAFKA-3724.
---
Resolution: Duplicate
Assignee: Ashish K Singh
Closing as duplicate of KAFKA-3308 and
[
https://issues.apache.org/jira/browse/KAFKA-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3308:
--
Description:
inter.broker.protocol.version configuration was nice for few releases, but it
is
[
https://issues.apache.org/jira/browse/KAFKA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285135#comment-15285135
]
Ashish K Singh commented on KAFKA-3699:
---
I will have a patch ready hopefully by
[
https://issues.apache.org/jira/browse/KAFKA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh reassigned KAFKA-3699:
-
Assignee: Ashish K Singh
> Update protocol page on website to explain how KIP-35 sho
[
https://issues.apache.org/jira/browse/KAFKA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279429#comment-15279429
]
Ashish K Singh commented on KAFKA-3699:
---
[~ijuma] I will take a crack at it. I
KIP-50 has passed with +6 (binding) and +3 (non-binding).
Thanks everyone for reviews and votes!
On Sun, May 1, 2016 at 4:08 PM, Don Bosco Durai wrote:
> +1 (non binding)
>
>
>
>
> On 4/28/16, 7:47 AM, "Jun Rao" wrote:
>
> >Ashish,
> >
> >Tha
ttps://issues.apache.org/jira/browse/KAFKA-1981
>
> Could someone please add it to the KIP page or grant me the mojo to do it
> myself?
>
> Thanks,
>
> Eric
>
--
Regards,
Ashish
[
https://issues.apache.org/jira/browse/KAFKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh resolved KAFKA-3469.
---
Resolution: Information Provided
Had an offline discussion with [~fpj] and it seems we can
the board from mailing lists, JIRA, code
> reviews
> > and helping us move to GitHub pull requests to contributing features, bug
> > fixes and code and documentation improvements.
> >
> > Thank you for your contribution and welcome to Apache Kafka, Ismael!
> >
> > --
> > Thanks,
> > Neha
> >
>
>
>
> --
> -- Guozhang
>
--
Ashish 🎤h
[
https://issues.apache.org/jira/browse/KAFKA-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3621:
--
Priority: Critical (was: Major)
> Add tests for ApiVersionRequest/Respo
[
https://issues.apache.org/jira/browse/KAFKA-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3621:
--
Fix Version/s: 0.10.0.0
> Add tests for ApiVersionRequest/Respo
[
https://issues.apache.org/jira/browse/KAFKA-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3621:
--
Affects Version/s: 0.10.0.0
> Add tests for ApiVersionRequest/Respo
Ashish K Singh created KAFKA-3621:
-
Summary: Add tests for ApiVersionRequest/Response
Key: KAFKA-3621
URL: https://issues.apache.org/jira/browse/KAFKA-3621
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3620:
--
Description:
This came up on PR of KAFKA-3307. Below is excerpt.
{quote}
With the versioning
Ashish K Singh created KAFKA-3620:
-
Summary: Clean up Protocol class.
Key: KAFKA-3620
URL: https://issues.apache.org/jira/browse/KAFKA-3620
Project: Kafka
Issue Type: Improvement
est knowledge of the client at the time of development (or
> > > > alternatively by configuration)."
> > > >
> > > > I still think that the mention of both 0.9.0 and 0.9.1 is confusing
> and
> > > > it's not clear if we need it for
om/apache/kafka/pull/861>.
The vote will run for 72 hours and I would like to start it with my +1
(non-binding).
​
--
Regards,
Ashish
[
https://issues.apache.org/jira/browse/KAFKA-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-3606:
--
Fix Version/s: (was: 0.10.1.0)
0.10.0.0
> Traverse CLASSPATH dur
>> current approach I think the authorizer stuff would be most consistent
> as a
> >> public package in common. It is true that this means you build against
> more
> >> stuff then needed but I'm not sure this has any negative implications in
> >> practice.
> >
Hello Jun,
On Fri, Apr 22, 2016 at 11:31 AM, Jun Rao wrote:
> Ashish,
>
> Just a couple of clarifications.
>
> 1. In ApiVersionRequest, we should get rid of ApiKeys since the request has
> an empty body, right?
>
Yes.
>
> 2. In ApiVersionResponse, we should list E
te will run for 72 hours and I would like to start it with my +1
(non-binding).
​
--
Regards,
Ashish
1 - 100 of 1013 matches
Mail list logo
