Skip to content

KAFKA-13255: use exclude filter for new topics #11401

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.

Sign up for GitHub

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

Merged
mimaison merged 7 commits into from
Nov 15, 2021
Merged

KAFKA-13255: use exclude filter for new topics #11401

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
6a4cffc
KAFKA-13255: use exclude filter for new topics
bdesert Oct 14, 2021
57cfc24
KAFKA-13255: add test for property exclude filter
bdesert Oct 29, 2021
b9d415d
adding exclude topic config integrated test
bdesert Oct 29, 2021
75ff17c
adding exclude topic config unit test test
bdesert Nov 3, 2021
3d87dff
adding exclude topic config unit test test
bdesert Nov 4, 2021
2d52d51
integration test updates include simplification and order change sugg…
bdesert Nov 8, 2021
3ba6d6c
integration test fix for IdentityReplication and optimizing the test …
bdesert Nov 9, 2021
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
2 changes: 1 addition & 1 deletion connect/mirror/src/main/java/org/apache/kafka/connect/mirror/MirrorSourceConnector.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -356,7 +356,7 @@ private void createNewTopics(Set<String> newSourceTopics, Map<String, Long> sour
.map(sourceTopic -> {
String remoteTopic = formatRemoteTopic(sourceTopic);
int partitionCount = sourceTopicToPartitionCounts.get(sourceTopic).intValue();
Map<String, String> configs = configToMap(sourceTopicToConfig.get(sourceTopic));
Map<String, String> configs = configToMap(targetConfig(sourceTopicToConfig.get(sourceTopic)));
return new NewTopic(remoteTopic, partitionCount, (short) replicationFactor)
.configs(configs);
})
Expand Down
38 changes: 38 additions & 0 deletions connect/mirror/src/test/java/org/apache/kafka/connect/mirror/MirrorSourceConnectorTest.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,6 +152,44 @@ public void testConfigPropertyFiltering() {
.anyMatch(x -> x.name().equals("min.insync.replicas")), "should not replicate excluded properties");
}

@Test
public void testConfigPropertyFilteringExclude() {

@mimaison mimaison Oct 29, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even without the code change, this test is passing. It's because it's calling connector.targetConfig() while the fix is in createNewTopics().

@bdesert bdesert Oct 29, 2021 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mimaison, thanks for the comments. Makes perfect sense.
I'm adding integration test to address your suggestion.
Along with that, i'm still keeping the unitTest committed before, so it will test configuration filtering logic without integration. The method I've added to unitTest follows the suit of the very previous test testConfigPropertyFiltering, which tests default exclude list this particular way.


Map<String, Object> mmConfig = new HashMap<>();
mmConfig.put(DefaultConfigPropertyFilter.CONFIG_PROPERTIES_EXCLUDE_CONFIG, "follower\\.replication\\.throttled\\.replicas, "
+ "leader\\.replication\\.throttled\\.replicas, "
+ "message\\.timestamp\\.difference\\.max\\.ms, "
+ "message\\.timestamp\\.type, "
+ "unclean\\.leader\\.election\\.enable, "
+ "min\\.insync\\.replicas,"
+ "exclude_param.*");

DefaultConfigPropertyFilter filter = new DefaultConfigPropertyFilter();
filter.configure(mmConfig);

MirrorSourceConnector connector = new MirrorSourceConnector(new SourceAndTarget("source", "target"),
new DefaultReplicationPolicy(), x -> true, filter);
ArrayList<ConfigEntry> entries = new ArrayList<>();
entries.add(new ConfigEntry("name-1", "value-1"));
entries.add(new ConfigEntry("exclude_param.param1", "value-param1"));
entries.add(new ConfigEntry("min.insync.replicas", "2"));
Config config = new Config(entries);
Config targetConfig = connector.targetConfig(config);

// property 'name-1' isn't defined in the exclude filter -> should be replicated
assertTrue(targetConfig.entries().stream().anyMatch(x -> x.name().equals("name-1")),
"should replicate properties");

// this property is in default list, just double check it:
String prop1 = "min.insync.replicas";
assertFalse(targetConfig.entries().stream().anyMatch(x -> x.name().equals(prop1)),
"should not replicate excluded properties " + prop1);
// this property is only in exclude filter custom parameter, also tests regex on the way:
String prop2 = "exclude_param.param1";
assertFalse(targetConfig.entries().stream().anyMatch(x -> x.name().equals(prop2)),
"should not replicate excluded properties " + prop2);
}

@mimaison mimaison Nov 4, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that calling verify on targetConfig() is not the best. But I think we should call verify on createNewTopics(any()) to ensure our mocked method, and the assertions, actually run.

@bdesert bdesert Nov 4, 2021

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree. with a small correction of createNewTopics(any(), any()). since the targetConfig() is being called from overloaded method with two params.

@mimaison mimaison Nov 8, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, the code we changed is actually in createNewTopics(any(), any()). As we explicitly call that method ourselves, I don't think the verify call adds a lot of value. But I think it's fine, it shouldn't hurt


@Test
public void testMirrorSourceConnectorTaskConfig() {
List<TopicPartition> knownSourceTopicPartitions = new ArrayList<>();
Expand Down