Is Connector#initialize(ConnectorContext, List<Map<String, String>>) a TODO method?

hi Kafka, I'm reading the connector flow. And I noticed the methods "initialize(ConnectorContext, List>)" and "reconfigure" are not used in production code. Hence, are they still in TODO state? Or they are designed to use rather than to override? Best Regards, Chia-Ping

[jira] [Resolved] (KAFKA-6870) Concurrency conflicts in SampledStat

[ https://issues.apache.org/jira/browse/KAFKA-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-6870. --- Resolution: Fixed Reviewer: Rajini Sivaram Thanks for the reviews. [~rsivaram

[jira] [Created] (KAFKA-6870) Concurrency conflicts in SampledStat

Chia-Ping Tsai created KAFKA-6870: - Summary: Concurrency conflicts in SampledStat Key: KAFKA-6870 URL: https://issues.apache.org/jira/browse/KAFKA-6870 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6931) Make worker id configurable

Chia-Ping Tsai created KAFKA-6931: - Summary: Make worker id configurable Key: KAFKA-6931 URL: https://issues.apache.org/jira/browse/KAFKA-6931 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

Chia-Ping Tsai created KAFKA-6941: - Summary: when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port Key: KAFKA-6941 URL: https://issues.apache.org/jira/browse/KAFKA-6941

[jira] [Created] (KAFKA-7032) The TimeUnit is neglected by KakfaConsumer#close(long, TimeUnit)

Chia-Ping Tsai created KAFKA-7032: - Summary: The TimeUnit is neglected by KakfaConsumer#close(long, TimeUnit) Key: KAFKA-7032 URL: https://issues.apache.org/jira/browse/KAFKA-7032 Project: Kafka

[jira] [Created] (KAFKA-7036) Complete the docs of KafkaConsumer#poll

Chia-Ping Tsai created KAFKA-7036: - Summary: Complete the docs of KafkaConsumer#poll Key: KAFKA-7036 URL: https://issues.apache.org/jira/browse/KAFKA-7036 Project: Kafka Issue Type

access to create KIP

dear Kafka, Please give me the permission to create KIP. the email is "chia7...@gmail.com" and the account is "chia7712" Best Regards, chia-ping

Re: access to create KIP

thanks for the helps! On 2018/06/12 17:36:05, "Matthias J. Sax" wrote: > Done. > > On 6/12/18 12:37 AM, Chia-Ping Tsai wrote: > > dear Kafka, > > > > Please give me the permission to create KIP. the email is > > "chia7...@gmail.com"

[jira] [Created] (KAFKA-7048) NPE when creating >1 connectors

Chia-Ping Tsai created KAFKA-7048: - Summary: NPE when creating >1 connectors Key: KAFKA-7048 URL: https://issues.apache.org/jira/browse/KAFKA-7048 Project: Kafka Issue Type: Improvem

[jira] [Created] (KAFKA-6992) Configuring the batch.size to zero won't disable the batching entirely

Chia-Ping Tsai created KAFKA-6992: - Summary: Configuring the batch.size to zero won't disable the batching entirely Key: KAFKA-6992 URL: https://issues.apache.org/jira/browse/KAFKA-6992 Project

[jira] [Created] (KAFKA-7014) Guarantee the byte buffer returned by Serializer is reusable

Chia-Ping Tsai created KAFKA-7014: - Summary: Guarantee the byte buffer returned by Serializer is reusable Key: KAFKA-7014 URL: https://issues.apache.org/jira/browse/KAFKA-7014 Project: Kafka

[jira] [Created] (KAFKA-7084) NewTopicBuilder#config should accept Map rather than Map

Chia-Ping Tsai created KAFKA-7084: - Summary: NewTopicBuilder#config should accept Map rather than Map Key: KAFKA-7084 URL: https://issues.apache.org/jira/browse/KAFKA-7084 Project: Kafka

Re: [DISCUSS] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

ohn Roesler wrote: > Hi Chia-Ping, > > I couldn't find KIP-331 in the list of KIPs ( > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals > ). > > Can you provide a link, please? > > Thanks, > -John > > On Sun, Jul 1, 2018 at 11

[DISCUSS] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

hi folks, KIP-331 is waiting for any suggestions, feedback and reviews. The main purpose of the KIP-331 is to add empty implementations to the close() and configure() so as to user can write less code to develop custom Serialzier, Deserializer and Serde. Cheers, Chia-Ping

[DISCUSS] add connect-related packages to "What is considered a "major change" that needs a KIP?"

hi Kafka There is a section[1] listing the packages which have public interfaces. However, it doesn't include any connect-related packages. It would be better to have a list used to highlight the public interfaces for connector. Otherwise, connector user may misuse the internal interface in

Re: [VOTE] KIP-338 Support to exclude the internal topics in kafka-topics.sh command

you all. -- Chia-Ping On 2018/07/25 18:38:26, Kamal Chandraprakash wrote: > Chia-Ping Tsai, > > The voting has passed. Dong Lin (binding) is a committer. > > On Wed, Jul 25, 2018 at 8:24 AM Chia-Ping Tsai wrote: > > > Current voting result is shown below. > &

Re: [DISCUSSION] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

Bumping up! On 2018/07/09 08:50:07, Viktor Somogyi wrote: > Hi folks, > > I've published KIP-336 which is about consolidating the > Serializer/Deserializer interfaces. > > Basically the story here is when ExtendedSerializer and > ExtendedDeserializer were added we still supported Java 7 and

[DISCUSS] KIP-348 Eliminate null from SourceTask#poll()

hi all, Please take a look at the KIP-348[1] if you have free cycel. It bring a little change to the usage of SourceTask#poll() [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89065853=true#KIP-348EliminatenullfromSourceTask#poll()-Status Cheers, Chia-Ping

Re: [DISCUSS] KIP-348 Eliminate null from SourceTask#poll()

t; since it will still be possible to return null here, > right? > > best, > Colin > > > On Tue, Jul 31, 2018, at 01:10, Chia-Ping Tsai wrote: > > hi all, > > > > Please take a look at the KIP-348[1] if you have free cycel. It bring a > > little change

[jira] [Created] (KAFKA-7253) The connector type responded by worker is always null when creating connector

Chia-Ping Tsai created KAFKA-7253: - Summary: The connector type responded by worker is always null when creating connector Key: KAFKA-7253 URL: https://issues.apache.org/jira/browse/KAFKA-7253

Re: [DISCUSS] add connect-related packages to "What is considered a "major change" that needs a KIP?"

t in there, it likely is not public API. > > In the case of Connect, the only public Java APIs are in their own module, > connect-api. Everything in the other connect modules are considered > internal implementation details. > > -Ewen > > > On Fri, Jul 27, 2018 at 7:15 PM C

[VOTE] KIP-348 Deprecate null from SourceTask#poll()

hi kafka, I'm starting a vote on KIP-348 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89065853 -- chia-ping

[DISCUSS]

hi all I would like to start a discussion of KIP-367 [1]. It is similar to KIP-358 and KIP-266 which is trying to substitute Duration for (long, TimeUnit). [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89070496 -- Chia-Ping

[DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

(re-start the thread for KIP-367 because I enter the incorrect topic in first post) hi all I would like to start a discussion of KIP-367 [1]. It is similar to KIP-358 and KIP-266 which is trying to substitute Duration for (long, TimeUnit). [1]

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

fix the topic of this discussion :( On 2018/08/28 08:59:36, Chia-Ping Tsai wrote: > hi all > > I would like to start a discussion of KIP-367 [1]. It is similar to KIP-358 > and KIP-266 which is trying to substitute Duration for (long, TimeUnit). > > [1] https://cwiki.apa

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

AdminClient? > > -Jason > > On Tue, Aug 28, 2018 at 2:32 AM, Chia-Ping Tsai wrote: > > > (re-start the thread for KIP-367 because I enter the incorrect topic in > > first post) > > > > hi all > > > > I would like to start a discussion of KIP-36

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

3 binding votes to pass. I still think we should include the > details of how things will look like with the headers being passed to > serializers/deserializers to ensure things actually make sense as a whole. > > Ismael > > > On Sun, 8 Jul 2018, 18:31 Chia-Ping Tsai, wrote:

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

work holistically. > > Ismael > > On Fri, Jul 20, 2018 at 3:50 AM Chia-Ping Tsai wrote: > > > > The KIP needs 3 binding votes to pass. > > > > Thanks for the reminder. I will reopen the ballot box until we get 3 > > tickets. > > > > > I still

Re: [DISCUSSION] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

> The approach where all the methods have a default implementation and the > user chooses to override one of them seems the most appealing to me given > the current state. sounds good. one Q: Which implementation is suitable for serialize()/deserialize()? maybe just throw exception? BTW,

Re: [VOTE] KIP-338 Support to exclude the internal topics in kafka-topics.sh command

Mon, Jul 16, 2018 at 2:23 PM, Dong Lin wrote: > > > +1 > > > > Thanks! > > Dong > > > > On Mon, Jul 16, 2018 at 9:17 AM, Vahid S Hashemian < > > vahidhashem...@us.ibm.com> wrote: > > > > > +1 (non-binding) > > > > > &g

[VOTE] KIP-338 Support to exclude the internal topics in kafka-topics.sh command

hi folks, The discussion[1] of KIP-338[2] did not get any objection for last 6 days so it is time to start the voting thread. Thanks for your time! [1] https://lists.apache.org/thread.html/9bd4e61b73c901b51132ada49743b9b703d40b85fc4eeaa5c9099900@%3Cdev.kafka.apache.org%3E [2]

Re: [DISCUSSION] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

here is my two cents. In order to keep the BC, SC, and correct deprecation cycle(deprecate Serializer/Deserializer in 2.0), the solution of this issue is to introduce a new class to replace the Serializer and Deserializer. The new class should be a subclass of Serializer/Deserializer and it

Re: [VOTE] KIP-338 Support to exclude the internal topics in kafka-topics.sh command

Current voting result is shown below. +2 (binding) 1) Jason Gustafson 2) Gwen Shapira +4 (non-binding) 1) Colin McCabe 2) Manikumar 3) Dong Lin 4) Vahid S Hashemian Need one more binding vote please Cheers, Chia-Ping On 2018/07/16 08:10:51, Chia-Ping Tsai wrote: > hi fo

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

ndicate if the get deprecated or added. Please > don't show a diff as in a patch :) > > Is there already a JIRA for this? If not, please create on and link it > in the KIP. > > Besides this, I think you can start a VOTE. > > > > -Matthias > > On 9/3/18 11:2

[VOTE] KIP-367 Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit)

Hi All, I'd like to put KIP-367 to the vote. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89070496 -- Chia-Ping

[jira] [Created] (KAFKA-7391) Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit)

Chia-Ping Tsai created KAFKA-7391: - Summary: Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit) Key: KAFKA-7391 URL: https://issues.apache.org/jira/browse/KAFKA-7391

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

; - `AdminClient#close(long duration, TimeUnit unit)` is `abstract` and > the KIP should contain this. > > > > -Matthias > > > > On 9/8/18 11:22 AM, Chia-Ping Tsai wrote: > >> It's a little hard to read -- it's easier if you just list the methods > >

[VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

hi all, I would like to start voting on "KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde"

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

All, The 72 hours has passed. The vote result of KIP-313 is shown below. 1 binding vote (Matthias J. Sax) 4 non-binding votes (John Roesler, Richard Yu, vito jeng and Chia-Ping) Cheers, Chia-Ping On 2018/07/05 14:45:01, Chia-Ping Tsai wrote: > hi all, > > I would like to sta

[DISCUSS] KIP-338 Support to exclude the internal topics in kafka-topics.sh command

hi Kafka, KIP-338 is trying to make us exclude internal topics easily when using the kafka-topics.sh. An new option will be added to kafka-topics.sh (TopicCommand) and user can use the option to exclude all internal topics when running the list or describe command.

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

ael > > On Thu, 5 Jul 2018, 07:45 Chia-Ping Tsai, wrote: > > > hi all, > > > > I would like to start voting on "KIP-331 Add default implementation to > > close() and configure() for Serializer, Deserializer and Serde" > > > > > > https

[jira] [Created] (KAFKA-7139) Support to exclude the internal topics in kafka-topics.sh command

Chia-Ping Tsai created KAFKA-7139: - Summary: Support to exclude the internal topics in kafka-topics.sh command Key: KAFKA-7139 URL: https://issues.apache.org/jira/browse/KAFKA-7139 Project: Kafka

Re: [DISCUSS] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

fka jar containing your change on my classpath at > run time, will it still work? > > I think it should be binary compatible, assuming Oracle didn't do anything > crazy, since all the method references would be the same. It might we worth > an experiment, though. > > Thanks, &g

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

We have following votes: non-binding 1. John Roesler 2. vito jeng 3. Richard Yu 4. Bill Bejeck 5. Satish Duggana binding 1. Matthias J. Sax 2. Ismael Juma 3. Damian Guy KIP-331 has passed. Thanks for all votes -- Chia-Ping On 2018/07/05 14:45:01, Chia-Ping Tsai wrote: > hi all, > >

Re: [DISCUSSION] KIP-376: Implement AutoClosable on appropriate classes that has close()

eption` and thus, it seems to be a backward incompatible change. > Hence, I am not sure if we can actually move forward easily with this KIP. > > Nit: `RecordCollectorImpl` is an internal class that implements > `RecordCollector` -- should `RecordCollector extends AutoCloseable`

Re: [DISCUSSION] KIP-376: Implement AutoClosable on appropriate classes that has close()

ered the cases > > where Autoclosable is so desired several times! Let me inspect more > > candidate classes as well. > > > > +1. I also refined your KIP a little bit. > > > > Best, > > Dongjin > > > > On Thu, Sep 27, 2018 at 12:21 PM Chia-Ping

[DISCUSS] Passing a copy of props to Connector#start rather than passing props itself

hi folks, The props passed to Connector#start is not a clone so any change to props will impact the props itself. If we try to pause and then resume a connector, the props passed to connector is what we changed before. However, the "changes" don't sync to config store. So if connector restart

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

(just bump) We have following votes: non-binding 1. John Roesler 2. vito jeng 3. Richard Yu 4. Bill Bejeck 5. Satish Duggana binding 1. Matthias J. Sax 2. Ismael Juma it needs one more ticket :) Cheers, Chia-Ping On 2018/07/05 14:45:01, Chia-Ping Tsai wrote: > hi all, > > I w

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

a similar change to > AdminClient? > > -Jason > > On Tue, Aug 28, 2018 at 2:32 AM, Chia-Ping Tsai wrote: > > > (re-start the thread for KIP-367 because I enter the incorrect topic in > > first post) > > > > hi all > > > > I would like to

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

I think that may not be desirable due to the method that > passes headers. So, it doesn't make sense to discuss two separate changes > to the same interfaces in isolation, we should figure out how we want them > to work holistically. > > Ismael > > On Fri, Jul 20, 2018 at 3:50 AM Ch

Re: [VOTE] KIP-367 Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit)

Thanks for all votes. KIP-367 has passed!!! binding votes (3) : Matthias J. Sax Harsha Jason Gustafson non-binding votes (6): Dongjin Lee Manikumar Mickael Maison vito jeng Colin McCabe Bill Bejeck Cheers, Chia-Ping On 2018/09/08 18:27:59, Chia-Ping Tsai wrote: > Hi All, > > I'd li

Re: [DISCUSSION] KIP-376: Implement AutoClosable on appropriate classes that has close()

hi Yishun Thanks for nice KIP! Q1) Why VerifiableProducer extend Closeable rather than AutoCloseable? Q2) I grep project and then noticed there are other close methods but do not implement AutoCloseable. For example: 1) WorkerConnector 2) MemoryRecordsBuilder 3) MetricsReporter 4)

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

gt; myData.toByteArrayOrWhatever()", right? (and of course similar for > deserializers). > > This sounds right to me, so if that is right, I'm still a non-binding +1. > > Thanks, > -John > > On Thu, Sep 20, 2018 at 10:12 PM Chia-Ping Tsai wrote: > > > KI

Re: [VOTE] KIP-367 Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit)

, TimeUnit) call to avoid breaking compatibility, however. > Does the KIP specify keeping the old overload? I can't seem to access the > wiki now. > > best, > Colin > > > On Sat, Sep 8, 2018, at 11:27, Chia-Ping Tsai wrote: > > Hi All, > > > > I'd like to

broken build on windows

hi folks, I love GNU/Linux but it pains me to see broken build on windows. Could someone take a look at PR: https://github.com/apache/kafka/pull/6208 ? It enables kafka to embrace windows again. Cheers, Chia-Ping

[jira] [Created] (KAFKA-8861) Fix flaky RegexSourceIntegrationTest.testMultipleConsumersCanReadFromPartitionedTopic

Chia-Ping Tsai created KAFKA-8861: - Summary: Fix flaky RegexSourceIntegrationTest.testMultipleConsumersCanReadFromPartitionedTopic Key: KAFKA-8861 URL: https://issues.apache.org/jira/browse/KAFKA-8861

[jira] [Created] (KAFKA-9654) ReplicaAlterLogDirsThread can't be created again if the previous ReplicaAlterLogDirsThreadmeet encounters leader epoch error

Chia-Ping Tsai created KAFKA-9654: - Summary: ReplicaAlterLogDirsThread can't be created again if the previous ReplicaAlterLogDirsThreadmeet encounters leader epoch error Key: KAFKA-9654 URL: https

[jira] [Created] (KAFKA-9599) create unique sensor to record group rebalance

Chia-Ping Tsai created KAFKA-9599: - Summary: create unique sensor to record group rebalance Key: KAFKA-9599 URL: https://issues.apache.org/jira/browse/KAFKA-9599 Project: Kafka Issue Type

[jira] [Created] (KAFKA-9476) the error "Scanner SubTypeScanner was not configured" caused by invalid jar when starting worker

Chia-Ping Tsai created KAFKA-9476: - Summary: the error "Scanner SubTypeScanner was not configured" caused by invalid jar when starting worker Key: KAFKA-9476 URL: https://issues.apache.org/jira/browse/

[jira] [Created] (KAFKA-9711) The authentication failure caused by SSLEngine#beginHandshake is not properly caught and handled

Chia-Ping Tsai created KAFKA-9711: - Summary: The authentication failure caused by SSLEngine#beginHandshake is not properly caught and handled Key: KAFKA-9711 URL: https://issues.apache.org/jira/browse/KAFKA-9711

[jira] [Created] (KAFKA-9686) MockConsumer#endOffsets should be idempotent

Chia-Ping Tsai created KAFKA-9686: - Summary: MockConsumer#endOffsets should be idempotent Key: KAFKA-9686 URL: https://issues.apache.org/jira/browse/KAFKA-9686 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9721) ReassignPartitionsCommand#reassignPartitions does not

Chia-Ping Tsai created KAFKA-9721: - Summary: ReassignPartitionsCommand#reassignPartitions does not Key: KAFKA-9721 URL: https://issues.apache.org/jira/browse/KAFKA-9721 Project: Kafka Issue

[jira] [Created] (KAFKA-9854) Re-authenticating causes mismatched parse of response

Chia-Ping Tsai created KAFKA-9854: - Summary: Re-authenticating causes mismatched parse of response Key: KAFKA-9854 URL: https://issues.apache.org/jira/browse/KAFKA-9854 Project: Kafka Issue

[jira] [Resolved] (KAFKA-9476) Worker throws error "Scanner SubTypeScanner was not configured" when loading invalid jar

[ https://issues.apache.org/jira/browse/KAFKA-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-9476. --- Resolution: Duplicate As KAFKA-9712 has PR, this ticket get closed as duplicate. > Wor

[jira] [Resolved] (KAFKA-5889) MetricsTest.testMetricsLeak is flaky

[ https://issues.apache.org/jira/browse/KAFKA-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-5889. --- Resolution: Won't Fix MetricsTest.testMetricsLeak was removed by https://github.com/apache

[jira] [Created] (KAFKA-9786) fix flaky MetricsTest.testGeneralBrokerTopicMetricsAreGreedilyRegistered

Chia-Ping Tsai created KAFKA-9786: - Summary: fix flaky MetricsTest.testGeneralBrokerTopicMetricsAreGreedilyRegistered Key: KAFKA-9786 URL: https://issues.apache.org/jira/browse/KAFKA-9786 Project

[jira] [Created] (KAFKA-9918) SslEngineFactory is NOT closed when channel is closing

Chia-Ping Tsai created KAFKA-9918: - Summary: SslEngineFactory is NOT closed when channel is closing Key: KAFKA-9918 URL: https://issues.apache.org/jira/browse/KAFKA-9918 Project: Kafka Issue

[jira] [Created] (KAFKA-10014) Always try to close all channels in Selector#close

Chia-Ping Tsai created KAFKA-10014: -- Summary: Always try to close all channels in Selector#close Key: KAFKA-10014 URL: https://issues.apache.org/jira/browse/KAFKA-10014 Project: Kafka Issue

[DISCUSS] KIP-581: add tag "partition" to BrokerTopicMetrics so as to observe the partition metrics on the same broker

hi this ticket is about to records partition metrics rather than topic metrics. It helps us to observe more precis metrics for specify partition. The downside is that broker needs more space to keep metrics and the origin metrics interface (tags) is broken since this ticket adds new tag

Re: [DISCUSS] KIP-581: add tag "partition" to BrokerTopicMetrics so as to observe the partition metrics on the same broker

> > Would you please choose another KIP number, maybe 583, I also see KIP-582 > discussion thread appears in the mail list, and insert into table [KIPs under > discussion]. > > > Best Regards, > Cheng Pan > -- Original -- > From:

[jira] [Resolved] (KAFKA-9721) ReassignPartitionsCommand#reassignPartitions doesn't wait for the completion of altering replica folder

[ https://issues.apache.org/jira/browse/KAFKA-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-9721. --- Resolution: Won't Fix ReassignPartitionsCommand does not guarantee to "complete" t

[jira] [Resolved] (KAFKA-7084) NewTopicBuilder#config should accept Map rather than Map

[ https://issues.apache.org/jira/browse/KAFKA-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-7084. --- Resolution: Won't Fix > NewTopicBuilder#config should accept Map rather than &g

[jira] [Resolved] (KAFKA-6931) Make worker id configurable

[ https://issues.apache.org/jira/browse/KAFKA-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-6931. --- Resolution: Won't Fix > Make worker id configura

[jira] [Resolved] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

[ https://issues.apache.org/jira/browse/KAFKA-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-6941. --- Resolution: Won't Fix > when passing port = 0 to worker, the advertisedPort still i

[jira] [Created] (KAFKA-9730) add tag "partition" to BrokerTopicMetrics so as to observe the metrics of partition in the same broker

Chia-Ping Tsai created KAFKA-9730: - Summary: add tag "partition" to BrokerTopicMetrics so as to observe the metrics of partition in the same broker Key: KAFKA-9730 URL: https://issues.apache.org/jira/br

[jira] [Resolved] (KAFKA-10129) Fail QA if there are javadoc warnings

[ https://issues.apache.org/jira/browse/KAFKA-10129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10129. Resolution: Won't Fix > Fail QA if there are javadoc warni

[jira] [Resolved] (KAFKA-10170) ReplicaManager should be responsible for checking delayed operations after appending to the log.

[ https://issues.apache.org/jira/browse/KAFKA-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10170. Resolution: Duplicate > ReplicaManager should be responsible for checking dela

[jira] [Created] (KAFKA-10463) the necessary utilities in Dockerfile should include git

Chia-Ping Tsai created KAFKA-10463: -- Summary: the necessary utilities in Dockerfile should include git Key: KAFKA-10463 URL: https://issues.apache.org/jira/browse/KAFKA-10463 Project: Kafka

[jira] [Created] (KAFKA-10479) Throw exception if users try to update configs of existing listeners

Chia-Ping Tsai created KAFKA-10479: -- Summary: Throw exception if users try to update configs of existing listeners Key: KAFKA-10479 URL: https://issues.apache.org/jira/browse/KAFKA-10479 Project

[jira] [Resolved] (KAFKA-10583) Thread-safety of AdminClient is not documented

[ https://issues.apache.org/jira/browse/KAFKA-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10583. Resolution: Fixed > Thread-safety of AdminClient is not documen

[jira] [Reopened] (KAFKA-10043) Some parameters will be overwritten which was configured in consumer.config where running "ConsumerPerformance.scala"

[ https://issues.apache.org/jira/browse/KAFKA-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened KAFKA-10043: Reopen since it is not resolved > Some parameters will be overwritten which was configu

[jira] [Created] (KAFKA-10438) Lazy initialization of record header to reduce memory usage in validating records

Chia-Ping Tsai created KAFKA-10438: -- Summary: Lazy initialization of record header to reduce memory usage in validating records Key: KAFKA-10438 URL: https://issues.apache.org/jira/browse/KAFKA-10438

[jira] [Created] (KAFKA-10433) Reuse the ByteBuffer in validating compressed records

Chia-Ping Tsai created KAFKA-10433: -- Summary: Reuse the ByteBuffer in validating compressed records Key: KAFKA-10433 URL: https://issues.apache.org/jira/browse/KAFKA-10433 Project: Kafka

[jira] [Created] (KAFKA-10412) Deprecate all setters of Headers

Chia-Ping Tsai created KAFKA-10412: -- Summary: Deprecate all setters of Headers Key: KAFKA-10412 URL: https://issues.apache.org/jira/browse/KAFKA-10412 Project: Kafka Issue Type: Improvement

KIP-658 Deprecate all setters of Headers

Hi everyone, I would like to start a discussion on KIP-658: https://cwiki.apache.org/confluence/x/-DJ4CQ KIP-658 plans to deprecate all setters of Headers and provide default implementation. The benefit of this KIP are shown below. 1. Users don't need to implement those setters which are not

Re: KIP-658 Deprecate all setters of Headers

implementation? > > > -Matthias > > > On 8/18/20 3:39 AM, Chia-Ping Tsai wrote: > > Hi everyone, > > > > I would like to start a discussion on KIP-658: > > https://cwiki.apache.org/confluence/x/-DJ4CQ > > > > KIP-658 plans to deprecate

[jira] [Created] (KAFKA-10446) add "lz4" and "zstd" to compression type of benchmark_test.py

Chia-Ping Tsai created KAFKA-10446: -- Summary: add "lz4" and "zstd" to compression type of benchmark_test.py Key: KAFKA-10446 URL: https://issues.apache.org/jira/browse/KAFKA-10446

[jira] [Created] (KAFKA-10514) flaky test StateDirectoryTest.shouldLogStateDirCleanerMessage

Chia-Ping Tsai created KAFKA-10514: -- Summary: flaky test StateDirectoryTest.shouldLogStateDirCleanerMessage Key: KAFKA-10514 URL: https://issues.apache.org/jira/browse/KAFKA-10514 Project: Kafka

[jira] [Created] (KAFKA-10044) Deprecate ConsumerConfig#addDeserializerToConfig(Properties, Deserializer, Deserializer) and ProducerConfig#addSerializerToConfig(Properties, Serializer, Serializer)

Chia-Ping Tsai created KAFKA-10044: -- Summary: Deprecate ConsumerConfig#addDeserializerToConfig(Properties, Deserializer, Deserializer) and ProducerConfig#addSerializerToConfig(Properties, Serializer, Serializer) Key: KAFKA

[jira] [Created] (KAFKA-10069) The user-defined "predicate" and "negate" are not removed from Transformation

Chia-Ping Tsai created KAFKA-10069: -- Summary: The user-defined "predicate" and "negate" are not removed from Transformation Key: KAFKA-10069 URL: https://issues.apache.org/jir

[DISCUSS] KIP-619 Deprecate ConsumerConfig#addDeserializerToConfig(Properties, Deserializer, Deserializer) and ProducerConfig#addSerializerToConfig(Properties, Serializer, Serializer)

hi All, This KIP plans to deprecate two unused methods without replacement. All suggestions are welcome! KIP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749118 ISSUE: https://issues.apache.org/jira/browse/KAFKA-10044 --- Chia-Ping

[jira] [Resolved] (KAFKA-10092) Remove unnecessary enum modifier in NioEchoServer

[ https://issues.apache.org/jira/browse/KAFKA-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10092. Fix Version/s: 2.8.0 Resolution: Fixed > Remove unnecessary enum modif

[jira] [Resolved] (KAFKA-10125) The partition which is removing should be considered to be under reassignment

[ https://issues.apache.org/jira/browse/KAFKA-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10125. Resolution: Won't Fix > The partition which is removing should be considered to be un

[jira] [Resolved] (KAFKA-10108) The cached configs of SslFactory should be updated only if the ssl Engine Factory is updated successfully

[ https://issues.apache.org/jira/browse/KAFKA-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10108. Resolution: Won't Fix > The cached configs of SslFactory should be updated o

[jira] [Created] (KAFKA-10326) Both serializer and deserializer should be able to see the generated client id

Chia-Ping Tsai created KAFKA-10326: -- Summary: Both serializer and deserializer should be able to see the generated client id Key: KAFKA-10326 URL: https://issues.apache.org/jira/browse/KAFKA-10326

[jira] [Resolved] (KAFKA-10194) run the reset tool between stopping StreamsOptimizedTest and starting the new one

[ https://issues.apache.org/jira/browse/KAFKA-10194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10194. Resolution: Duplicate > run the reset tool between stopping StreamsOptimizedT

[jira] [Created] (KAFKA-10234) The key/value deserializer used by ConsoleConsumer is not closed

Chia-Ping Tsai created KAFKA-10234: -- Summary: The key/value deserializer used by ConsoleConsumer is not closed Key: KAFKA-10234 URL: https://issues.apache.org/jira/browse/KAFKA-10234 Project: Kafka

Re: [VOTE] KIP-620 Deprecate ConsumerConfig#addDeserializerToConfig(Properties, Deserializer, Deserializer) and ProducerConfig#addSerializerToConfig(Properties, Serializer, Serializer)

nks for the KIP. > > > > On Wed, Jun 10, 2020 at 11:43 PM Matthias J. Sax wrote: > > > > > Yes, it does. > > > > > > I guess many people are busy wrapping up 2.6 release. Today is code > > freeze. > > > > > > > > > -Matt

[jira] [Created] (KAFKA-10244) An new java interface to replace 'kafka.common.MessageReader'

Chia-Ping Tsai created KAFKA-10244: -- Summary: An new java interface to replace 'kafka.common.MessageReader' Key: KAFKA-10244 URL: https://issues.apache.org/jira/browse/KAFKA-10244 Project: Kafka

  1   2   3   4   5   6   >