Skip to content

Impl/cherry picks #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: 2.10_ds
Choose a base branch
from
Open

Impl/cherry picks #90

wants to merge 2 commits into from

Conversation

eolivelli
Copy link
Collaborator

No description provided.

BewareMyPower and others added 2 commits June 6, 2023 15:46
https://github.com/apache/kafka/blob/61530d68ce83467de6190a52da37b3c0af84f0ef/core/src/main/scala/kafka/server/KafkaApis.scala#L1203-L1210

When a topic is not found, Kafka only returns `INVALID_TOPIC_EXCEPTION`
when the topic name is invalid. If the topic name is valid,
`UNKNOWN_TOPIC_OR_PARTITION` will be returned.

- Refactor `getPartitionedTopicMetadataAsync` to return the correct
error code (and rename this method). For the case when any error happens
at the broker side, return `UNKNOWN_TOPIC_OR_PARTITION`.
- Do not print error logs when the topic is not found. Kafka also does
not print the logs. The Kafka client will print the logs for
`UNKNOWN_TOPIC_OR_PARTITION`.
- Add `testTopicMetadataNotFound` to verify the changes.

(cherry picked from commit 4c22dfa)
### Motivation

When using pulsar format and has messages In batch,
we should use single message metadata's event time as the record
timestamp.

### Modifications

Use single message metadata's event time as the record timestamp

(cherry picked from commit 539af59)
@codecov-commenter
Copy link

Codecov Report

Merging #90 (9a0a274) into 2.10_ds (997d479) will increase coverage by 54.46%.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff               @@
##             2.10_ds      #90       +/-   ##
==============================================
+ Coverage           0   54.46%   +54.46%     
- Complexity         0      118      +118     
==============================================
  Files              0       19       +19     
  Lines              0      940      +940     
  Branches           0       80       +80     
==============================================
+ Hits               0      512      +512     
- Misses             0      411      +411     
- Partials           0       17       +17     

see 19 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants