Use DataChangedEventHandler to instead of DispatchEventBuilder

apache · Dec 31, 2024 · 5fc4a7c · 5fc4a7c
1 parent 074e5f5
commit 5fc4a7c
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...re/mode/manager/cluster/event/dispatch/listener/DataChangedEventListenerRegistryTest.java b/...re/mode/manager/cluster/event/dispatch/listener/DataChangedEventListenerRegistryTest.java
@@ -19,7 +19,7 @@
 
 import org.apache.shardingsphere.mode.manager.ContextManager;
 import org.apache.shardingsphere.mode.manager.cluster.event.dispatch.listener.type.DatabaseMetaDataChangedListener;
-import org.apache.shardingsphere.mode.manager.cluster.event.dispatch.listener.type.GlobalMetaDataChangedListener;
+import org.apache.shardingsphere.mode.manager.cluster.event.dispatch.listener.type.GlobalMetaDataChangedHandler;
 import org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepository;
 import org.junit.jupiter.api.Test;
 
@@ -44,6 +44,6 @@ void assertRegister() {
         DataChangedEventListenerRegistry registry = new DataChangedEventListenerRegistry(contextManager, Collections.singleton("foo_db"));
         registry.register();
         verify(repository).watch(eq("/metadata/foo_db"), any(DatabaseMetaDataChangedListener.class));
-        verify(repository, atLeastOnce()).watch(anyString(), any(GlobalMetaDataChangedListener.class));
+        verify(repository, atLeastOnce()).watch(anyString(), any(GlobalMetaDataChangedHandler.class));
     }
 }