回复: 你好,我发现了你们kafka-API文档的文本错误问题.

[Hu Xi]

谢谢指正。已经提交了一个jira ticket 
[KAFKA-10222]准备修复了：）



发件人: Koray 
发送时间: 2020年6月30日 23:06
收件人: users-subscribe ; users 
; dev-subscribe ; dev 
; dev ; dev-subscribe 
; apache 
主题: 你好,我发现了你们kafka-API文档的文本错误问题.

你好,我发现了你们的API文档上的一个错误信息,提供给你们修改,谢谢.

错误问题是 :   KStreamBuilder这个类,并没有from的方法. 我这里展示的是kafka 
10.0版本..,但愿能修改过来,以免误导开发者们的使用. 谢谢
这是问题网址:  
http://kafka.apache.org/0100/javadoc/index.html?org/apache/kafka/streams/KafkaStreams.html



[cid:02F3F845@59AAC928.0955FB5E]
 [cid:DBEF9ACA@7D891A2E.0955FB5E]

destination topics in mm2 larger than source topic

[Iftach Ben-Yosef]

Hello everyone.

I'm testing mm2 for our cross dc topic replication. We used to do it using
mm1 but faced various issues.

So far, mm2 is working well, but I have 1 issue which I can't really
explain; the destination topic is larger than the source topic.

For example, We have 1 topic which on the source cluster is around
2.8-2.9TB with retention.ms=8640

I added to our mm2 cluster the "sync.topic.configs.enabled=false" config,
and edited the retention.ms of the destination topic to be 5760. Other
than that, I haven't touched the topic created by mm2 on the destination
cluster.

By logic I'd say that if I shortened the retention on the destination, the
topic size should decrease, but in practice, I see that it is larger than
the source topic (it's about 4.6TB).
This same behaviour is seen on all 3 topics which I am currently mirroring
(all 3 from different source clusters, into the same destination clusters)

Does anyone have any idea as to why mm2 acts this way for me?

Thanks,
Iftach

-- 
The above terms reflect a potential business arrangement, are provided 
solely as a basis for further discussion, and are not intended to be and do 
not constitute a legally binding obligation. No legally binding obligations 
will be created, implied, or inferred until an agreement in final form is 
executed in writing by all parties involved.


This email and any 
attachments hereto may be confidential or privileged.  If you received this 
communication by mistake, please don't forward it to anyone else, please 
erase all copies and attachments, and please let me know that it has gone 
to the wrong person. Thanks.

Re: destination topics in mm2 larger than source topic

[Ryanne Dolan]

Iftach, is it possible the source topic is compressed?

Ryanne

On Wed, Jul 1, 2020, 8:39 AM Iftach Ben-Yosef 
wrote:

> Hello everyone.
>
> I'm testing mm2 for our cross dc topic replication. We used to do it using
> mm1 but faced various issues.
>
> So far, mm2 is working well, but I have 1 issue which I can't really
> explain; the destination topic is larger than the source topic.
>
> For example, We have 1 topic which on the source cluster is around
> 2.8-2.9TB with retention.ms=8640
>
> I added to our mm2 cluster the "sync.topic.configs.enabled=false" config,
> and edited the retention.ms of the destination topic to be 5760. Other
> than that, I haven't touched the topic created by mm2 on the destination
> cluster.
>
> By logic I'd say that if I shortened the retention on the destination, the
> topic size should decrease, but in practice, I see that it is larger than
> the source topic (it's about 4.6TB).
> This same behaviour is seen on all 3 topics which I am currently mirroring
> (all 3 from different source clusters, into the same destination clusters)
>
> Does anyone have any idea as to why mm2 acts this way for me?
>
> Thanks,
> Iftach
>
> --
> The above terms reflect a potential business arrangement, are provided
> solely as a basis for further discussion, and are not intended to be and
> do
> not constitute a legally binding obligation. No legally binding
> obligations
> will be created, implied, or inferred until an agreement in final form is
> executed in writing by all parties involved.
>
>
> This email and any
> attachments hereto may be confidential or privileged.  If you received
> this
> communication by mistake, please don't forward it to anyone else, please
> erase all copies and attachments, and please let me know that it has gone
> to the wrong person. Thanks.
>

Re: destination topics in mm2 larger than source topic

[Iftach Ben-Yosef]

Hi Ryanne, thanks for the quick reply.

I had the thought it might be compression. I see that the topics have the
following config "compression.type=producer". This is for both the source
and destination topics. Should I check something else regarding compression?

Also, the destination topics are larger than the same topic being mirrored
using mm1 - the sum of the 3 topics mirrored by mm2 is much larger than the
1 topic that mm1 produced (they have the same 3 source topics, only mm1
aggregates to 1 destination topic). Retention is again the same between the
mm1 destination topic and the mm2 destination topics.

Thanks,
Iftach


On Wed, Jul 1, 2020 at 4:54 PM Ryanne Dolan  wrote:

> Iftach, is it possible the source topic is compressed?
>
> Ryanne
>
> On Wed, Jul 1, 2020, 8:39 AM Iftach Ben-Yosef 
> wrote:
>
> > Hello everyone.
> >
> > I'm testing mm2 for our cross dc topic replication. We used to do it
> using
> > mm1 but faced various issues.
> >
> > So far, mm2 is working well, but I have 1 issue which I can't really
> > explain; the destination topic is larger than the source topic.
> >
> > For example, We have 1 topic which on the source cluster is around
> > 2.8-2.9TB with retention.ms=8640
> >
> > I added to our mm2 cluster the "sync.topic.configs.enabled=false" config,
> > and edited the retention.ms of the destination topic to be 5760.
> Other
> > than that, I haven't touched the topic created by mm2 on the destination
> > cluster.
> >
> > By logic I'd say that if I shortened the retention on the destination,
> the
> > topic size should decrease, but in practice, I see that it is larger than
> > the source topic (it's about 4.6TB).
> > This same behaviour is seen on all 3 topics which I am currently
> mirroring
> > (all 3 from different source clusters, into the same destination
> clusters)
> >
> > Does anyone have any idea as to why mm2 acts this way for me?
> >
> > Thanks,
> > Iftach
> >
> > --
> > The above terms reflect a potential business arrangement, are provided
> > solely as a basis for further discussion, and are not intended to be and
> > do
> > not constitute a legally binding obligation. No legally binding
> > obligations
> > will be created, implied, or inferred until an agreement in final form is
> > executed in writing by all parties involved.
> >
> >
> > This email and any
> > attachments hereto may be confidential or privileged.  If you received
> > this
> > communication by mistake, please don't forward it to anyone else, please
> > erase all copies and attachments, and please let me know that it has gone
> > to the wrong person. Thanks.
> >
>

-- 
The above terms reflect a potential business arrangement, are provided 
solely as a basis for further discussion, and are not intended to be and do 
not constitute a legally binding obligation. No legally binding obligations 
will be created, implied, or inferred until an agreement in final form is 
executed in writing by all parties involved.


This email and any 
attachments hereto may be confidential or privileged.  If you received this 
communication by mistake, please don't forward it to anyone else, please 
erase all copies and attachments, and please let me know that it has gone 
to the wrong person. Thanks.

User License Agreement - Kafka v.2.4.0

[Theresa Sowinski]

May I please get a copy of the user license?  I am trying to determine whether 
your license is permissive or restrictive.


Thank you,
Reese

Theresa 'Reese' Sowinski
Contracts Manager
Burgess
800-637-2004
burgessgroup.com
Note: The information, including any attachments, contained in this message is 
confidential and intended only for use by the individual(s) or entity(s) to 
which it is addressed. If you are not an intended recipient or if you have 
received this message in error, please promptly delete this message. Any 
dissemination, distribution, or copying of this information is strictly 
prohibited. Burgess, The B logo, Burgess Source, and Payment Accountability are 
trademarks of The Burgess Group, LLC and are registered with the U.S. Patent 
and Trademark Office.

Re: User License Agreement - Kafka v.2.4.0

[John-Taylor Smith]

Hello Reese,
Apache Kafka is licensed under the Apache License 2.0. You can find that
here: https://www.apache.org/licenses/LICENSE-2.0

JT



On Wed, Jul 1, 2020 at 1:10 PM Theresa Sowinski <
reese.sowin...@burgessgroup.com> wrote:

> May I please get a copy of the user license?  I am trying to determine
> whether your license is permissive or restrictive.
>
>
> Thank you,
> Reese
>
> Theresa 'Reese' Sowinski
> Contracts Manager
> Burgess
> 800-637-2004
> burgessgroup.com
> Note: The information, including any attachments, contained in this
> message is confidential and intended only for use by the individual(s) or
> entity(s) to which it is addressed. If you are not an intended recipient or
> if you have received this message in error, please promptly delete this
> message. Any dissemination, distribution, or copying of this information is
> strictly prohibited. Burgess, The B logo, Burgess Source, and Payment
> Accountability are trademarks of The Burgess Group, LLC and are registered
> with the U.S. Patent and Trademark Office.
>
>

Re: User License Agreement - Kafka v.2.4.0

[M. Manna]

Hello,

Apache Kafka has both Apache 2.0 licence (a fine text at the bottom of
Kafka website), and Confluent licence (From Confluent.io).

Depending on what you use, you can get it from the appropriate site.

I hope this helps ?

Regards,

On Wed, 1 Jul 2020 at 18:10, Theresa Sowinski <
reese.sowin...@burgessgroup.com> wrote:

> May I please get a copy of the user license?  I am trying to determine
> whether your license is permissive or restrictive.
>
>
> Thank you,
> Reese
>
> Theresa 'Reese' Sowinski
> Contracts Manager
> Burgess
> 800-637-2004
> burgessgroup.com
> Note: The information, including any attachments, contained in this
> message is confidential and intended only for use by the individual(s) or
> entity(s) to which it is addressed. If you are not an intended recipient or
> if you have received this message in error, please promptly delete this
> message. Any dissemination, distribution, or copying of this information is
> strictly prohibited. Burgess, The B logo, Burgess Source, and Payment
> Accountability are trademarks of The Burgess Group, LLC and are registered
> with the U.S. Patent and Trademark Office.
>
>