DATACASS-656 - Disable schema debouncer.

Allows running tests much faster as we no longer use the debouncer.

spring-data-cassandra/src/test/resources/application.conf

@@ -155,4 +155,80 @@ datastax-java-driver {
       shutdown {quiet-period = 0, timeout = 0, unit = SECONDS}
     }
   }
+
+  advanced.metadata {
+    # Topology events are external signals that inform the driver of the state of Cassandra nodes
+    # (by default, they correspond to gossip events received on the control connection).
+    # The debouncer helps smoothen out oscillations if conflicting events are sent out in short
+    # bursts.
+    # Debouncing may be disabled by setting the window to 0 or max-events to 1 (this is not
+    # recommended).
+    topology-event-debouncer {
+      # How long the driver waits to propagate an event. If another event is received within that
+      # time, the window is reset and a batch of accumulated events will be delivered.
+      #
+      # Required: yes
+      # Modifiable at runtime: no
+      # Overridable in a profile: no
+      window = 0 second
+
+      # The maximum number of events that can accumulate. If this count is reached, the events are
+      # delivered immediately and the time window is reset. This avoids holding events indefinitely
+      # if the window keeps getting reset.
+      #
+      # Required: yes
+      # Modifiable at runtime: no
+      # Overridable in a profile: no
+      max-events = 20
+    }
+
+    # Options relating to schema metadata (Cluster.getMetadata.getKeyspaces).
+    # This metadata is exposed by the driver for informational purposes, and is also necessary for
+    # token-aware routing.
+    schema {
+      # Whether schema metadata is enabled.
+      # If this is false, the schema will remain empty, or to the last known value.
+      #
+      # Required: yes
+      # Modifiable at runtime: yes, the new value will be used for refreshes issued after the
+      #   change. It can also be overridden programmatically via Cluster.setSchemaMetadataEnabled.
+      # Overridable in a profile: no
+      enabled = true
+
+      # Protects against bursts of schema updates (for example when a client issues a sequence of
+      # DDL queries), by coalescing them into a single update.
+      # Debouncing may be disabled by setting the window to 0 or max-events to 1 (this is highly
+      # discouraged for schema refreshes).
+      debouncer {
+        # How long the driver waits to apply a refresh. If another refresh is requested within that
+        # time, the window is reset and a single refresh will be triggered when it ends.
+        #
+        # Required: yes
+        # Modifiable at runtime: no
+        # Overridable in a profile: no
+        window = 0 second
+
+        # The maximum number of refreshes that can accumulate. If this count is reached, a refresh
+        # is done immediately and the window is reset.
+        #
+        # Required: yes
+        # Modifiable at runtime: no
+        # Overridable in a profile: no
+        max-events = 20
+      }
+    }
+
+    # Whether token metadata (Cluster.getMetadata.getTokenMap) is enabled.
+    # This metadata is exposed by the driver for informational purposes, and is also necessary for
+    # token-aware routing.
+    # If this is false, it will remain empty, or to the last known value. Note that its computation
+    # requires information about the schema; therefore if schema metadata is disabled or filtered to
+    # a subset of keyspaces, the token map will be incomplete, regardless of the value of this
+    # property.
+    #
+    # Required: yes
+    # Modifiable at runtime: yes, the new value will be used for refreshes issued after the change.
+    # Overridable in a profile: no
+    token-map.enabled = true
+  }
 }