Skip to content
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

[fix] [broker] response not-found error if topic does not exist when calling getPartitionedTopicMetadata #22838

Merged
merged 20 commits into from
Jun 17, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix tests
  • Loading branch information
poorbarcode committed Jun 11, 2024
commit 3e061cc53c79fe62f1aa5681aec82e502b10b06b
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,10 @@ public void testValidateReplicationSettingsOnNamespace() throws Exception {
CompletableFuture<TopicExistsInfo> future = new CompletableFuture<>();
future.complete(TopicExistsInfo.notExists());
doReturn(future).when(namespaceService).checkTopicExists(any(TopicName.class));
doReturn(future).when(namespaceService).checkTopicExists(any(TopicName.class), anyBoolean());
CompletableFuture<Boolean> booleanFuture = new CompletableFuture<>();
booleanFuture.complete(false);
doReturn(future).when(namespaceService).checkNonPartitionedTopicExists(any(TopicName.class), anyBoolean());
destLookup.lookupTopicAsync(asyncResponse, TopicDomain.persistent.value(), property, cluster, ns2,
"invalid-localCluster", false, null, null);
verify(asyncResponse).resume(arg.capture());
Expand Down
Loading