Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #23

2020-08-19 Thread Apache Jenkins Server
See Changes: [github] KAFKA-10407: Have KafkaLog4jAppender support `linger.ms` and `batch.size` (#9189) -- [...truncated 3.22 MB...]

[jira] [Resolved] (KAFKA-10407) add linger.ms parameter support to KafkaLog4jAppender

2020-08-19 Thread huxihx (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-10407. Fix Version/s: 2.7.0 Resolution: Fixed > add linger.ms parameter support to KafkaLog4jAppender >

[GitHub] [kafka-site] mjsax merged pull request #298: MINOR: remove unreleased versions from CVE page

2020-08-19 Thread GitBox
mjsax merged pull request #298: URL: https://github.com/apache/kafka-site/pull/298 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: Someone should remove nonexistent versions 2.0.2, 2.1.2 from https://kafka.apache.org/cve-list

2020-08-19 Thread Matthias J. Sax
Franklin, thanks for raising this. I opened a PR to update the web-page accordingly: https://github.com/apache/kafka-site/pull/298 -Matthias On 8/10/20 10:53 AM, Franklin Davis wrote: > https://kafka.apache.org/cve-list APACHE KAFKA SECURITY VULNERABILITIES > incorrectly lists fixed versions

[GitHub] [kafka-site] mjsax opened a new pull request #298: MINOR: remove unreleased versions from CVE page

2020-08-19 Thread GitBox
mjsax opened a new pull request #298: URL: https://github.com/apache/kafka-site/pull/298 As reported on the mailing list: https://lists.apache.org/list.html?dev@kafka.apache.org:lte=1M:cve%202.0.2%202.1.2 Call for review @ijuma

Re: [VOTE] KIP-657: Add Customized Kafka Streams Logo

2020-08-19 Thread Boyang Chen
Hey Ben, that otter was supposed to be a river-otter to connect to "streams". And of course, it's cute :) On Wed, Aug 19, 2020 at 12:41 PM Philip Schmitt wrote: > Hi, > > I’m with Robin and Michael here. > > What this decision needs is a good design brief. > This article seems decent: >

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

2020-08-19 Thread Harsha Ch
Hi Jun, Thanks. This will help a lot. Tuesday will work for us. -Harsha On Wed, Aug 19, 2020 at 1:24 PM Jun Rao wrote: > Hi, Satish, Ying, Harsha, > > Do you think it would be useful to have a regular virtual meeting to > discuss this KIP? The goal of the meeting will be sharing >

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #9

2020-08-19 Thread Apache Jenkins Server
See Changes: [github] Revert KAFKA-9309: Add the ability to translate Message to JSON (#9197) -- [...truncated 3.15 MB...]

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

2020-08-19 Thread Jun Rao
Hi, Satish, Ying, Harsha, Do you think it would be useful to have a regular virtual meeting to discuss this KIP? The goal of the meeting will be sharing design/development progress and discussing any open issues to accelerate this KIP. If so, will every Tuesday (from next week) 9am-10am PT work

Re: [VOTE] KIP-657: Add Customized Kafka Streams Logo

2020-08-19 Thread Philip Schmitt
Hi, I’m with Robin and Michael here. What this decision needs is a good design brief. This article seems decent: https://yourcreativejunkie.com/logo-design-brief-the-ultimate-guide-for-designers/ Robin is right about the usage requirements. It goes a bit beyond resolution. How does the logo

Re: [DISCUSSION] KIP-619: Add internal topic creation support

2020-08-19 Thread Cheng Tan
Hi David, Thanks for the feedback. They are really helpful. > Can you clarify a bit more what the difference is between regular topics > and internal topics (excluding __consumer_offsets and > __transaction_state)? Reading your last message, if internal topics > (excluding the two) can be

Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #21

2020-08-19 Thread Apache Jenkins Server
See

Re: [VOTE] KIP-657: Add Customized Kafka Streams Logo

2020-08-19 Thread Robin Moffatt
I echo what Michael says here. Another consideration is that logos are often shrunk (when used on slides) and need to work at lower resolution (think: printing swag, stitching socks, etc) and so whatever logo we come up with needs to not be too fiddly in the level of detail - something that I

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #22

2020-08-19 Thread Apache Jenkins Server
See Changes: [github] MINOR: Include security configs for topic delete in system tests (#9142) -- [...truncated 3.23 MB...]

Re: [VOTE] KIP-657: Add Customized Kafka Streams Logo

2020-08-19 Thread Michael Noll
Hi all! Great to see we are in the process of creating a cool logo for Kafka Streams. First, I apologize for sharing feedback so late -- I just learned about it today. :-) Here's my *personal, subjective* opinion on the currently two logo candidates for Kafka Streams. TL;DR: Sorry, but I

Re: [DISCUSS] KIP-406: GlobalStreamThread should honor custom reset policy

2020-08-19 Thread Navinder Brar
Thanks Matthias & John,  I am glad we are converging towards an understanding. So, to summarize,  we will still keep treating this change in KIP and instead of providing a reset strategy, we will cleanup, and reset to earliest and build the state.  When we hit the exception and we are

[jira] [Created] (KAFKA-10421) Kafka Producer deadlocked on get call

2020-08-19 Thread Ranadeep Deb (Jira)
Ranadeep Deb created KAFKA-10421: Summary: Kafka Producer deadlocked on get call Key: KAFKA-10421 URL: https://issues.apache.org/jira/browse/KAFKA-10421 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-10420) group instance id Optional.empty failed due to UNKNOWN_MEMBER_ID, resetting generation when running kafka client 2.6 against broker 2.3.1

2020-08-19 Thread Tomasz Kaszuba (Jira)
Tomasz Kaszuba created KAFKA-10420: -- Summary: group instance id Optional.empty failed due to UNKNOWN_MEMBER_ID, resetting generation when running kafka client 2.6 against broker 2.3.1 Key: KAFKA-10420 URL:

Re: [DISCUSS] KIP-406: GlobalStreamThread should honor custom reset policy

2020-08-19 Thread Matthias J. Sax
Your observation is correct. Connecting (regular) stores to processors is necessary to "merge" sub-topologies into single ones if a store is shared. -- For global stores, the structure of the program does not change and thus connecting srocessors to global stores is not required. Also given our