Re: KRaft Observer Nodes

hat we want a broker to be an observer? > > On Sun, Mar 24, 2024 at 3:01 PM Paolo Patierno > wrote: > > > Hi Sanaa, > > in KRaft mode there is the role of "observer" which is typically taken by > > brokers as part of the data plane. The broker/observer

Re: KRaft Observer Nodes

Hi Sanaa, in KRaft mode there is the role of "observer" which is typically taken by brokers as part of the data plane. The broker/observer can discover which node is the leader/active controller and fetches the metadata from it (as the "followers" in the KRaft quorum), but cannot vote and cannot

Re: [VOTE] 3.7.0 RC4

+1 (non-binding). I used the staged binaries with Scala 2.13 and mostly focused on the ZooKeeper to KRaft migration with multiple tests. Everything works fine. Thanks Paolo On Mon, 12 Feb 2024, 22:06 Jakub Scholz, wrote: > +1 (non-binding). I used the staged binaries with Scala 2.13 and the

Re: [VOTE] 3.7.0 RC2

gt; > > > > > >>> > > > > > > >>> > > > > > Cheers, > >>> > > > > > > >>> > > > > > Chris > >>> > > > > > > >>> > > > > > On Thu, Jan 11, 20

[jira] [Created] (KAFKA-16101) Kafka cluster unavailable during KRaft migration rollback procedure

Paolo Patierno created KAFKA-16101: -- Summary: Kafka cluster unavailable during KRaft migration rollback procedure Key: KAFKA-16101 URL: https://issues.apache.org/jira/browse/KAFKA-16101 Project

[jira] [Created] (KAFKA-16005) ZooKeeper to KRaft migration rollback missing disabling controller and migration configuration on brokers

Paolo Patierno created KAFKA-16005: -- Summary: ZooKeeper to KRaft migration rollback missing disabling controller and migration configuration on brokers Key: KAFKA-16005 URL: https://issues.apache.org/jira/browse

[jira] [Created] (KAFKA-16003) The znode /config/topics is not updated during KRaft migration in "dual-write" mode

Paolo Patierno created KAFKA-16003: -- Summary: The znode /config/topics is not updated during KRaft migration in "dual-write" mode Key: KAFKA-16003 URL: https://issues.apache.org/jira/browse/K

[jira] [Resolved] (KAFKA-15754) The kafka-storage tool can generate UUID starting with "-"

[ https://issues.apache.org/jira/browse/KAFKA-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno resolved KAFKA-15754. Resolution: Not A Problem > The kafka-storage tool can generate UUID start

[jira] [Reopened] (KAFKA-15754) The kafka-storage tool can generate UUID starting with "-"

[ https://issues.apache.org/jira/browse/KAFKA-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno reopened KAFKA-15754: > The kafka-storage tool can generate UUID start

[jira] [Created] (KAFKA-15754) The kafka-storage tool can generate UUID starting with "-"

Paolo Patierno created KAFKA-15754: -- Summary: The kafka-storage tool can generate UUID starting with "-" Key: KAFKA-15754 URL: https://issues.apache.org/jira/browse/KAFKA-15754 Proj

[jira] [Created] (KAFKA-15689) KRaftMigrationDriver not logging the skipped event when expected state is wrong

Paolo Patierno created KAFKA-15689: -- Summary: KRaftMigrationDriver not logging the skipped event when expected state is wrong Key: KAFKA-15689 URL: https://issues.apache.org/jira/browse/KAFKA-15689

[jira] [Created] (KAFKA-14883) Broker state should be "observer" in KRaft quorum

Paolo Patierno created KAFKA-14883: -- Summary: Broker state should be "observer" in KRaft quorum Key: KAFKA-14883 URL: https://issues.apache.org/jira/browse/KAFKA-14883 Project: Kafka

[jira] [Created] (KAFKA-14411) Logging warning when partitions don't exist on assign request

Paolo Patierno created KAFKA-14411: -- Summary: Logging warning when partitions don't exist on assign request Key: KAFKA-14411 URL: https://issues.apache.org/jira/browse/KAFKA-14411 Project: Kafka

Re: [ANNOUNCE] New committer: Tom Bentley

Congratulations Tom! Get Outlook for Android From: Guozhang Wang Sent: Monday, March 15, 2021 8:02:44 PM To: dev Subject: Re: [ANNOUNCE] New committer: Tom Bentley Congratulations Tom! Guozhang On Mon, Mar 15, 2021 at 11:25 AM Bill

Re: [ANNOUNCE] New Kafka PMC member: Dong Lin

Congratulations Dong! Paolo Patierno Principal Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : De

KIP-176 and related PR : today deadline for merging in 2.0.0

/confluence/display/KAFKA/KIP-176%3A+Remove+deprecated+new-consumer+option+for+tools Thanks Paolo Patierno Principal Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it

Re: [VOTE] KIP-176: Remove deprecated new-consumer option for tools

Thanks for voting! As far as I understood, today is the last day for having a PR for this one. The KIP-176 has 3 (bindings) + 2 (non binding) votes so it is accepted. I'll provide a related PR by the EOD. Thanks, Paolo Patierno Principal Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure

[VOTE] KIP-176: Remove deprecated new-consumer option for tools

vote for that adding to the release plan, please ? Thanks, Paolo Patierno Principal Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolop

Re: [ANNOUNCE] New Committer: Dong Lin

Congrats Dong !! From: Becket Qin Sent: Wednesday, March 28, 2018 7:58:07 PM To: dev; us...@kafka.apache.org Subject: [ANNOUNCE] New Committer: Dong Lin Hello everyone, The PMC of Apache Kafka is pleased to announce that Dong Lin has

Re: 1.1 release progress

Hi Guozhang and Damian, I have a couple of issues marked for 1.1.0 but the PR isn't reviewed since a long time and both of them should be ready. They are : KAFKA-5919 KAFKA-5532 Maybe you can

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

Hi Matthias, just a question : what will be the timestamp "type" in the new message on the wire ? Thanks, Paolo. From: Matthias J. Sax Sent: Wednesday, January 31, 2018 2:06 AM To: dev@kafka.apache.org Subject: [DISCUSS] KIP-251: Allow

Re: [ANNOUNCE] New Kafka PMC Member: Rajini Sivaram

Congratulations Rajini ! From: Sriram Subramanian Sent: Wednesday, January 17, 2018 8:01 PM To: dev@kafka.apache.org Subject: Re: [ANNOUNCE] New Kafka PMC Member: Rajini Sivaram Congratulations Rajini! On Wed, Jan 17, 2018 at 11:40 AM,

Re: [ANNOUNCE] New committer: Matthias J. Sax

Congratulations Matthias ! Very well deserved ! From: Guozhang Wang Sent: Friday, January 12, 2018 11:59:21 PM To: dev@kafka.apache.org; us...@kafka.apache.org Subject: [ANNOUNCE] New committer: Matthias J. Sax Hello everyone, The PMC of

Re: Stream Processing Meetup@LinkedIn (Dec 4th)

Hi Becket, I watched some of these meetups on the related YouTube channel in the past. Will be it available in streaming or just recorded for watching it later ? Thanks Paolo From: Becket Qin Sent: Friday, November 17, 2017 8:33:04 PM To:

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Ismael +1 ... I'm going to update the name Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : De

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Guozhang thanks :-) It's getting late in my timezone, so maybe it's better for me don't take a look at email anymore ;) So finally, the KIP-204 was accepted. Waiting for more comments (if needed) on the PR for getting it merged. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Monday, November 13, 2017 9:21:07 PM To: Paolo Patierno Cc: dev@kafka.apache.org Subject: Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API I'm not sure if Ismael's reply on the mailing list is a casted vote for this KIP. @Ismael, could you review the KIP again and cas

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Hi all, I'm going to close this vote because this KIP was accepted with : 3 binding votes 5 non-binding votes Thanks everyone for comments and for voting. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno&

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

afka/pull/4132> as well. Thanks for your comments ! Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.c

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

s opinions otherwise I'll start to implement in such way. I have updated the KIP and the PR using "recordsToDelete" parameter as well. Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<h

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

d then have a field logStartOffset or lowWatermark instead of having to document it via a comment only. Ismael On Tue, Oct 3, 2017 at 6:51 AM, Paolo Patierno <ppatie...@live.com> wrote: > Hi all, > > I didn't see any further discussion around this KIP, so I'd like to start

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

the KIP got accepted and we can start to think about merging the PR for a future 1.1.0 release. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopat

Re: [ANNOUNCE] New committer: Onur Karaman

Congrats Onur ! Well deserved ! Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : De

Re: [ANNOUNCE] Apache Kafka 1.0.0 Released

Congratulations for this milestone ! Thanks to Gouzhang for running the release ! Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi Colin, I have just updated the KIP mentioning that this new method should replace the "legacy" Scala API used for deleting records today. Thanks, Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitte

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Thanks Jason ! I have just updated the KIP with DeleteRecordsOptions definition. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it

Re: Metadata class doesn't "expose" topics with errors

:22 PM To: dev@kafka.apache.org Subject: Re: Metadata class doesn't "expose" topics with errors Hello Paolo, I'm looking at your PR for KIP-204 now. Will reply on the discussion thread / PR diff file directly if I find anything. Guozhang On Tue, Oct 24, 2017 at 5:45 AM, Paolo Patierno <

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

in On Wed, Oct 25, 2017, at 03:47, Paolo Patierno wrote: > Thanks for all your feedback guys. I have updated my current code as > well. > > I know that the vote for this KIP is not started yet (actually I opened > it due to no feedback on this KIP after a while but then the discuss

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

18 ? There are only "non binding" votes up to now. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

for that. Maybe feedback could be useful on that as well : https://github.com/apache/kafka/pull/4132 Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopat

Re: Metadata class doesn't "expose" topics with errors

client). For now the current implementation I have (I'll push a PR soon), use the Call class for sending a MetadataRequest and then its handleResponse for using another Call instance for sending the DeleteRecordsRequest. Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP

Re: Metadata class doesn't "expose" topics with errors

Finally another plan could be to use nesting of runnable calls. The first one for asking metadata (using the MetadataRequest which provides us all the errors) and then sending the delete records requests in the handleResponse() of such metadata request. Paolo Patierno Senior Software Engineer

Re: Metadata class doesn't "expose" topics with errors

requests but different of them (even if for the same leader). Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolop

Metadata class doesn't "expose" topics with errors

Is there any specific reason why "topics with errors" are not exposed in the Metadata instance ? Is the preferred pattern using the low level protocol stuff in such case ? Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Mic

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

to the delete records operation and what it means, so the target for such operation. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

it's really clear and give us more possibility to evolve this DeletionTarget class if we'll add different ways to specify such target not only offset based. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppati

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi all, I have just updated the KIP with your suggestion. I'm going to continue implementation and tests with these changes, waiting for further discussion. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twi

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

itions") having a deleteBefore(Long) factory method for a simple creation when you need to delete before the specified offset. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twit

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Hi all, since I started voting KIP-204 on October 3rd I haven't seen any votes on that. I know you are busy on 1.0.0 release, just as reminder Thanks. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno&

Re: [VOTE] KIP-176 : Remove deprecated new-consumer option for tools

Just as reminder for other committers in order to have other binding votes, for now we have ... binding +1 Ismael Juma +1 Guozhang Wang non binding +1 Mickael Maison +1 Vahid Hashemian Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft A

[VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

Hi all, I didn't see any further discussion around this KIP, so I'd like to start the vote for it. Just for reference : https://cwiki.apache.org/confluence/display/KAFKA/KIP-204+%3A+adding+records+deletion+operation+to+the+new+Admin+Client+API Thanks, Paolo Patierno Senior Software Engineer

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi, maybe we want to start without the delete records policy for now waiting for a real needs. So I'm removing it from the KIP. I hope for more comments on this KIP-204 so that we can start a vote on Monday. Thanks. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi, I have just updated the KIP-204 description with the new TopicDeletionPolicy suggested by the KIP-201. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : pao

Re: [DISCUSS] KIP-201: Rationalising Policy interfaces

be better (even already happens for topic deletion). 2. I know about the problem of restarting broker due to changes on policies but what do you mean by doing that on the clients ? Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Ad

Re: [DISCUSS] KIP-201: Rationalising Policy interfaces

Hi Tom, I guess that at "On topic deletion will be applied on topic and message deletion." you meant something like "The TopicDeletionPolicy will be applied on topic and messages deletion". Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on A

Re: [DISCUSS] KIP-201: Rationalising Policy interfaces

for allowing or not deletion on time base. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : De

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi Tom, as I said in the KIP-201 discussion I'm ok with having a unique DeleteTopicPolicy but then it could be useful having more information then just the topic name; partitions and offset for messages deletion could be useful for a fine grained use cases. Paolo Patierno Senior Software

Re: [DISCUSS] KIP-201: Rationalising Policy interfaces

the delete records takes info like partition and specific offset. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolop

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

them but not the other. In such a policy a user could also check the timestamp related to the offset for allowing or not deletion on time base. Wdyt ? Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno&

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi Edoardo, I was referring to the KIP-107 where the delete records operation is coming with the authorizer I mentioned. You are referring to KIP-170 ... same digits, inverse order ! Sorry for that ;) Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure &

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

uggest a policy as you are saying but using the authorizer mechanism with operation = DELETE and resource = TOPIC. Is my understanding right ? Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

? Starting from a specific offset ? Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : DevExp

The way for the tools and the Admin Client API usage

a using Admin Client API but maybe during this path having a smooth migration just using new Admin Client API in the current Scala tools first (removing Zookeeper calls) could be better. Maybe for committers, in order to review and merge PRs, little ones are better ... What do you think about this ?

Re: [VOTE] KIP-176 : Remove deprecated new-consumer option for tools

? Thanks. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : DevExperience<http://paolopat

[jira] [Reopened] (KAFKA-5588) ConsoleConsumer : uselss --new-consumer option

[ https://issues.apache.org/jira/browse/KAFKA-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno reopened KAFKA-5588: --- > ConsoleConsumer : uselss --new-consumer opt

[DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

ing+records+deletion+operation+to+the+new+Admin+Client+API Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Azure & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopa

[jira] [Created] (KAFKA-5925) Adding records deletion operation to the new Admin Client API

Paolo Patierno created KAFKA-5925: - Summary: Adding records deletion operation to the new Admin Client API Key: KAFKA-5925 URL: https://issues.apache.org/jira/browse/KAFKA-5925 Project: Kafka

[jira] [Created] (KAFKA-5919) Delete records command "version" parameter ignored

Paolo Patierno created KAFKA-5919: - Summary: Delete records command "version" parameter ignored Key: KAFKA-5919 URL: https://issues.apache.org/jira/browse/KAFKA-5919 Project: Kafka

Admin Client : no way to create topic with default partitions and replication factor

lues in this case. What do you think about that ? Thanks. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : DevExperience<http://paolopatierno.wordpress.com/>

Re: [DISCUSS] KIP-195: AdminClient.increasePartitions

My 2 cents about naming ... PartitionCount or NumPartitions sound better to me providing an "absolute" value (as today the kafka-topics script work) for an idempotent operation while the NumPartitionsIncrease name sounds to me like the "increment" value. Paolo Pati

Re: KAFKA-5723: Refactor BrokerApiVersionsCommand to use the new AdminClient

As related to different tools making their PRs Does this plan make sense ? Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linked

Re: KAFKA-5723: Refactor BrokerApiVersionsCommand to use the new AdminClient

Hi Ismael, first of all thanks for your reply. So as far as I understood having a branch in the Kafka repo could be better for you as committer to validate small PRs from us and not a big one at the end, right ? Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows

Re: KAFKA-5723: Refactor BrokerApiVersionsCommand to use the new AdminClient

not good for us because we can't go forward with development. Let's see what they say, maybe something like that already happened in the past ... Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno&

Re: KAFKA-5723: Refactor BrokerApiVersionsCommand to use the new AdminClient

Hi committers, as already asked by Viktor on the JIRA yesterday can you give us a feedback/advice on how to move on that ? Thanks ! Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twit

Re: [VOTE] KIP-176 : Remove deprecated new-consumer option for tools

KIP updated to clarify it will be removed in the 2.0.0 version. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it

Fw: [VOTE] KIP-176 : Remove deprecated new-consumer option for tools

Hi devs, I haven't seen any votes for this since last month. Is there something that should be addressed in the KIP (it didn't have any comments anymore and for this reason I started the vote). Thanks. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows

Re: KAFKA-5723: Refactor BrokerApiVersionsCommand to use the new AdminClient

Any feedback is really appreciated :-) Thanks, Paolo Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatie

Re: Command tools : from Scala to Java, from Zookeeper utils to Admin Client API

. Does the Java re-implementation of the TopicCommand tool need a KIP ? Thanks, Paolo Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopat

[jira] [Created] (KAFKA-5739) Rewrite KStreamPeekTest at processor level avoiding driver usage

Paolo Patierno created KAFKA-5739: - Summary: Rewrite KStreamPeekTest at processor level avoiding driver usage Key: KAFKA-5739 URL: https://issues.apache.org/jira/browse/KAFKA-5739 Project: Kafka

[jira] [Resolved] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

[ https://issues.apache.org/jira/browse/KAFKA-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno resolved KAFKA-5684. --- Resolution: Feedback Received > KStreamPrintProcessor as customized KStreamPeekProces

Re: [VOTE] KIP-176 : Remove deprecated new-consumer option for tools

Hi Tom, good question. Due to the new version policies, the deprecation will be in the coming 1.0.0 release but then, due to a breaking change on the API, the removal should be on 2.0.0 I guess. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows

[VOTE] KIP-176 : Remove deprecated new-consumer option for tools

Hi devs, I didn't see any more comments about this KIP. The JIRAs related to the first step (so making --new-consumer as deprecated with warning messages) are merged. I'd like to start a vote for this KIP. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP

Jenkins problem with JDK 8 and Scala 2.12 ?

to fetch from git://github.com/apache/kafka.git I re-tried twice with same results. All is good with JDK 7 and Scala 2.11 Thanks, Paolo Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twit

Re: KStreamPrintTest : no differences in the unit tests

Hi Damian, I submit the patch as part of this PR https://github.com/apache/kafka/pull/3611 adding a couple of other tests as well. Maybe you can take a look at it :-) Thanks ! Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Micro

KStreamPrintTest : no differences in the unit tests

n all the code seems to be the same (some other "final" missing ...). Is there something that my eyes can't see ? Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppa

Re: Command tools : from Scala to Java, from Zookeeper utils to Admin Client API

ly developed in Java. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : De

Re: Command tools : from Scala to Java, from Zookeeper utils to Admin Client API

a specific version (tools migration will be done over more releases). Is that right ? Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin

Re: Command tools : from Scala to Java, from Zookeeper utils to Admin Client API

hing users to move from old to new tool ... that is good for us. What do you think ? Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin

Re: [DISCUSS] KIP-179: Change ReassignPartitionsCommand to use AdminClient

o the configs change with the alter topic as well. Last thing on the KIP ... the "timeout" field in the AlterTopicRequest is missing in the table with related description. Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & Io

Re: Command tools : from Scala to Java, from Zookeeper utils to Admin Client API

rong. I'd like to have some input from committers as well to be sure that the way is good about how handling such use cases. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twit

Re: Kafka Streams debugging with "no fluent" API choice

Hi Damian, changing the print() method for sure needs a KIP but I guess there is some reason we don't know why they decided to not have a fluent API for that. Regarding my JIRA I don't think a KIP is required, it's just internal stuff ... no ? Thanks Paolo Patierno Senior Software

[jira] [Created] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

Paolo Patierno created KAFKA-5684: - Summary: KStreamPrintProcessor as customized KStreamPeekProcessor Key: KAFKA-5684 URL: https://issues.apache.org/jira/browse/KAFKA-5684 Project: Kafka

Re: Kafka Streams debugging with "no fluent" API choice

with forwardDownStream = false and providing the usage of Serdes. For this I have opened the following JIRA : https://issues.apache.org/jira/browse/KAFKA-5684 What do you think ? Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Adv

Kafka Streams debugging with "no fluent" API choice

I was going to propose before coming across the PR :-)). Why this preference on the first one ? Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno>

Re: [DISCUSS] KIP-176: Remove deprecated new-consumer option from tools

://github.com/apache/kafka/pull/3537 https://github.com/apache/kafka/pull/3555 Thanks Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopat

Command tools : from Scala to Java, from Zookeeper utils to Admin Client API

e but it's something that could be factorized. Thanks, Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/pa

Consumer assign vs subscribe influence on __consumer_offset

the opposite direction). Conclusion ... it's possible that there is something that I didn't understand about this interaction between consumers in the same group but asking for partitions in two different way (assign vs subscribe). Thanks, Paolo Paolo Patierno Senior Software Engineer (IoT) @

About "exclude.internal.topics" ... some thoughts

; or something that explains the difference between subscribing using a topic filter (so the property takes an effect) or direct topic name (property does have no effect). What do you think ? Thanks, Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Win

[jira] [Created] (KAFKA-5643) Using _DUCKTAPE_OPTIONS has no effect on executing tests

Paolo Patierno created KAFKA-5643: - Summary: Using _DUCKTAPE_OPTIONS has no effect on executing tests Key: KAFKA-5643 URL: https://issues.apache.org/jira/browse/KAFKA-5643 Project: Kafka

Re: [DISCUSS] KIP-179: Change ReassignPartitionsCommand to use AdminClient

JIRA). I also agree that it would be good to consider > if alterTopics would be a sensible way to support all the use cases or if > it's better to have separate APIs. I think it makes sense to have a single > KIP though as they are related and it will be easier to evaluate as a > whol

  1   2   >