@@ -41,6 +41,22 @@ datastax-java-driver {
4141 # connecting to lower-version nodes later. You should force the lowest common protocol version
4242 # in that case.
4343 // version = V4
44+
45+ # The maximum length of the frames supported by the driver. Beyond that limit, requests will
46+ # fail with an exception
47+ #
48+ # This option can be changed at runtime, the new value will be used for new connections created
49+ # after the change.
50+ max-frame-length = 256 MB
51+
52+ # The components that handles authentication on each new connection.
53+ auth-provider {
54+ # This property is optional; if it is not present, no authentication will occur.
55+ // class = com.datastax.driver.api.core.auth.PlainTextAuthProvider
56+ # Sample configuration for the plain-text provider:
57+ // username = cassandra
58+ // password = cassandra
59+ }
4460 }
4561
4662 # A name that uniquely identifies the driver instance created from this configuration. This is
@@ -58,18 +74,10 @@ datastax-java-driver {
5874 # To disable periodic reloading, set this to 0.
5975 config-reload-interval = 5 minutes
6076
61- retry-policy {
62- class = com.datastax.oss.driver.api.core.retry.DefaultRetryPolicy
63- }
64-
6577 load-balancing-policy {
6678 class = com.datastax.oss.driver.api.core.loadbalancing.RoundRobinLoadBalancingPolicy
6779 }
6880
69- speculative-execution-policy {
70- class = com.datastax.oss.driver.api.core.specex.NoSpeculativeExecutionPolicy
71- }
72-
7381 connection {
7482 # The timeout to use for internal queries that run as part of the initialization process, just
7583 # after we open a connection. If this timeout fires, the initialization of the connection will
@@ -125,12 +133,6 @@ datastax-java-driver {
125133 # issued after the change.
126134 timeout = ${datastax-java-driver.connection.init-query-timeout}
127135 }
128- # The maximum length of the frames supported by the driver. Beyond that limit, requests will
129- # fail with an exception
130- #
131- # This option can be changed at runtime, the new value will be used for new connections created
132- # after the change.
133- max-frame-length = 256 MB
134136
135137 reconnection-policy {
136138 class = com.datastax.oss.driver.api.core.connection.ExponentialReconnectionPolicy
@@ -157,6 +159,21 @@ datastax-java-driver {
157159 # The reschedule interval.
158160 reschedule-interval = 10 microseconds
159161 }
162+
163+ # The driver maintains a connection pool to each node, according to the distance assigned to it
164+ # by the load balancing policy. If the distance is IGNORED, no connections are maintained.
165+ pool {
166+ local {
167+ # The number of connections in the pool.
168+ #
169+ # This option can be changed at runtime; when the change is detected, all active pools will
170+ # adjust their size.
171+ size = 1
172+ }
173+ remote {
174+ size = 1
175+ }
176+ }
160177 }
161178
162179 request {
@@ -213,36 +230,44 @@ datastax-java-driver {
213230 # This option can be changed at runtime, the new value will be used for requests issued after
214231 # the change. It can be overridden in a profile.
215232 default-idempotence = false
216- }
217233
218- # The generator that assigns a microsecond timestamp to each query sent by the driver.
219- timestamp-generator {
220- # The implementation to use. Built-in options are (all from the package
221- # com.datastax.oss.driver.api.core.time):
222- # - AtomicTimestampGenerator: timestamps are guaranteed to be unique across all client threads.
223- # - ThreadLocalTimestampGenerator: timestamps that are guaranteed to be unique within each
224- # thread only.
225- # - ServerSideTimestampGenerator: do not generate timestamps, let the server assign them.
226- class = com.datastax.oss.driver.api.core.time.AtomicTimestampGenerator
227-
228- # To guarantee that queries are applied on the server in the same order as the client issued
229- # them, timestamps must be strictly increasing. But this means that, if the driver sends more
230- # than one query per microsecond, timestamps will drift in the future. While this could happen
231- # occasionally under high load, it should not be a regular occurrence. Therefore the built-in
232- # implementations log a warning to detect potential issues.
233- drift-warning {
234- # How far in the future timestamps are allowed to drift before the warning is logged.
235- # If it is undefined or set to 0, warnings are disabled.
236- threshold = 1 second
237- # How often the warning will be logged if timestamps keep drifting above the threshold.
238- interval = 10 seconds
234+ # The generator that assigns a microsecond timestamp to each request.
235+ timestamp-generator {
236+ # The implementation to use. Built-in options are (all from the package
237+ # com.datastax.oss.driver.api.core.time):
238+ # - AtomicTimestampGenerator: timestamps are guaranteed to be unique across all client threads.
239+ # - ThreadLocalTimestampGenerator: timestamps that are guaranteed to be unique within each
240+ # thread only.
241+ # - ServerSideTimestampGenerator: do not generate timestamps, let the server assign them.
242+ class = com.datastax.oss.driver.api.core.time.AtomicTimestampGenerator
243+
244+ # To guarantee that queries are applied on the server in the same order as the client issued
245+ # them, timestamps must be strictly increasing. But this means that, if the driver sends more
246+ # than one query per microsecond, timestamps will drift in the future. While this could happen
247+ # occasionally under high load, it should not be a regular occurrence. Therefore the built-in
248+ # implementations log a warning to detect potential issues.
249+ drift-warning {
250+ # How far in the future timestamps are allowed to drift before the warning is logged.
251+ # If it is undefined or set to 0, warnings are disabled.
252+ threshold = 1 second
253+ # How often the warning will be logged if timestamps keep drifting above the threshold.
254+ interval = 10 seconds
255+ }
256+
257+ # Whether to force the driver to use Java's millisecond-precision system clock.
258+ # If this is false, the driver will try to access the microsecond-precision OS clock via native
259+ # calls (and fallback to the Java one if the native calls fail).
260+ # Unless you explicitly want to avoid native calls, there's no reason to change this.
261+ force-java-clock = false
262+ }
263+
264+ retry-policy {
265+ class = com.datastax.oss.driver.api.core.retry.DefaultRetryPolicy
239266 }
240267
241- # Whether to force the driver to use Java's millisecond-precision system clock.
242- # If this is false, the driver will try to access the microsecond-precision OS clock via native
243- # calls (and fallback to the Java one if the native calls fail).
244- # Unless you explicitly want to avoid native calls, there's no reason to change this.
245- force-java-clock = false
268+ speculative-execution-policy {
269+ class = com.datastax.oss.driver.api.core.specex.NoSpeculativeExecutionPolicy
270+ }
246271 }
247272
248273 prepared-statements {
@@ -308,21 +333,6 @@ datastax-java-driver {
308333 }
309334 }
310335
311- # The driver maintains a connection pool to each node, according to the distance assigned to it
312- # by the load balancing policy. If the distance is IGNORED, no connections are maintained.
313- pooling {
314- local {
315- # The number of connections in the pool.
316- #
317- # This option can be changed at runtime; when the change is detected, all active pools will
318- # adjust their size.
319- connections = 1
320- }
321- remote {
322- connections = 1
323- }
324- }
325-
326336 metadata {
327337 # Topology events are external signals that inform the driver of the state of Cassandra nodes
328338 # (by default, they correspond to gossip events received on the control connection).
@@ -340,6 +350,7 @@ datastax-java-driver {
340350 max-events = 20
341351 }
342352 }
353+
343354 # The address translator to use to convert the addresses sent by Cassandra nodes into ones that
344355 # the driver uses to connect.
345356 # This is only needed if the nodes are not directly reachable from the driver (for example, the
@@ -349,14 +360,7 @@ datastax-java-driver {
349360 # This default implementation always returns the same address unchanged.
350361 class = com.datastax.oss.driver.api.core.addresstranslation.PassThroughAddressTranslator
351362 }
352- # The auth provider that will handle authentication for each new connection to a server.
353- auth-provider {
354- # This property is optional; if it is not present, no authentication will occur.
355- // class = com.datastax.driver.api.core.auth.PlainTextAuthProvider
356- # Sample configuration for the plain-text provider:
357- // username = cassandra
358- // password = cassandra
359- }
363+
360364 # The SSL engine factory that will initialize an SSL engine for each new connection to a server.
361365 ssl-engine-factory {
362366 # This property is optional; if it is not present, SSL won't be activated.
0 commit comments