Build failed in Jenkins: kafka-trunk-jdk8 #3797

See -- Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Start

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

See

[jira] [Created] (KAFKA-8679) kafka-topics.sh --describe with --zookeeper throws error when there is no topic

Weichu Liu created KAFKA-8679: - Summary: kafka-topics.sh --describe with --zookeeper throws error when there is no topic Key: KAFKA-8679 URL: https://issues.apache.org/jira/browse/KAFKA-8679 Project: Kafk

Build failed in Jenkins: kafka-trunk-jdk11 #703

See Changes: [bbejeck] MINOR: improve error message for incorrect window-serde initialization -- [...truncated 6.45 MB...] org.apache.kafka.connect.data.ValuesTest > s

[jira] [Created] (KAFKA-8678) LeaveGroup request versioning on throttle time is incorrect

Boyang Chen created KAFKA-8678: -- Summary: LeaveGroup request versioning on throttle time is incorrect Key: KAFKA-8678 URL: https://issues.apache.org/jira/browse/KAFKA-8678 Project: Kafka Issue

Re: [DISCUSS] KIP-479: Add Materialized to Join

Hi Bill, thanks for your explanations. I'm on board with your decision too. Guozhang On Wed, Jul 17, 2019 at 10:20 AM Bill Bejeck wrote: > Thanks for the response, John. > > > If I can offer my thoughts, it seems better to just document on the > > Stream join javadoc for the Materialized param

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Yes, I believe that's what I had in mind. Again, not totally sure it makes sense, but I believe something similar is the rationale for having the partitioner option in Produced. Thanks, -John On Wed, Jul 17, 2019 at 3:20 PM Levani Kokhreidze wrote: > > Hey John, > > Oh that’s interesting use-cas

Re: [VOTE] KIP-480 : Sticky Partitioner

Hello all, I wanted to let you all know the KIP has been updated. The ComputedPartition class has been removed in favor of simply returning an integer to represent the record's partition. In short, the implications of this change mean that keyed records will also trigger a change in the sticky par

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

Thanks, Stanislav. Let's restart the vote to reflect the fact that we've made significant changes. The new vote will go for 3 days as usual. I'll start with my +1 (binding). best, Colin On Wed, Jul 17, 2019, at 08:56, Stanislav Kozlovski wrote: > Hey everybody, > > We have further iterated

Build failed in Jenkins: kafka-trunk-jdk11 #702

See Changes: [github] MINOR: Fix api exception single argument constructor usage (#6956) -- [...truncated 2.56 MB...] org.apache.kafka.connect.json.JsonConverterTest > by

Re: [VOTE] KIP-488: Clean up Sum,Count,Total Metrics

+1 (binding) for the updated KIP. On Wed, Jul 17, 2019 at 4:09 PM John Roesler wrote: > Hey, Bruno and Bill, > > Since you cast your votes before the KIP was updated, do you mind > re-casting just so we can be sure you're still in favor? > > Thanks, > -John > > On Wed, Jul 17, 2019 at 2:01 PM Gu

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hey John, Oh that’s interesting use-case. Do I understand this correctly, in your example I would first issue repartition(Repartitioned) with proper partitioner that essentially would be the same as the topic I want to join with and then do the KStream#join with DSL? Regards, Levani > On Jul

Build failed in Jenkins: kafka-trunk-jdk8 #3795

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hey, all, just to chime in, I think it might be useful to have an option to specify the partitioner. The case I have in mind is that some data may get repartitioned and then joined with an input topic. If the right-side input topic uses a custom partitioning strategy, then the repartitioned stream

Re: [VOTE] KIP-488: Clean up Sum,Count,Total Metrics

Hey, Bruno and Bill, Since you cast your votes before the KIP was updated, do you mind re-casting just so we can be sure you're still in favor? Thanks, -John On Wed, Jul 17, 2019 at 2:01 PM Guozhang Wang wrote: > > +1 (binging). > > This is a great cleanup, thanks John! > > Guozhang > > On Wed,

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

Cool. I'll update the KIP, then, and we can re-start the vote. (looks like you've already cast a vote :) ) -John On Wed, Jul 17, 2019 at 1:23 PM Ryanne Dolan wrote: > > John, makes sense to me! Thanks. > > Ryanne > > On Wed, Jul 17, 2019, 1:16 PM John Roesler wrote: > > > Agreed. I think the n

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Yes, I was thinking about it as well. To be honest I’m not sure about it yet. As Kafka Streams DSL user, I don’t really think I would need control over partitioner for internal topics. As a user, I would assume that Kafka Streams knows best how to partition data for internal topics. In this KIP I

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Thanks for clearing that up. I agree that Repartitioned would be a useful addition. I'm wondering if it might also need to have a withStreamPartitioner method/field, similar to Produced? I'm not sure how widely this feature is really used, but seems it should be available for repartition topics. O

Build failed in Jenkins: kafka-trunk-jdk8 #3794

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Re: [VOTE] KIP-488: Clean up Sum,Count,Total Metrics

+1 (binging). This is a great cleanup, thanks John! Guozhang On Wed, Jul 17, 2019 at 11:26 AM Ryanne Dolan wrote: > +1 (non-binding) > > Thanks for the interesting discussion. > > Ryanne > > On Fri, Jul 12, 2019, 2:49 PM Ryanne Dolan wrote: > > > John, I'm glad to learn I'm not the only one w

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hey Sophie, In both cases KStream#repartition and KStream#repartition(Repartitioned) topic will be created and managed by Kafka Streams. Idea of Repartitioned is to give user more control over the topic such as num of partitions. I feel like Repartitioned parameter is something that is missing

Re: [VOTE] KIP-488: Clean up Sum,Count,Total Metrics

+1 (non-binding) Thanks for the interesting discussion. Ryanne On Fri, Jul 12, 2019, 2:49 PM Ryanne Dolan wrote: > John, I'm glad to learn I'm not the only one who's re-read the metrics > code multiple times. > > I do wonder if the proposed names could be improved further though, given > that

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

John, makes sense to me! Thanks. Ryanne On Wed, Jul 17, 2019, 1:16 PM John Roesler wrote: > Agreed. I think the names are actually not ambiguous once you recall > that the stats summarize measurements and each measurement is a > floating point number, but there's enough overlap that I also was

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

Agreed. I think the names are actually not ambiguous once you recall that the stats summarize measurements and each measurement is a floating point number, but there's enough overlap that I also was initially confused as well. I do plan to make this super clear in the documentation. Thanks, -John

Build failed in Jenkins: kafka-trunk-jdk8 #3793

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

Sounds good to me By the way, while I agree that we can't really do better than Sum and Count I will say I also found the distinction a bit unclear at first glance. We should at least document clearly that "Sum" is a "sum of values" whereas "Count" is a "number of things" -- but that doesn't need

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hey Levani, Thanks for the KIP! Can you clarify one thing for me -- for the KStream#repartition signature taking a Repartitioned, will the topic be auto-created by Streams (which seems to be the case for the signature without a Repartitioned) or does it have to be pre-created? The wording in the K

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

Thanks for the replies. I guess that if we did add (e.g.) ExponentiallyWeightedWindowedX or something, it should still be pretty obvious that WindowedX is the unweighted version? In that case, I buy the argument that we don't need "Simple" and we can just go with: WindowedSum, WindowedCount Cumul

Re: Add to contribution list

No problem Omar. You're all set now in the wiki as well. -Bill On Wed, Jul 17, 2019 at 1:19 PM Omar Al-Safi wrote: > Awesome, thanks a lot! Correct apparently it doesn't use Jira crowd > directory. I have created a username there, the same username: omarsmak > > Thanks again! > Omar > > On Wed

Build failed in Jenkins: kafka-trunk-jdk8 #3792

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP-479: Add Materialized to Join

Thanks for the response, John. > If I can offer my thoughts, it seems better to just document on the > Stream join javadoc for the Materialized parameter that it will not > make the join result queriable. I'm not opposed to the queriable flag > in general, but introducing it is a much larger consi

Re: Add to contribution list

Awesome, thanks a lot! Correct apparently it doesn't use Jira crowd directory. I have created a username there, the same username: omarsmak Thanks again! Omar On Wed, 17 Jul 2019 at 19:06, Bill Bejeck wrote: > Thanks for your interest in Apache Kafka. > > You're all set with Jira, but I couldn'

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hello, One more bump about KIP-221 (https://cwiki.apache.org/confluence/display/KAFKA/KIP-221%3A+Enhance+KStream+with+Connecting+Topic+Creation+and+Repartition+Hint )

Re: Add to contribution list

Thanks for your interest in Apache Kafka. You're all set with Jira, but I couldn't find your user name in the wiki. The wiki requires a separate username creation. Can you add yourself there and ping the list again and we'll get you added. Thanks, Bill On Wed, Jul 17, 2019 at 6:42 AM Omar Al-Sa

[jira] [Created] (KAFKA-8677) Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

Boyang Chen created KAFKA-8677: -- Summary: Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl Key: KAFKA-8677 URL: https://issues.apache.org/jira/browse/KAFKA-8677

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

Thanks for the crash course in statistical terms :) In light of this I definitely support Cumulative{Sum,Count}, but I'm really not crazy about SimpleWindowed{Sum,Count} (vs just Windowed). Not so much because of its unfortunate length (although that is unfortunate it shouldn't be a deciding facto

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

I'm fine with the new names. While I was previously in the "brevity" camp when it came to the Cumulative name, I'll take clarity over brevity. Thanks for the updates, John. -Bill On Wed, Jul 17, 2019 at 11:18 AM John Roesler wrote: > Thanks for the discussion, all. > > I've done a little more

[jira] [Resolved] (KAFKA-8218) IllegalStateException while accessing context in Transformer

[ https://issues.apache.org/jira/browse/KAFKA-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8218. -- Resolution: Not A Problem > IllegalStateException while accessing context in Transformer >

[jira] [Resolved] (KAFKA-7176) State store metrics for migrated tasks are not removed

[ https://issues.apache.org/jira/browse/KAFKA-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7176. -- Resolution: Fixed Fix Version/s: 2.3.0 > State store metrics for migrated tasks are not

[jira] [Resolved] (KAFKA-7850) Remove deprecated KStreamTestDriver

[ https://issues.apache.org/jira/browse/KAFKA-7850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7850. -- Resolution: Fixed Fix Version/s: 2.3.0 KStreamTestDriver has been removed since 2.3.0 re

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

Hello all, I was looking at this KIP again, and there is a decision I made that I think is worth discussing. In the case where both the broker and producer's 'auto.create.topics.enable' are set to true, we have to choose either the broker configs or the producer configs for the replication factor

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

Hey everybody, We have further iterated on the KIP in the accompanying discussion thread and I'd like to propose we resume the vote. Some notable changes: - we will store reassignment information in the `/brokers/topics/[topic]` - we will internally use two collections to represent a reassignment

Re: [DISCUSS] KIP-488: Clean up Sum,Count,Total Metrics

Thanks for the discussion, all. I've done a little more research into the statistical terminology. Matthias is correct, "running" and "moving" appear to be synonyms. Unfortunately, both can be computed either over a window of the last N measurements or over all prior measurements. "Moving" just si

Jenkins build is back to normal : kafka-trunk-jdk11 #701

See

Re: Any documents on this

ii) Are we talking here about a Kafka OnPremise to Kafka into the cloud migration or you would like to move the data from OracleDB OnPremise to Kafka OnCloud? On Mon, 15 Jul 2019 at 14:01, Habeebullah khwaja wrote: > Hi, > I got few questions. Can anyone please give me a feedback > i)To upgrade

Add to contribution list

Hi guys, I would like to be added to the contribution list in Jira and Wiki in order to work on some issues. My username is : omarsmak Thanks

Re: [DISCUSS] KIP-492 Add java security providers in Kafka Security config

Hi Sandeep, Thanks for the KIP. A few questions below: 1. Is the main use case for this KIP adding security providers for SSL? If so, wouldn't a more generic solution like KIP-383 work for this? 2. Presumably this config would also apply to clients. If so, have we thought through the

Build failed in Jenkins: kafka-trunk-jdk8 #3791

See Changes: [jason] KAFKA-8024; Fix `UtilsTest` failure under non-english locales (#6351) -- [...truncated 2.56 MB...] org.apache.kafka.connect.transforms.TimestampConve

[jira] [Created] (KAFKA-8676) Avoid Stopping Unnecessary Connectors and Tasks

Luying Liu created KAFKA-8676: - Summary: Avoid Stopping Unnecessary Connectors and Tasks Key: KAFKA-8676 URL: https://issues.apache.org/jira/browse/KAFKA-8676 Project: Kafka Issue Type: Improvem

[jira] [Created] (KAFKA-8675) "Main" consumers are not unsubsribed on KafkaStreams.close()

Modestas Vainius created KAFKA-8675: --- Summary: "Main" consumers are not unsubsribed on KafkaStreams.close() Key: KAFKA-8675 URL: https://issues.apache.org/jira/browse/KAFKA-8675 Project: Kafka