[GitHub] [kafka-site] ocadaruma opened a new pull request, #414: MINOR: fix streams tutorial

[GitBox]

ocadaruma opened a new pull request, #414:
URL: https://github.com/apache/kafka-site/pull/414

   refs: https://github.com/apache/kafka/pull/12251


-- 
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 the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [kafka-site] showuon merged pull request #414: MINOR: fix streams tutorial

[GitBox]

showuon merged PR #414:
URL: https://github.com/apache/kafka-site/pull/414


-- 
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 the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [kafka-site] showuon commented on pull request #414: MINOR: fix streams tutorial

[GitBox]

showuon commented on PR #414:
URL: https://github.com/apache/kafka-site/pull/414#issuecomment-1146565749

   Thank you, @ocadaruma !


-- 
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 the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.2 #52

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 523264 lines...]
[2022-06-04T10:26:56.001Z] > Task :connect:api:copyDependantLibs UP-TO-DATE
[2022-06-04T10:26:56.001Z] > Task :connect:api:jar UP-TO-DATE
[2022-06-04T10:26:56.001Z] > Task 
:connect:api:generateMetadataFileForMavenJavaPublication
[2022-06-04T10:26:56.001Z] > Task :connect:json:copyDependantLibs UP-TO-DATE
[2022-06-04T10:26:56.001Z] > Task :connect:json:jar UP-TO-DATE
[2022-06-04T10:26:56.001Z] > Task 
:connect:json:generateMetadataFileForMavenJavaPublication
[2022-06-04T10:26:56.001Z] > Task :connect:api:javadocJar
[2022-06-04T10:26:56.001Z] > Task :connect:api:compileTestJava UP-TO-DATE
[2022-06-04T10:26:56.001Z] > Task :connect:api:testClasses UP-TO-DATE
[2022-06-04T10:26:56.001Z] > Task 
:connect:json:publishMavenJavaPublicationToMavenLocal
[2022-06-04T10:26:56.001Z] > Task :connect:json:publishToMavenLocal
[2022-06-04T10:26:56.001Z] > Task :connect:api:testJar
[2022-06-04T10:26:56.001Z] > Task :connect:api:testSrcJar
[2022-06-04T10:26:56.001Z] > Task 
:connect:api:publishMavenJavaPublicationToMavenLocal
[2022-06-04T10:26:56.001Z] > Task :connect:api:publishToMavenLocal
[2022-06-04T10:26:59.752Z] 
[2022-06-04T10:26:59.752Z] > Task :streams:javadoc
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/TopologyConfig.java:58:
 warning - Tag @link: missing '#': "org.apache.kafka.streams.StreamsBuilder()"
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/TopologyConfig.java:58:
 warning - Tag @link: can't find org.apache.kafka.streams.StreamsBuilder() in 
org.apache.kafka.streams.TopologyConfig
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/Position.java:44:
 warning - Tag @link: can't find query(Query,
[2022-06-04T10:26:59.752Z]  PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:44:
 warning - Tag @link: can't find query(Query, PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:36:
 warning - Tag @link: can't find query(Query, PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:57:
 warning - Tag @link: can't find query(Query, PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:74:
 warning - Tag @link: can't find query(Query, PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:110:
 warning - Tag @link: reference not found: this#getResult()
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:117:
 warning - Tag @link: reference not found: this#getFailureReason()
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:117:
 warning - Tag @link: reference not found: this#getFailureMessage()
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:155:
 warning - Tag @link: reference not found: this#isSuccess()
[2022-06-04T10:26:59.752Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:155:
 warning - Tag @link: reference not found: this#isFailure()
[2022-06-04T10:26:59.752Z] 12 warnings
[2022-06-04T10:27:00.689Z] 
[2022-06-04T10:27:00.689Z] > Task :streams:javadocJar
[2022-06-04T10:27:00.689Z] 
[2022-06-04T10:27:00.689Z] > Task :clients:javadoc
[2022-06-04T10:27:00.689Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_3.2/clients/src/main/java/org/apache/kafka/common/security/oauthbearer/secured/OAuthBearerLoginCallbackHandler.java:147:
 warning - Tag @link: reference not found: 
[2022-06-04T10:27:00.689Z] 1 warning
[2022-06-04T10:27:01.626Z] 
[2022-06-04T10:27:01.626Z] > Task :clients:javadocJar
[2022-06-04T10:27:02.564Z] 
[2022-06-04T10:27:02.564Z] > Task :clients:srcJar
[2022-06-04

Re: [DISCUSS] KIP-846: Task-level Streams metrics for bytes/records Produced

[Luke Chen]

Hi Sophie,

Sorry for the late comments.
Thanks for the KIP.

One question from me:
In test plan section, you mentioned we'll have benchmark for potential
performance regression.
And in the end, you said:

See #2 under Rejected Alternatives for more on this.

But I didn't find there's #2 in Rejected Alternatives section. I'm curious
about it.
Did you forget to put it?

The KIP overall LGTM, as long as we won't create performance regression to
it.
Sorry for being late for the vote.

Thank you.
Luke

On Thu, Jun 2, 2022 at 12:28 PM Sophie Blee-Goldman
 wrote:

> Thanks Guozhang -- I'll definitely make sure we have this benchmarked with
> an eye for any regressions before it
> makes it into a release. That said, if it's any comfort, we use the cached
> system time and record only count and
> sum type metrics, so unlike the *-rate *metrics for example we don't have
> to make any calls to the system clock
> which I know we have found to impact performance when investigating past
> regressions.
>
> On Wed, Jun 1, 2022 at 11:07 AM Guozhang Wang  wrote:
>
> > Thanks Sophie, that makes sense. Also I agree that since we are adding it
> > at finest granularity for consumed metrics, it's better to have symmetry
> > and add produced metrics at processor-node level as well.
> >
> > Regarding the benchmarks, I think that would be critical to have before
> we
> > add in the next release, since we propose to make this INFO level,
> meaning
> > it would be on by default, and collecting per-record is a critical path.
> >
> >
> > Guozhang
> >
> > On Wed, Jun 1, 2022 at 8:04 AM Sophie Blee-Goldman
> >  wrote:
> >
> > > I just want to send out a small update -- I decided to include the "-
> > > *consumed*" metrics in the KIP alongside the
> > > *"-produced"* metrics after all, for reasons I address in the
> paragraph I
> > > added at the end of the motivation section.
> > > Please let me know if you have any questions or concerns
> > >
> > > Cheers,
> > > Sophie
> > >
> > > On Wed, Jun 1, 2022 at 1:38 AM Sophie Blee-Goldman <
> sop...@confluent.io>
> > > wrote:
> > >
> > > > Just a quick question: for filling the gap of sub-topology
> > visibilities,
> > > >> would task-level produced metrics be sufficient?
> > > >
> > > >
> > > > If I understand your question correctly, you're asking whether we
> could
> > > > just report at the task/subtopology
> > > > level since we mainly want the bytes/throughput produced by the
> > > > subtopology itself?
> > > >
> > > > Note that since we're only reporting this metric at the sink nodes,
> > it's
> > > > basically the same as a task-level metric
> > > > for any subtopology that has only one sink and only scales with the
> > > number
> > > > of output topics. If you're concerned
> > > > about a potential performance impact I would say that (a) making
> these
> > > > task-level doesn't buy us much, if anything,
> > > > and (b) we can always revisit this if our benchmarks do indeed
> reveal a
> > > > regression but for now let's not over-
> > > > optimize too much :)
> > > >
> > > > Also, the general philosophy  behind the KAfka Streams metrics thus
> far
> > > > has been to report at the finest granularity
> > > > and allow users to roll them up into whatever scope they want to
> > > aggregate
> > > > over. This KIP adopts the same approach.
> > > >
> > > > On Tue, May 31, 2022 at 12:02 PM Guozhang Wang 
> > > wrote:
> > > >
> > > >> Hi Sophie,
> > > >>
> > > >> Just a quick question: for filling the gap of sub-topology
> > visibilities,
> > > >> would task-level produced metrics be sufficient?
> > > >>
> > > >> On Mon, May 30, 2022 at 10:59 AM Bill Bejeck 
> > wrote:
> > > >>
> > > >> > Thanks for the KIP Sophie.
> > > >> >
> > > >> > I'm in favor of this change as well. I don't have any comments in
> > > >> > addition to the ones already expressed.
> > > >> >
> > > >> > -Bill
> > > >> >
> > > >> > On Mon, May 30, 2022 at 4:55 AM Sagar 
> > > >> wrote:
> > > >> >
> > > >> > > Hi Sophie,
> > > >> > >
> > > >> > > A very minor comment but you might want to remove this KIP
> > template
> > > >> > related
> > > >> > > information from the top of the KIP:
> > > >> > >
> > > >> > > *This page is meant as a template for writing a KIP
> > > >> > > <
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > >> > > >.
> > > >> > > To create a KIP choose Tools->Copy on this page and modify with
> > your
> > > >> > > content and replace the heading with the next KIP number and a
> > > >> > description
> > > >> > > of your issue. Replace anything in italics with your own
> > > description.*
> > > >> > >
> > > >> > >
> > > >> > > Thanks!
> > > >> > > Sagar.
> > > >> > >
> > > >> > > On Mon, May 30, 2022 at 1:04 PM Sophie Blee-Goldman
> > > >> > >  wrote:
> > > >> > >
> > > >> > > > >
> > > >> > > > > Why does the title of the KIP talk about task-level metrics,
> > but
> > > >> the
> > > >> > > > > specified metrics are on processor-l

[jira] [Resolved] (KAFKA-9948) Gradle Issue

[Dulvin Witharane (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dulvin Witharane resolved KAFKA-9948.
-
Resolution: Not A Bug

> Gradle Issue
> 
>
> Key: KAFKA-9948
> URL: https://issues.apache.org/jira/browse/KAFKA-9948
> Project: Kafka
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.4.1
> Environment: gradle -v
> 
> Gradle 6.0.1
> 
> Build time:   2019-11-18 20:25:01 UTC
> Revision: fad121066a68c4701acd362daf4287a7c309a0f5
> Kotlin:   1.3.50
> Groovy:   2.5.8
> Ant:  Apache Ant(TM) version 1.10.7 compiled on September 1 2019
> JVM:  1.8.0_152 (Oracle Corporation 25.152-b16)
> OS:   Mac OS X 10.15.4 x86_64
>Reporter: Dulvin Witharane
>Priority: Blocker
>
> Can't get Gradle to build kafka.
>  
> Build file '/Users/dulvin/Documents/Work/git/kafka/build.gradle' line: 457
> A problem occurred evaluating root project 'kafka'.
> > Could not create task ':clients:spotbugsMain'.
>  > Could not create task of type 'SpotBugsTask'.
>  > Could not create an instance of type 
> com.github.spotbugs.internal.SpotBugsReportsImpl.
>  > 
> org.gradle.api.reporting.internal.TaskReportContainer.(Ljava/lang/Class;Lorg/gradle/api/Task;)V
>  
> The above error is thrown



--
This message was sent by Atlassian Jira
(v8.20.7#820007)