Re: [ANNOUNCE] New committer: Satish Duggana
Congratulations Sato :-) Regards, Dhiraj On Thu, Dec 29, 2022 at 10:17 AM Bill Bejeck wrote: > Congratulations Satish! > > -Bill > > On Thu, Dec 29, 2022 at 11:05 AM Satish Duggana > wrote: > > > Thank you, everyone! > > > > On Wed, 28 Dec 2022 at 00:02, Matthias J. Sax wrote: > > > > > > Congrats! > > > > > > On 12/27/22 10:20 AM, Kirk True wrote: > > > > Congrats, Satish! > > > > > > > > On Fri, Dec 23, 2022, at 10:07 AM, Jun Rao wrote: > > > >> Hi, Everyone, > > > >> > > > >> The PMC of Apache Kafka is pleased to announce a new Kafka committer > > Satish > > > >> Duggana. > > > >> > > > >> Satish has been a long time Kafka contributor since 2017. He is the > > main > > > >> driver behind KIP-405 that integrates Kafka with remote storage, a > > > >> significant and much anticipated feature in Kafka. > > > >> > > > >> Congratulations, Satish! > > > >> > > > >> Thanks, > > > >> > > > >> Jun (on behalf of the Apache Kafka PMC) > > > >> > > > > > > >
Re: [ANNOUNCE] New committer: Satish Duggana
Congratulations Sato :-) Regards, Dhiraj On Thu, Dec 29, 2022 at 10:17 AM Bill Bejeck wrote: > Congratulations Satish! > > -Bill > > On Thu, Dec 29, 2022 at 11:05 AM Satish Duggana > wrote: > > > Thank you, everyone! > > > > On Wed, 28 Dec 2022 at 00:02, Matthias J. Sax wrote: > > > > > > Congrats! > > > > > > On 12/27/22 10:20 AM, Kirk True wrote: > > > > Congrats, Satish! > > > > > > > > On Fri, Dec 23, 2022, at 10:07 AM, Jun Rao wrote: > > > >> Hi, Everyone, > > > >> > > > >> The PMC of Apache Kafka is pleased to announce a new Kafka committer > > Satish > > > >> Duggana. > > > >> > > > >> Satish has been a long time Kafka contributor since 2017. He is the > > main > > > >> driver behind KIP-405 that integrates Kafka with remote storage, a > > > >> significant and much anticipated feature in Kafka. > > > >> > > > >> Congratulations, Satish! > > > >> > > > >> Thanks, > > > >> > > > >> Jun (on behalf of the Apache Kafka PMC) > > > >> > > > > > > >
[jira] [Assigned] (KAFKA-9049) TopicCommandWithAdminClientTest should use mocks
[
https://issues.apache.org/jira/browse/KAFKA-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhiraj Dwarapudi reassigned KAFKA-9049:
---
Assignee: Dhiraj Dwarapudi
> TopicCommandWithAdminClientTest should use mocks
>
>
> Key: KAFKA-9049
> URL: https://issues.apache.org/jira/browse/KAFKA-9049
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
>Affects Versions: 2.5.0
>Reporter: Viktor Somogyi-Vass
> Assignee: Dhiraj Dwarapudi
>Priority: Minor
> Labels: easy, newbie, newbie++
>
> The {{TopicCommandWithAdminClientTest}} class currently sets up a few brokers
> for every test case which is wasteful and slow. We should improve it by
> mocking out the broker behavior (maybe use {{MockAdminClient}}?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [issue assign]
Hi Matthias, I would also like to contribute to the project. Could you please add me to the contributors list too:- my jira user name : ddhirajkumar Thanks, Dhiraj On Fri, Nov 29, 2019 at 6:37 PM Matthias J. Sax wrote: > Added you to the list on contributors in Jira. You can now self-assign > tickets. > > -Matthias > > On 11/28/19 8:27 PM, deng ziming wrote: > > my jira username is : > > dengziming > > > > thank you > > > > On Fri, Nov 29, 2019 at 11:31 AM Gurudatt Kulkarni > > wrote: > > > >> Share your jira username here. > >> > >> On Friday, November 29, 2019, deng ziming > >> wrote: > >>> hello, I read the Contributing Code Changes page which says I can > assign > >> a ticket to myself but it turns out that I can't assign? how could I > assign > >> it to myself? thank you! > >>> > >>> > >>> > >> > > > >
[jira] [Commented] (KAFKA-9049) TopicCommandWithAdminClientTest should use mocks
[
https://issues.apache.org/jira/browse/KAFKA-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985450#comment-16985450
]
Dhiraj Dwarapudi commented on KAFKA-9049:
-
Thanks [~viktorsomogyi]
But looks like I do not have permissions to self-assign tickets. Let me post on
the dev mailing list
> TopicCommandWithAdminClientTest should use mocks
>
>
> Key: KAFKA-9049
> URL: https://issues.apache.org/jira/browse/KAFKA-9049
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
>Affects Versions: 2.5.0
>Reporter: Viktor Somogyi-Vass
>Priority: Minor
> Labels: easy, newbie, newbie++
>
> The {{TopicCommandWithAdminClientTest}} class currently sets up a few brokers
> for every test case which is wasteful and slow. We should improve it by
> mocking out the broker behavior (maybe use {{MockAdminClient}}?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-9049) TopicCommandWithAdminClientTest should use mocks
[
https://issues.apache.org/jira/browse/KAFKA-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983066#comment-16983066
]
Dhiraj Dwarapudi commented on KAFKA-9049:
-
I am a new contributor and I would like to start with this ticket. Can I go
ahead and assign this to myself?
> TopicCommandWithAdminClientTest should use mocks
>
>
> Key: KAFKA-9049
> URL: https://issues.apache.org/jira/browse/KAFKA-9049
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
>Affects Versions: 2.5.0
>Reporter: Viktor Somogyi-Vass
>Priority: Minor
> Labels: easy, newbie, newbie++
>
> The {{TopicCommandWithAdminClientTest}} class currently sets up a few brokers
> for every test case which is wasteful and slow. We should improve it by
> mocking out the broker behavior (maybe use {{MockAdminClient}}?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[mojo-dev] [jira] (MCASSANDRA-38) Upgrade to support 2.1.3 version of Cassandra
Title: Message Title Dhiraj Dwarapudi created an issue Mojo's Cassandra Maven Plugin / MCASSANDRA-38 Upgrade to support 2.1.3 version of Cassandra Issue Type: Improvement Assignee: Stephen Connolly Created: 03/Apr/15 3:26 PM Priority: Major Reporter: Dhiraj Dwarapudi The current version 2.0.0-1 of the plugin only supports 2.0.x version of Cassandra. In my project I am using 2.1.3 of cassandra and cassandra-maven-plugin does not work with 2.1.3 version of cassandra-all artifact. I see the following error with that:- [ERROR] Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:2.0.0-1:start (start-cassandra) on project spotlight-domain: Execution start-cassandra of goal org.codehaus.mojo:cassandra-maven-plugin:2.0.0-1:start failed: A required class was missing while executing org.codehaus.mojo:cassandra-maven-plugin:2.0.0-1:start: org/apache/cassandra/tools/NodeCmd Apparently the name of the nodetool class has changed to 'org.apache.cassandra.tools.NodeTool' in 2.1 version of cassandra. Can we have an upgraded version of maven-plugin-version which has this support? I can provide the patch for this support.
[mojo-dev] [jira] (MCASSANDRA-35) upgrade cassandra version to 2.1.1
Title: Message Title Dhiraj Dwarapudi commented on an issue Re: upgrade cassandra version to 2.1.1 Any idea when this would be released? Add Comment Mojo's Cassandra Maven Plugin / MCASSANDRA-35 upgrade cassandra version to 2.1.1 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
