symmetric-default.properties

#
# Licensed to JumpMind Inc under one or more contributor
# license agreements.  See the NOTICE file distributed
# with this work for additional information regarding
# copyright ownership.  JumpMind Inc licenses this file
# to you under the GNU General Public License, version 3.0 (GPLv3)
# (the "License"); you may not use this file except in compliance
# with the License.
#
# You should have received a copy of the GNU General Public License,
# version 3.0 (GPLv3) along with this library; if not, see
# <http://www.gnu.org/licenses/>.
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.
#

# This is the engine name.  This should be set if you have more than one engine running in the same JVM.
# It is used to name the JMX management bean.  Please do not use underscores in this name.
#
# Tags: general
engine.name=SymmetricDS

# The node group id that this node belongs to
# Tags: init
group.id=please set me

# The external id for this SymmetricDS node.  The external id is
# usually used as all or part of the node id.
# Tags: init
external.id=please set me

# This is the URL this node will use to register and pull it's configuration.
# If this is the root server, then this may remain blank and the configuration
# should be inserted directly into the database
# Tags: init
registration.url=please set me

# The url that can be used to access this SymmetricDS node.
# The default setting of http://$(hostName):31415/sync should be
# valid of the standalone launcher is used with the default settings
# The tokens of $(hostName) and $(ipAddress) are supported for this property.
# Tags: init
sync.url=http://$(hostName):31415/sync/$(engineName)

# Specify your database driver
# Tags: database
db.driver=org.h2.Driver
#db.driver=org.h2.Driver
#db.driver=com.mysql.jdbc.Driver
#db.driver=oracle.jdbc.driver.OracleDriver
#db.driver=org.postgresql.Driver
#db.driver=org.apache.derby.jdbc.EmbeddedDriver
#db.driver=org.hsqldb.jdbcDriver
#db.driver=net.sourceforge.jtds.jdbc.Driver
#db.driver=com.ibm.db2.jcc.DB2Driver
#db.driver=org.sqlite.JDBC
#db.driver=org.firebirdsql.jdbc.FBDriver
#db.driver=com.sybase.jdbc4.jdbc.SybDriver

# Specify your database URL
# Tags: database
db.url=jdbc:h2:mem:setme
#db.url=jdbc:h2:file:target/h2/client
#db.url=jdbc:oracle:thin:@127.0.0.1:1521:sampleroot
#db.url=jdbc:postgresql://localhost/sampleroot
#db.url=jdbc:derby:sampleroot;create=true
#db.url=jdbc:hsqldb:file:sampleroot;shutdown=true
#db.url=jdbc:jtds:sqlserver://localhost:1433;sendStringParametersAsUnicode=false;useCursors=true;bufferMaxMemory=10240;lobBuffer=5242880
#db.url=jdbc:db2://localhost/samproot
#db.url=jdbc:mysql://localhost/sampleroot?tinyInt1isBit=false&zeroDateTimeBehavior=convertToNull
#db.url=jdbc:sqlite:target/sqlite/client
#db.url=jdbc:firebirdsql://host[:port]/client
#db.url=jdbc:sybase:Tds:localhost:5000/client

# Specify your database user
# Tags: database
db.user=please set me

# Specify your database password
# Tags: database
db.password=

# The initial size of the connection pool
# Tags: database
db.pool.initial.size=5

# The maximum number of connections that will be allocated in the pool
# The http.concurrent.workers.max value should be half or less than half of
# this value.
# Tags: database
db.pool.max.active=40

# The maximum number of connections that can remain idle in the pool, without extra ones
# being released
# Tags: database
db.pool.max.idle=20

# The minimum number of connections that can remain idle in the pool, without extra ones
# being created
# Tags: database
db.pool.min.idle=5

# This is the query to validate the database connection in Connection Pool.
# It is database specific.  The following are example statements for different databases.
#
# MySQL
#  db.validation.query=select 1
# Oracle
#  db.validation.query=select 1 from dual
# DB2
#  db.validation.query=select max(1) from syscat.datatypes
# Tags: database
db.validation.query=

# These are settings that will be passed to the JDBC driver as connection properties.
# Suggested settings by database are as follows:
# Oracle
#
#  db.connection.properties=oracle.net.CONNECT_TIMEOUT=300000;oracle.jdbc.ReadTimeout=300000;SetBigStringTryClob=true
# Tags: database
db.connection.properties=

# Specify a SQL statement that will be run when a database connection is created
#
# Tags: database
db.init.sql=

# When symmetric tables are created and accessed, this is the prefix to use for the tables.
#
# Tags: database
sync.table.prefix=sym

# Most symmetric queries have a timeout associated with them.  This is the default.
# Tags: database
db.sql.query.timeout.seconds=300

# Override the JDBC isolation level.  The isolation level is detected by platform and automatically set,
# but it can be overridden here.  Most platforms need at least read committed level to prevent
# phantom reads. 
# (0=none, 1=read uncommitted, 2=read committed, 4=repeatable read, 8=serializable)
#
# Tags: database
db.jdbc.isolation.level=

# If set to true forces database columns that contain character data to be read as bytes (bypassing JDBC driver character encoding) 
# so the raw values be encoded using the system default character set (usually UTF8).  This property was added to bypass MySQL character
# encoding so the raw data can be converted to utf8 directly.
#
# Tags: database
# Type: boolean
db.read.strings.as.bytes=false

# Name of class that can extract native JDBC objects and interact directly with the driver.
# Spring uses this to perform operations specific to database, like handling LOBs on Oracle.
#
# Tags: database
db.native.extractor=org.springframework.jdbc.support.nativejdbc.CommonsDbcpNativeJdbcExtractor

# This is how long a request for a connection from the datasource will wait before
# giving up.
#
# Tags: database
db.pool.max.wait.millis=30000

# This is how long a connection can be idle before it will be evicted.
# Tags: database
db.pool.min.evictable.idle.millis=120000

# This is the default fetch size for streaming result sets.
#
# Tags: database
db.jdbc.streaming.results.fetch.size=100

# This is the default number of rows that will be sent to the database as a batch when
# SymmetricDS uses the JDBC batch API.  Currently, only routing uses JDBC batch.  The
# data loader does not.
#
# Tags: database,routing
db.jdbc.execute.batch.size=100

# This override any database specific bulk loader if the channel data loader algorithm
# is set to bulk and a specific bulk loader is available.  For example is a PostgreSQL
# database is setup for bulk loading and this parameter is true the JdbcBatchBulkDatabaseWriter
# will be used instead of the PostgreSQL bulk loader.  If a dialect does not have a designated
# bulk loader and the channel is set for bulk loading this will be used automatically even if the 
# the parameter is false.  Essentially the parameter only controls "overriding" a dialect specific
# bulk loader.
#
# Tags: database,load
# Type: boolean
db.jdbc.bulk.execute.batch.override=false

# This is the default number of rows that will be sent to the database as a batch when
# SymmetricDS uses the JDBC batch API for bulk data load types.  Designed for loads that are setup 
# with a channel data loader algorithm of batch. 
#
# Tags: database,load
db.jdbc.bulk.execute.batch.size=25

# Indicates that case should be ignored when looking up references to tables using the database's metadata api.
#
# Tags: database
# Type: boolean
db.metadata.ignore.case=true

# Determines whether delimited identifiers are used or normal SQL92
# identifiers (which may only contain alphanumerical characters and the
# underscore, must start with a letter and cannot be a reserved keyword).
#
# Tags: database
# Type: boolean
db.delimited.identifier.mode=true

# Name of a JNDI data source to use instead of using SymmetricDS's connection pool.  When
# this is set the db.url is ignored.  Using a JNDI data source is relevant when deploying
# to an application server.
#
# Tags: database
db.jndi.name=

# This is the number of HTTP concurrent push/pull requests SymmetricDS will accept.  This is controlled
# by the NodeConcurrencyFilter. The number is per servlet the filter is applied to.  The
# db.pool.max.active value should be twice this value.
#
# DatabaseOverridable: true
# Tags: transport
http.concurrent.workers.max=20

# This is the amount of time the host will keep a concurrent connection reservation after it has
# been attained by a client node while waiting for the subsequent reconnect to push.
# Tags: transport
http.concurrent.reservation.timeout.ms=20000

# During SSL handshaking, if the URL's hostname and the server's
# identification hostname mismatch, the verification mechanism
# will check this comma separated list of server names to see if the
# cert should be accepted (see javax.net.ssl.HostnameVerifier.)
# Set this value equal to 'all' if all server names should be accepted.
# Set this value to blank if a valid SSL cert is required.
# Tags: transport
# DatabaseOverridable: true
https.verified.server.names=

# Save data to the file system before transporting it to the client or loading
# it to the database if the number of bytes is past a certain threshold.  This allows
# for better compression and better use of database and network resources.  Statistics
# in the batch tables will be more accurate if this is set to true because each timed
# operation is independent of the others.
#
# Tags: transport
# Type: boolean
stream.to.file.enabled=true

# If stream.to.file.enabled is true, then the threshold number of bytes at which a file
# will be written is controlled by this property.  Note that for a synchronization the
# entire payload of the synchronization will be buffered in memory up to this number (at
# which point it will be written and continue to stream to disk.)
#
# DatabaseOverridable: true
# Tags: transport
stream.to.file.threshold.bytes=0

# If stream.to.file.enabled is true, then this is how long a file will be retained in the
# staging directory after it has been marked as done.
#
# DatabaseOverridable: true
# Tags: transport
stream.to.file.ttl.ms=3600000

# If stream.to.file.enabled is false and staging is purged based on the database, then this 
# is the minimum amount of time a staging file will be retained after it is purged from the 
# database
#
# DatabaseOverridable: true
# Tags: transport
stream.to.file.min.ttl.ms=1800000


# When this is set to false, then batches in the staging area will only be purged after they have been
# purged from the database.  If this is set to true, then batches will be purged based on the 
# stream.to.file.ttl.ms setting.
#
# DatabaseOverridable: true
# Tags: transport
# Type: boolean
stream.to.file.purge.on.ttl.enabled=false

# This is the number of times we will attempt to send an ACK back to the remote node
# when pulling and loading data.
#
# DatabaseOverridable: true
# Tags: transport
num.of.ack.retries=5

# After a push or pull HTTP connection has been idle for this many milliseconds, a small
# partial acknowledgement or partial batch is sent to keep the connection alive.
#
# DatabaseOverridable: true
# Tags: transport
send.ack.keepalive.ms=30000

# This is the amount of time to wait between trying to send an ACK back to the remote node
# when pulling and loading data.
#
# DatabaseOverridable: true
# Tags: transport
time.between.ack.retries.ms=5000

# Sets both the connection and read timeout on the internal HttpUrlConnection
#
# DatabaseOverridable: true
# Tags: transport
http.timeout.ms=90000

# Whether or not to use compression over HTTP connections.
# Currently, this setting only affects the push connection of the source node.
# Compression on a pull is enabled using a filter in the web.xml for the PullServlet.
# @see web.compression.disabled to enable/disable the filter
#
# DatabaseOverridable: true
# Tags: transport
# Type: boolean
http.compression=true

# The HTTP client connection, during a push, buffers the entire outgoing pay-load locally
# before sending it.  Set this to true if you are getting heap space errors during
# a push.  Note that basic auth may not work when this is turned on.
#
# DatabaseOverridable: true
# Tags: transport
# Type: boolean
http.push.stream.output.enabled=true

# When HTTP chunking is turned on, this is the size to use for each chunk.
#
# DatabaseOverridable: true
# Tags: transport
http.push.stream.output.size=30720

# Disable compression from occurring on Servlet communication.  This property only
# affects the outbound HTTP traffic streamed by the PullServlet and PushServlet.
#
# DatabaseOverridable: true
# Tags: transport
# Type: boolean
web.compression.disabled=false

# Set the compression level this node will use when compressing synchronization payloads.
# @see java.util.zip.Deflater
# NO_COMPRESSION = 0
# BEST_SPEED = 1
# BEST_COMPRESSION = 9
# DEFAULT_COMPRESSION = -1
#
# DatabaseOverridable: true
# Tags: transport
compression.level=-1

# Set the compression strategy this node will use when compressing synchronization payloads.
# @see java.util.zip.Deflater
# FILTERED = 1
# HUFFMAN_ONLY = 2
# DEFAULT_STRATEGY = 0
#
# DatabaseOverridable: true
# Tags: transport
compression.strategy=0

# Indicate whether the batch servlet (which allows specific batches to be requested) is enabled.
#
# Tags: other
# Type: boolean
web.batch.servlet.enable=true

# Specify the transport type.  Supported values currently include: http, file, internal.
#
# Tags: transport
transport.type=http

# This is the number of maximum number of bytes to synchronize in one connect.
#
# DatabaseOverridable: true
# Tags: transport
transport.max.bytes.to.sync=104857600

# Networks errors will be logged at INFO level since they are retried.
# After the maximum number of millis for network errors that continue in succession, the logging
# switches to WARN level.
#
# DatabaseOverridable: true
# Tags: transport
transport.max.error.millis=300000

# This indicates whether this node engine should be started when the instance is restarted
# 
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.start.engine=true

# If this is true, when symmetric starts up it will try to create the necessary tables.
#
# Tags: general
# Type: boolean
auto.config.database=true

# If this is true, triggers will be created or dropped to match configuration during the sync triggers process.
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.triggers=true

# Number of threads to use for creating triggers and removing old ones.
#
# DatabaseOverridable: true
# Tags: general
sync.triggers.thread.count.per.server=1

# If this is true, when a configuration change is detected during routing, 
# symmetric will make sure all triggers in the database are up to date.
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.triggers.after.config.change=true

# If this is true, when a configuration change is detected while being loaded onto a target node, 
# symmetric will make sure all triggers in the database are up to date.
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.triggers.after.config.loaded=true


# If this is true, then run the sync triggers process at startup
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.triggers.at.startup=true

# If this is true, then check if configuration should be pulled from registration server at startup.
# If the config version in the database does not match the software version, it will pull config.
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.config.at.startup=true

# If this is true, then check if configuration should be pulled from registration server after upgrading.
# If the config version in the database does not match the software version, it will pull config.
#
# Tags: general
# Type: boolean
auto.sync.config.after.upgrade=true

# Capture and send SymmetricDS configuration changes to client nodes.
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.configuration=true

# Whether triggers should fire when changes sync into the node that this property is configured for.
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
auto.sync.configuration.on.incoming=true

# Update the node row in the database from the local properties during a heartbeat operation.
#
# Tags: general
# Type: boolean
auto.update.node.values.from.properties=true

# If this is true, then node, group, security and identity rows will be inserted if the
# registration.url is blank and there is no configured node identity.
#
# Tags: general
# Type: boolean
auto.insert.registration.svr.if.not.found=true

# Provide the path to a SQL script that can be run to do initial setup of a registration server.  This script
# will only be run on a registration server if the node_identity cannot be found.
#
# Tags: general
auto.config.registration.svr.sql.script=

# This is hook to give the user a mechanism to indicate the schema version that is being synchronized.
#
# DatabaseOverridable: true
#
# Tags: other
schema.version=?

# This is the number of times registration will be attempted before being aborted.  The default
# value is -1 which means an endless number of attempts.  This parameter is specific to the node
# that is trying to register, not the node that is providing registration.
#
# DatabaseOverridable: true
# Tags: registration
registration.number.of.attempts=-1

# Indicates that if registration is reopened if the same password should be used.  If set to false
# then a new password will be generated.
#
# DatabaseOverridable: true
# Tags: registration
# Type: boolean
registration.reopen.use.same.password=true

# Indicates whether SymmetricDS should be re-initialized immediately before registration.
# When a client is successful with its registration, it will un-install its database
# objects (sym triggers, tables, and procedures), then re-install its database objects
# and load the configuration received from registration.
#
# DatabaseOverridable: true
# Tags: registration
# Type: boolean
registration.reinitialize.enable=false


# When this is set to true a node will have to have had an initial load prior to allowing other nodes to register with it
#
# DatabaseOverridable: true
# Tags: registration
# Type: boolean
registration.require.initial.load=true

# Initial load and reload events should normally block other channels to ensure each table
# is loaded first followed by changes captured during the initial load.  Setting this to false
# will allow all channels to load in priority order even when reload events or 
# an initial load is running.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.block.channels=true

# This is the number of maximum number of bytes to synchronize in one connect during an initial load.
#
# DatabaseOverridable: true
# Tags: load
initial.load.transport.max.bytes.to.sync=524288000

# Allow other channels to load when initial.load.block.channels is true and the
# reload channel goes into error.  When the initial load runs while changes are
# being made, it can lead to foreign key errors that might resolve when the other
# channels are allowed to sync.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.unblock.channels.on.error=false

# Set this if tables should be created prior to an initial load.
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.create.first=false

# Set this if tables should be purged prior to an initial load.
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.delete.first=false

# This is the SQL statement that will be used for purging a table
# during an initial load.
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
initial.load.delete.first.sql=delete from %s

# Indicate that the initial load events should be put on the reload channel.
# If this is set to false each table will be put on it's assigned channel during
# the reload.
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.use.reload.channel=true

# Indicate that if both the initial load and the reverse initial load
# are requested, then the reverse initial load should take place first.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.reverse.first=true

# Indicate that the extract job job should be used
# to extract reload batches
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.use.extract.job.enabled=true

# The number of threads available for concurrent extracts of initial load batches.
#
# DatabaseOverridable: true
# Tags: load
initial.load.extract.thread.per.server.count=20

# The number of milliseconds to wait until the lock will be broken on an initial load
# extract job.
#
# DatabaseOverridable: true
# Tags: load
initial.load.extract.timeout.ms=7200000

# Some dialects can extract small LOBs faster using a substring function.
# When the dialect supports it and the parameter is enabled, the initial load
# will extract tables with LOBs using two passes.  The first pass gets rows
# with LOBs under the character limit, and the second pass gets all other rows.
# Currently implemented for Oracle/Tibero.  
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.extract.use.two.pass.lob=true

# Indicates that the SQL used to extract data from a 
# table for an initial load should concatenate the data using 
# the same SQL expression that a trigger uses versus concatenating 
# the data in code.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.concat.csv.in.sql.enabled=false

# The initial load SQL to extract a table will wrap each column with
# a template of SQL functions to format the data using the database.
# When disabled, each column is selected directly, and data is
# formatted by the server instead.  Currently, the server can format
# string, integer, and LOB types, but other types still use templates.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.use.column.templates.enabled=false

# This is SQL that will run on the client before an initial load starts.
# The default delimiter for these lines is a semicolon.  To override, include
# a single line that starts with delimiter and is followed by the new delimiter, then the old
# For example a line that reads:
# delimiter $;
# would change sql lines to have a delimiter of $ for subsequent lines.
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
# Type: sql
initial.load.before.sql=

# This is SQL that will run on the client after an initial load finishes.
# The default delimiter for these lines is a semicolon.  To override, include
# a single line that starts with delimiter and is followed by the new delimiter, then the old
# For example a line that reads:
# delimiter $;
# would change sql lines to have a delimiter of $ for subsequent lines.
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
# Type: sql
initial.load.after.sql=

# This is SQL that will run on the server before a reverse initial load starts.
#
# DatabaseOverridable: true
# Tags: load
# Type: sql
initial.load.reverse.before.sql=

# This is SQL that will run on the server after a reverse initial load finishes.
#
# DatabaseOverridable: true
# Tags: load
# Type: sql
initial.load.reverse.after.sql=

# Specify a system command that writes the structure of
# the database to system.out to be captured and sent to the 
# node that is being initial loaded.  Used in conjunction with
# initial.load.schema.load.command. 
# An example is: pg_dump --dbname=server --schema=my_schema --schema-only --clean
#
# DatabaseOverridable: true
# Tags: load
initial.load.schema.dump.command=

# Specify a system command that will take the content captured
# by initial.load.schema.dump.command and apply it to the database.
# The content is passed to the system command via system.in.
# An example is: psql --output=output.log --dbname=client
#
# DatabaseOverridable: true
# Tags: load
initial.load.schema.load.command=

# Estimate the row count for tables to generate the number of batches needed for initial load.
# It is faster to estimate the row count than to get an actual row count. 
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.use.estimated.counts=true

# If the number of rows in the load request is greater than or equal to this threshold,
# it will immediately purge the staging file after each batch is successfully loaded.
# Set this to -1 to disable and keep the staging files. 
# 
# DatabaseOverridable: true
# Tags: load
initial.load.purge.stage.immediate.threshold.rows=5000

# If tables are created as part of the initial load, it will defer the creation
# of foreign keys and indexes to improve performance.
# After data is loaded, the constraints will be added after tables have reached consistency. 
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
# 
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.defer.create.constraints=true

# For tables with self-referencing foreign keys, the initial load will attempt to
# query each level of the rows starting with parent rows, as a way
# to preserve the order of rows.
# 
# DatabaseOverridable: true
# Tags: load
# Type: boolean
initial.load.recursion.self.fk=true

# If this is true, registration is opened automatically for nodes requesting it.
#
# DatabaseOverridable: true
# Tags: registration
# Type: boolean
auto.registration=false

# If this is true, a reload is automatically sent to nodes when they register
# This parameter needs set for the node that will send the initial load,
# not the node receiving it.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
auto.reload=false

# If this is true, a reload is automatically sent from a source node
# to all target nodes after the source node has registered.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
auto.reload.reverse=false

# If this is true, when a batch receives a foreign key violation,
# the missing data will be automatically sent to resolve it.
# The resolution is done at the source node by sending
# reload batches when it receives the acknowledgement of the batch error.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
auto.resolve.foreign.key.violation=true

# If this is true, when a batch receives a foreign key violation,
# the missing data will be automatically sent to resolve it.
# The resolution is done at the target node by sending a script
# that requests reload batches.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
auto.resolve.foreign.key.violation.reverse=false

# When resolving a foreign key violation for a batch in error
# at a node, also send the missing data to peers in a multi-master 
# configuration who may also be missing the same data.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
auto.resolve.foreign.key.violation.reverse.peers=false

# If this is true, when a reload batch receives a foreign key violation,
# the missing data will be automatically sent to resolve it.
# The resolution is done at the target node by sending a script
# that requests reload batches.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
auto.resolve.foreign.key.violation.reverse.reload=true

# Indicate whether the process of inserting data, data_events and outgoing_batches for
# a reload is transactional.  The only reason this might be marked as false is to reduce
# possible contention while multiple nodes connect for reloads at the same time.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
datareload.batch.insert.transactional=true

# Enables clustering of jobs.
#
# DatabaseOverridable: true
# Tags: jobs
# Type: boolean
cluster.lock.enabled=false


# Set this to true if you are sharing your staging directory with multiple instances of SymmetricDS
#
# DatabaseOverridable: true
# Tags: jobs
# Type: boolean
cluster.staging.enabled=false

# Set this if you want to give your server a unique name to be used to identify which server did what action.  Typically useful when running in
# a clustered environment.  This is currently used by the ClusterService when locking for a node.
#
# Tags: jobs
cluster.server.id=

# Indicate that this node is being run on a farm or cluster of servers and it needs to use the database to 'lock' out other activity when actions are taken.
#
# DatabaseOverridable: true
# Tags: jobs
cluster.lock.timeout.ms=7200000

# Period of time that certain locks will get refreshed while long processing happens.  This value should be a small fraction of cluster.lock.timeout.ms
#
# DatabaseOverridable: true
# Tags: jobs
cluster.lock.refresh.ms=1200000

# The amount of time a thread can hold a shared or exclusive lock before another thread can break the lock.
# The timeout is a safeguard in case an unexpected exception causes a lock to be abandoned.
# Restarting the service will clear all locks.
#
# DatabaseOverridable: true
# Tags: jobs
lock.timeout.ms=1800000

# While waiting for a lock to be released, how often should we check the lock status
# in the sym_lock table in the database.
#
# DatabaseOverridable: true
# Tags: jobs
lock.wait.retry.ms=10000

instance.id.location=conf/instance.uuid

# If jobs need to be synchronized so that only one job can run at a time, set this parameter to true
#
# DatabaseOverridable: true
# Tags: jobs
# Type: boolean
jobs.synchronized.enable=false

# This is how often the push job will be run to schedule pushes to nodes.
#
# DatabaseOverridable: true
# Tags: jobs
job.push.period.time.ms=60000

# If true, the push job will re-push immediately after it sends data.
#
# DatabaseOverridable: true
# Tags: jobs
push.immediate.if.data.found=true

# This is the minimum time that is allowed between pushes to a specific node.
#
# DatabaseOverridable: true
# Tags: jobs
push.period.minimum.ms=0

# This is how often the pull job will be run to schedule pulls of nodes.
#
# DatabaseOverridable: true
# Tags: jobs
job.pull.period.time.ms=60000

# If true, the pull job will re-pull immediately after it receives data.
#
# DatabaseOverridable: true
# Tags: jobs
pull.immediate.if.data.found=true

# This is the minimum time that is allowed between pulls of a specific node.
#
# DatabaseOverridable: true
# Tags: jobs
pull.period.minimum.ms=0

# This is how often accumulated statistics will be flushed out to the database from memory.
#
# DatabaseOverridable: true
# Tags: jobs
job.stat.flush.cron=0 0/5 * * * *

# This is how often a client will push its status to the root server.  Used in conjuction with hybrid.push.pull.
#
# DatabaseOverridable: true
# Tags: jobs
job.report.status.cron=0 0/5 * * * *

# This is how often the router will run in the background
#
# DatabaseOverridable: true
# Tags: jobs,routing
job.routing.period.time.ms=10000

# This is how often the heartbeat job runs.  Note that this doesn't mean that a heartbeat
# is performed this often.
# See heartbeat.sync.on.push.period.sec to change how often the heartbeat is sync'd
#
# DatabaseOverridable: true
# Tags: jobs
job.heartbeat.period.time.ms=900000

# DatabaseOverridable: true
# Tags: jobs
job.watchdog.period.time.ms=3600000

# This is how often the incoming batch purge job will be run.
#
# DatabaseOverridable: true
# Tags: jobs
job.purge.incoming.cron=0 0 */4 * * *

# This is how often the outgoing batch and data purge job will be run.
#
# DatabaseOverridable: true
# Tags: jobs
job.purge.outgoing.cron=0 0 */4 * * *

# This is when the sync triggers job will run.
#
# DatabaseOverridable: true
# Tags: jobs
job.synctriggers.cron=0 0 0 * * *

# This is when the sync config job will run.
#
# DatabaseOverridable: true
# Tags: jobs
job.sync.config.cron=0 0/10 1 * * *

# This is when the refresh cache job will run.
#
# DatabaseOverridable: true
# Tags: jobs
job.refresh.cache.cron=0/30 * * * * *

# This is when the stage management job will run.
#
# DatabaseOverridable: true
# Tags: jobs
job.stage.management.cron=0 0 * * * *

# This is how often the initial load extract queue job will run in the background
#
# DatabaseOverridable: true
# Tags: jobs
job.initial.load.extract.period.time.ms=10000

# DatabaseOverridable: true
# Tags: jobs
job.monitor.period.time.ms=60000

# This is the number of batches that will be purged from the data_event table in one database transaction.
#
# DatabaseOverridable: true
# Tags: purge, jobs
job.purge.max.num.data.event.batches.to.delete.in.tx=5

# This is the number of batches that will be purged in one database transaction.
#
# DatabaseOverridable: true
# Tags: purge, jobs
job.purge.max.num.batches.to.delete.in.tx=5000

# This is the number of data ids that will be purged in one database transaction.
#
# DatabaseOverridable: true
# Tags: purge
job.purge.max.num.data.to.delete.in.tx=5000

# Enables a first pass purge for sym_data and sym_data_event that quickly purges
# the beginning of the table that precedes outstanding batches.
# These delete statements don't use joins, so they run quicker.
#
# DatabaseOverridable: true
# Tags: purge
# Type: boolean
job.purge.first.pass=true

# The maximum number of outstanding batches allowed for running the
# first pass purge.  If there are too many outstanding batches, it will
# take too long to find their first data_id, so it shouldn't be run.
#
# DatabaseOverridable: true
# Tags: purge
job.purge.first.pass.outstanding.batches.threshold=100000

# Whether the refresh cache job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.refresh.cache.job=false

# Whether the routing job is enabled for this node.
#
# Tags: jobs,routing
# Type: boolean
start.routing.job=true

# Whether the pull job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.pull.job=true

# Whether the push job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.push.job=true

# Whether the outgoing purge job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.purge.outgoing.job=true

# Whether the incoming purge job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.purge.incoming.job=true

# Whether the heartbeat job is enabled for this node.  The heartbeat job simply
# inserts an event to update the heartbeat_time column on the node_host table for the current node.
#
# Tags: jobs
# Type: boolean
start.heartbeat.job=true

# Whether the sync triggers job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.synctriggers.job=true

# Whether the sync config job is enabled for this node.
# This job checks that the configuration version matches the software version, otherwise it
# will pull the latest configuration from the registration server.
#
# DatabaseOverridable: true
# Tags: jobs
# Type: boolean
start.sync.config.job=true

# Whether the statistic flush job is enabled for this node.
#
# Tags: jobs
start.stat.flush.job=true

# Whether the watchdog job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.watchdog.job=true

# Whether the stage management job is enabled for this node.
#
# Tags: jobs
# Type: boolean
start.stage.management.job=true

# Whether the background initial load extractor job is started.
#
# Tags: jobs
# Type: boolean
start.initial.load.extract.job=true

# Whether the monitor job is started.
#
# Tags: jobs
# Type: boolean
start.monitor.job=true

# Whether the routing job will start manually when a push or pull is started
#
# DatabaseOverridable: true
# Tags: jobs,routing
# Type: boolean
route.on.extract=false

# The number of threads created that will be used to pull nodes concurrently on one server in the cluster.
#
# DatabaseOverridable: true
# Tags: jobs
pull.thread.per.server.count=10

# The amount of time a single pull worker node_communication lock will timeout after.
#
# DatabaseOverridable: true
# Tags: jobs
pull.lock.timeout.ms=7200000

# The number of threads created that will be used to push to nodes concurrently on one server in the cluster.
#
# DatabaseOverridable: true
# Tags: jobs
push.thread.per.server.count=10

# The amount of time a single push worker node_communication lock will timeout after.
#
# DatabaseOverridable: true
# Tags: jobs
push.lock.timeout.ms=7200000

# This is the maximum number of events that will be peeked at to look for additional transaction rows after
# the max batch size is reached.  The more concurrency in your db and the longer the transaction takes the
# bigger this value might have to be.
#
# DatabaseOverridable: true
# Tags: routing
routing.peek.ahead.window.after.max.size=2000

# When reading data to route, if a lot of data has been committed in a single transaction, then
# the peek ahead queue size can cause out of memory errors.  This setting instructs the routing
# reader to disperse with all "non" active transactions if the peek ahead queue grows to be 
# a certain percentage of the overall allocated heap size.
#
# DatabaseOverridable: true
# Tags: routing
routing.peek.ahead.memory.threshold.percent=50

# DatabaseOverridable: true
# Tags: routing
routing.wait.for.data.timeout.seconds=330

# DatabaseOverridable: true
# Tags: routing
routing.flush.jdbc.batch.size=50000

# This is the number of gaps that will be included in the SQL that is used to select data
# from sym_data.  If there are more gaps than this number, then the last gap will in the SQL
# will use the end id of the last gap.
#
# DatabaseOverridable: true
# Tags: routing
routing.max.gaps.to.qualify.in.sql=100

# This is the maximum number of changes that can be applied to the data_gap table.
# If the gap detection exceeds this number of changes,
# it will record the minimal gaps to the table and keep the rest in memory.
# This setting only applies to non-clustered systems.
#
# DatabaseOverridable: true
# Tags: routing
routing.max.gap.changes=200

# This is the time that any gaps in data_ids will be considered stale and skipped.
#
# DatabaseOverridable: true
# Tags: routing
routing.stale.dataid.gap.time.ms=1200000

# This is the maximum number of data that will be routed during one run.  It should be a number that well
# exceeds the number rows that will be in a transaction.
#
# DatabaseOverridable: true
# Tags: routing
routing.largest.gap.size=50000000

# Use the order by clause to order sym_data when selecting data for routing.  Most databases
# order the data naturally and might even have better performance when the order by clause is
# left off.
#
# DatabaseOverridable: true
# Tags: routing
# Type: boolean
routing.data.reader.order.by.gap.id.enabled=true

# Router will read all unrouted data into memory, then perform sorting.
# Enable this option if sorting is expensive for the database to perform. 
#
# DatabaseOverridable: true
# Tags: routing
# Type: boolean
routing.data.reader.into.memory.enabled=false

# Select data to route from sym_data using a simple > start_gap_id query if
# the number of gaps in sym_data_gap are greater than the following number
#
# DatabaseOverridable: true
# Tags: routing
routing.data.reader.threshold.gaps.to.use.greater.than.query=100

# Enable to collect routing statistics for each batch and log the statistics
# when a batch goes into error.
#
# DatabaseOverridable: true
# Tags: routing
routing.log.stats.on.batch.error=false

# Enable to collect unrouted data statistics into the stat tables for graphs.
#
# DatabaseOverridable: true
# Tags: routing
routing.collect.stats.unrouted=false

# Enable to query for which channels have data waiting, and then only route for those channels.
#
# DatabaseOverridable: true
# Tags: routing
# Type: boolean
routing.query.channels.first=true

# Use a faster method of gap detection that uses the output of the work from router service
# instead of querying for it.
#
# DatabaseOverridable: false
# Tags: routing
# Type: boolean
routing.use.fast.gap.detector=true

# Run checks for duplicate, invalid range, overlapping, and large gaps while processing
# each gap.  This can be used to log information and catch problems with gap detection,
# but it incurs additional overhead.
#
# DatabaseOverridable: true
# Tags: routing
# Type: boolean
routing.detect.invalid.gaps=true

# For a busy system, how often to run checks on sym_data in order to expire gaps.
# Normally the routing reads all data and gap expiration can run without checking sym_data.
# But when the system is busy, then not all data is read, and gap expiration must query each
# gap from the sym_data table, which is expensive.
#
# DatabaseOverridable: true
# Tags: routing
routing.stale.gap.busy.expire.time.ms=7200000

# Start routing again immediately when that last run of routing reached the max data to route
# for a channel.
#
# DatabaseOverridable: true
# Type: boolean
# Tags: routing
routing.immediate.if.max.channel=true

# This is the number of data events that will be batched and committed together while building a batch.
# Note that this only kicks in if the prospective batch size is bigger than the configured max batch size.
#
# DatabaseOverridable: true
# Tags: routing
outgoing.batches.peek.ahead.batch.commit.size=10

# When sending an outgoing batch, copy directly from the outgoing staging to the incoming staging
# when both nodes are on the same server.  This also requires the staging to be enabled
# (stream.to.file.enabled=true).  The HTTP transport is still used to send a batch
# "retry" instruction that causes the target node to read from staging.
#
# DatabaseOverridable: true
# Type: boolean
# Tags: extract
outgoing.batches.copy.to.incoming.staging=true

# Update the outgoing batch status to QY (querying) and SE (sending) only when
# the last update to the batch is in the past by at least the specified number of milliseconds.
# This can improve performance overhead on small batches by avoiding status updates. 
#
# DatabaseOverridable: true
# Tags: extract
outgoing.batches.update.status.millis=10000


# Update the outgoing batch status to QY (querying) and SE (sending) when 
# the data event count is larger than this threshold.  
# This can improve performance overhead on small batches by avoiding status updates. 
#
# DatabaseOverridable: true
# Tags: extract
outgoing.batches.update.status.data.count=1000

# Disable the extraction of all channels with the exception of the config channel
#
# DatabaseOverridable: true
# Tags: extract
# Type: boolean
dataextractor.enable=true

# Provide an expression that will be used in the trigger templates, and in the initial load
# and the sym_data extraction SQL for all text based column values (like varchar, char, nvarchar,
# clob and nchar columns).  The expression can be used to make scenario based casts.  For example,
# if the data in the database was inserted under a different character set that the default character set
# on Oracle, then a helpful expression might be something like this:  
# convert($(columnName), 'AR8ISO8859P6', 'AR8MSWIN1256')
#
# DatabaseOverridable: true
# Tags: extract
# Type: textbox
dataextractor.text.column.expression=

# This instructs symmetric to attempt to skip duplicate batches that are received.  Symmetric might
# be more efficient when recovering from error conditions if this is set to true, but you run the
# risk of missing data if the batch ids get reset (on one node, but not another) somehow (which is unlikely in production, but
# fairly likely in lab or development setups).
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
incoming.batches.skip.duplicates=true

# Indicates whether batches that have loaded successfully should be recorded in the incoming_batch table.
# Note that if this is set to false, then duplicate batches will NOT be skipped because SymmetricDS will
# have no way of knowing that a batch has already loaded.
# This parameter can be set to false to reduce contention on sym_incoming_batch for systems with many clients.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
incoming.batches.record.ok.enabled=true

# Disable the loading of all channel with the exception of the config channel.  This
# property can be set to allow all changes to be extracted without introducing other
# changes in order to allow maintenance operations.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
dataloader.enable=true

# Indicates that old data should be used to create the update statement.  If old data is equal to the new data
# and this property is set to true, then no update statement will be run.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
dataloader.apply.changes.only=false

# Tables that are missing at the target database will be ignored.  This should be set to
# true if you expect that in some clients a table might not exist.  If set to false, the
# batch will fail.
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
dataloader.ignore.missing.tables=false

# Indicate that the data loader should truncate data that is bigger than the target columns can handle.  This applies 
# to text-based columns only.  
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
dataloader.fit.to.column=false

# This is the maximum number of rows that will be supported in a
# single transaction.  If the database transaction row count reaches a size
# that is greater than this number then the transaction will be auto committed.
# The default value of -1 indicates that there is no size limit.
#
# DatabaseOverridable: true
# Tags: load
dataloader.max.rows.before.commit=10000

# Amount of time to sleep before continuing data load after dataloader.max.rows.before.commit rows have been loaded.
# This is useful to give other application threads a chance to do work before continuing to load.
#
# DatabaseOverridable: true
# Tags: load
dataloader.sleep.time.after.early.commit=5

# Whether to alter the case of the database tables that are created by the
# SymmetricDS data loader to match the default case of the target database.
#
# DatabaseOverridable: true
# Tags: load
dataloader.create.table.alter.to.match.db.case=true

# If set to true, when a table's schema is sent to the target database default values will not 
# be included.
#
# DatabaseOverridable: true
# Type: boolean
create.table.without.defaults=false

# If set to true, when a table's schema is sent to the target database foreign keys will not 
# be included.
#
# DatabaseOverridable: true
# Type: boolean
create.table.without.foreign.keys=false

# If set to true, when a table's schema is sent to the target database, indexes will not 
# be included.
#
# DatabaseOverridable: true
# Type: boolean
create.table.without.indexes=false

# If set to true, when a table's schema is sent to the target database it will not have all 
# columns set as the primary key if the source does not have any primary keys.
#
# DatabaseOverridable: true
# Type: boolean
create.table.without.pk.if.source.without.pk=true

# If set to true, when a table's schema is sent to the target database it will use NOT NULL
# statements to match the source.  If this is false NOT NULL will not be included in the sql
#
# DatabaseOverridable: true
# Type: boolean
create.table.not.null.columns.supported=true

# Indicates that the current value of the row should be recorded in the incoming_error table
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
dataloader.error.save.curval=false

# Provide a SQL expression that will be used by the data loader in DML statements 
# for all text based column values (like varchar, char, nvarchar,
# clob and nchar columns).  The expression can be used to make scenario based casts.  For example,
# if the data in the database should be converted to a different character set that the default character set
# on Oracle, then a helpful expression might be something like this:  
# convert($(columnName), 'AR8MSWIN1256', 'AR8ISO8859P6')
#
# DatabaseOverridable: true
# Tags: load
# Type: textbox
dataloader.text.column.expression=

# Indicates that the database writer should use the primary keys from the source.  Flip this to false if
# you want update and deletes to be based on the primary key as defined by the target table
#
# DatabaseOverridable: true
# Tags: load
# Type: boolean
dataloader.use.primary.keys.from.source=true

# The number of milliseconds parameters will be cached by the ParameterService before they are reread from the
# file system and database.
#
# DatabaseOverridable: true
# Tags: other
parameter.reload.timeout.ms=600000

# This is the amount of time node security entries will be cached before re-reading
# them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.node.security.time.ms=600000

# This is the amount of time node entries will be cached before re-reading
# them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.node.time.ms=600000

# This is the amount of time node group links entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.node.group.link.time.ms=600000

# This is the amount of time grouplet entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.grouplets.time.ms=600000

# This is the amount of time trigger entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.trigger.router.time.ms=600000

# This is the amount of time transform entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.transform.time.ms=600000

# This is the amount of time load filter entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.load.filter.time.ms=600000

# This is the amount of time conflict setting entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.conflict.time.ms=600000

# This is the amount of time table meta data will be cached before re-reading it from the database
#
# DatabaseOverridable: false
# Tags: other
cache.table.time.ms=3600000

# This is the amount of time channel entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.channel.time.ms=600000

# This is the amount of time monitor entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.monitor.time.ms=60000

# This is the amount of time notification entries will be cached before re-reading them from the database.
#
# DatabaseOverridable: true
# Tags: other
cache.notification.time.ms=60000

# This is the amount of time the routing service will cache the common batch status of channels.
#
# DatabaseOverridable: true
# Tags: other
cache.channel.common.batches.time.ms=600000

# This is the amount of time the routing service will cache the default router status of channels.
#
# DatabaseOverridable: true
# Tags: other
cache.channel.default.router.time.ms=600000

# When starting jobs, symmetric attempts to randomize the start time to spread out load.  This is the
# maximum wait period before starting a job.
# Tags: jobs
job.random.max.start.time.ms=10000

# This is the retention for how long log summary messages will be retained in memory.
#
# DatabaseOverridable: true
# Tags: purge
purge.log.summary.retention.minutes=60

# This is the retention for how long synchronization data will be kept in the symmetric synchronization
# tables.  Note that data will be purged only if the purge job is enabled.
#
# DatabaseOverridable: true
# Tags: purge
purge.retention.minutes=120

# This is the retention for how long statistic data will be kept in the symmetric stats
# tables.  Note that data will be purged only if the statistics flush job is enabled.
#
# DatabaseOverridable: true
# Tags: purge
purge.stats.retention.minutes=14400

# This is the retention time for how long a extract request will be retained
#
# DatabaseOverridable: true
# Tags: purge
purge.extract.request.retention.minutes=14400

# This is the retention time for how long a registration request will be retained
#
# DatabaseOverridable: true
# Tags: purge
purge.registration.request.retention.minutes=7200

# If using the HsqlDbDialect, this property indicates whether Symmetric should setup the embedded database properties or if an
# external application will be doing so.
# Tags: other
# Type: boolean
hsqldb.initialize.db=true

# This is the precision that is used in the number template for oracle triggers
# DatabaseOverridable: true
# Tags: other
oracle.template.precision=*,38

# Requires access to gv$transaction
# Tags: other
# Type: boolean
# DatabaseOverridable: true
oracle.use.transaction.view=false

# Requires access to gv$transaction.  This is the threshold by which clock can be off in
# an oracle rac environment.  It is only applicable when oracle.use.transaction.view is set
# to true.
# Tags: other
# DatabaseOverridable: true
oracle.transaction.view.clock.sync.threshold.ms=60000

# On Oracle RAC, an ordered sequence for sym_data must be coordinated across RAC nodes, which has
# wait overhead.  By setting this to true, a no-order sequence is used instead, which
# performs better for high throughput.  Because the sequence is no longer ordered,
# sym_data is queried using an order by of create_time and data_id.  You will need to restart
# after changing this parameter to get DDL applied to the sequence and sym_data.
# Tags: other
# Type: boolean
# DatabaseOverridable: true
oracle.sequence.noorder=false

# For Oracle RAC in no-order mode, this parameter provides two methods for managing data gaps across multiple
# nodes in the cluster.  When left blank, routing will use gv$_sequences to manage gaps.
# Or, use this parameter to specify a comma-separated list of database URLs to connect to
# during the heartbeat, which ensures each RAC node has periodic activity within its gap
# to prevent the gap from expiring.
# Tags: other
# DatabaseOverridable: true
oracle.sequence.noorder.nextvalue.db.urls=

# Path to the sqlldr executable for running Oracle SQL*Loader.
# If blank, it will check for ORACLE_HOME environment variable and find sqlldr there.
# Otherwise, it will run "sqlldr" and expect the operating system to find it.
#
# Tags: other
# DatabaseOverridable: false
oracle.bulk.load.sqlldr.cmd=

# Options passed to Oracle SQL*Loader.
#
# Tags: other
# Type: boolean
# DatabaseOverridable: false
oracle.bulk.load.sqlldr.options=silent=(header,discards) direct=false readsize=4096000 bindsize=4096000 rows=2000 errors=0

# For bulk loading with SQL*Loader, specify how to connect to the database with an ezconnect name.
# If blank, the connection is determined using the db.url parameter. 
#
# Tags: other
# DatabaseOverridable: false
oracle.bulk.load.ezconnect=

# For initial load extracting data to specify the number of parallel processes to use while selecting data from a table
#
# Tags: other
# DatabaseOverridable: true
oracle.load.query.hint.parallel.count=1

# Path to the tbloader executable for running Tibero tbLoader.
# If blank, it will check for TB_HOME environment variable and find tbLoader there.
# Otherwise, it will run "tbloader" and expect the operating system to find it.
#
# Tags: other
# DatabaseOverridable: false
tibero.bulk.load.tbloader.cmd=

# Options passed to Tibero tbLoader
#
# Tags: other
# Type: boolean
# DatabaseOverridable: false
tibero.bulk.load.tbloader.options=direct=N dpl_parallel=1 disable_idx=N readsize=2097152 bindsize=2097152 rows=2000 errors=0

# For bulk loading with tbLoader, specify the database name.
# If blank, the database name is determined using the db.url parameter. 
#
# Tags: other
# DatabaseOverridable: false
tibero.bulk.load.dname=

# Use to map the version string a zseries jdbc driver returns to the 'zseries' dialect
# Tags: other
db2.zseries.version=DSN08015

# Specify the database type to cast clob values to
# DatabaseOverridable: true
# Tags: AS400
as400.cast.clob.to=DBCLOB

# Turn on the capture of transaction id for DB2 systems that support it.
# DatabaseOverridable: false
# Tags: DB2
db2.capture.transaction.id=false

# Specify the type of line feed to use in JMX console methods.  Possible values are: text or html.
# Tags: other
jmx.line.feed=text

# Specify whether to push node_host records to configured push clients.  If this is true
# the node for this instance and the node_host rows for all children instances will be pushed
# to all nodes that this node is configured to push to.
# DatabaseOverridable: true
# Tags: other
# Type: boolean
heartbeat.sync.on.push.enabled=true

# This is the number of seconds between when the sym_node_host table's heartbeat_time column is
# updated.  This property depends on the frequency of the heartbeat job.  If the heartbeat job
# is set to run every 10 minutes and this property is set to 10 seconds, then the heartbeat will
# only update every 10 minutes.
# DatabaseOverridable: true
# Tags: other
heartbeat.sync.on.push.period.sec=0

# When this property is set to true the heartbeat process will run at server startup.  Prior to 3.4
# the heartbeat always happened at startup.
# DatabaseOverridable: true
# Tags: other
# Type: boolean
heartbeat.sync.on.startup=false

# When this is set to true, SymmetricDS will update fields in the sym_node table that indicate the
# number of outstanding errors and/or batches it has pending
# DatabaseOverridable: true
# Tags: other
# Type: boolean
heartbeat.update.node.with.batch.status=false

# This is the number of minutes that a node has been offline before taking action
# A value of -1 (or any negative value) disables the feature.
# DatabaseOverridable: true
# Tags: other
offline.node.detection.period.minutes=-1

# This is the number of minutes after a node has been restarted that it will begin
# considering remote nodes as offline.  This gives remote nodes a chance to send
# their heartbeats.
# DatabaseOverridable: true
# Tags: other
offline.node.detection.restart.minutes=5

# Enable this property to force a compare of old and new data in triggers.  If
# old=new, then don't record the change in the data capture table.
#
# This is currently supported by the following dialects:  mysql, oracle, db2, postgres, sql server
# DatabaseOverridable: true
# Tags: other
# Type: boolean
trigger.update.capture.changed.data.only.enabled=false

# Disable this property to prevent table triggers from being created before initial load
# has completed.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
trigger.create.before.initial.load.enabled=true

# Feature to install a DDL trigger to capture any schema changes, including
# tables, views, triggers, functions, and stored procedures, which are synced
# to all nodes on configured group links.  Supported on MS SQL-Server only.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
trigger.capture.ddl.changes=false

# This is a setting that instructs the data capture and data load to
# treat JDBC TIME, DATE, and TIMESTAMP columns as if they were VARCHAR
# columns.  This means that the columns will be captured and loaded in
# the form that the database stores them.  Setting this to true on MySQL
# will allow datetime columns with the value of '0000-00-00 00:00:00' to
# be synchronized.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
db.treat.date.time.as.varchar.enabled=false

# This is the expected increment value for the data_id in the data table.
# This is useful if you use auto_increment_increment and auto_increment_offset in MySQL.
# Note that these settings require innodb_autoinc_lock_mode=0, otherwise the increment
# and offset are not guaranteed.
# DatabaseOverridable: true
# Tags: other
data.id.increment.by=1

# Control whether statistics are recorded.
#
# Tags: other
# Type: boolean
# statistic.record.enable=false

# The maximum number of unprocessed outgoing batch rows for a node that will be read
# into memory for the next data extraction.
#
# DatabaseOverridable: true
# Tags: extract
outgoing.batches.max.to.select=50000

# The class name for the Security Service to use for encrypting and
# decrypting database passwords
# Tags: database
security.service.class.name=org.jumpmind.security.SecurityService

# This is a bean shell script that will be used to generate the node id
# for a registering node.  This script is run on the registration server,
# not the registering node.  The following variable are available for use:
# node, hostname, remoteHost, remoteAddress, and log.  You can get the node
# group id by calling node.getNodeGroupId()
# DatabaseOverridable: true
# Type: code
# Tags: registration
node.id.creator.script=

# Determines if a node id will be assigned the external id directly or if the external id (and thereby the node id) 
# will be forced to be unique.  This is done by adding the "-0", "-1", sequence to the end of the 
# node id.   By default the node id will just be assigned the external id directly without change.

# DatabaseOverridable: true
# Type: boolean
external.id.is.unique.enabled=true

# Enables the REST API
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
rest.api.enable=false

# Enables the REST API to update the heartbeat when pulling data
#
# DatabaseOverridable: true
# Tags: general
# Type: boolean
rest.api.heartbeat.on.pull=false

# Enables File Synchronization capabilities
#
# DatabaseOverridable: true
# Tags: filesync
# Type: boolean
file.sync.enable=false

# How long file sync should wait in millis for the exclusive lock used by file tracker
# or the shared lock used by file sync push/pull jobs.
#
# Tags: filesync
# DatabaseOverridable: true
file.sync.lock.wait.ms=300000

# DatabaseOverridable: true
# Tags: jobs,filesync
job.file.sync.tracker.cron=0 0/5 * * * *

# DatabaseOverridable: true
# Tags: jobs,filesync
job.file.sync.pull.period.time.ms=60000

# Fast scan will look for files that were modified since the last run of file sync tracker
# and commit their changes using the data loader max commit row setting.
# When it finds modified directories, it compares to the file snapshot to find changes.
# For a large file system, this is faster and more efficient than the normal tracker.
#
# DatabaseOverridable: true
# Tags: filesync
# Type: boolean
file.sync.fast.scan=true

# Calculate a checksum for each file (using CRC32), which is used to detect a file collision
# if the target file has a different checksum.  If you don't need to detect conflicts,
# turn this off for better performance.
#
# DatabaseOverridable: true
# Tags: filesync
# Type: boolean    
file.sync.use.crc=true

# Record each file received in the sym_incoming_file table, which is checked when syncing
# outgoing files to prevent a "ping back" where the same file change is sent back and forth
# during bi-directional sync.  If you aren't using bi-directional sync,
# turn this off for better performance.
#
# DatabaseOverridable: true
# Tags: filesync
# Type: boolean
file.sync.prevent.ping.back=true

# DatabaseOverridable: true
# Tags: jobs,filesync
file.pull.period.minimum.ms=0

# DatabaseOverridable: true
# Tags: jobs,filesync
file.pull.thread.per.server.count=1

# DatabaseOverridable: true
# Tags: jobs,filesync
file.pull.lock.timeout.ms=7200000

# DatabaseOverridable: true
# Tags: jobs,filesync
job.file.sync.push.period.time.ms=60000

# DatabaseOverridable: true
# Tags: jobs,filesync
file.push.period.minimum.ms=0

# DatabaseOverridable: true
# Tags: jobs,filesync
file.push.thread.per.server.count=1

# DatabaseOverridable: true
# Tags: jobs,filesync
file.push.lock.timeout.ms=7200000

# If the ctl file is used to control file triggers this will allow the system to remove
# the ctl file after sync but leave the source file.
#
# DatabaseOverridable: true
# Tags: filesync
# Type: boolean   
file.sync.delete.ctl.file.after.sync=false

# If the ctl file is used to control file triggers this will look for a control file
# with the same name but .ctl replacing the existing extension.  
# Example: temp.txt would need control file called temp.ctl instead of temp.txt.ctl
#
# DatabaseOverridable: true
# Tags: filesync
# Type: boolean 
file.sync.use.ctl.as.file.ext=false

# This parameter can be used to indicate that bean shell load filters will handle missing tables.  Useful
# for the case where you want to make, for example, global catalog or schema changes at the destination
# in the case where the catalog, schema, or table doesn't exist but the BSH will handle it.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
bsh.load.filter.handles.missing.tables=false

# BeanShell script to include at the beginning of all scripts used in transforms
#
# DatabaseOverridable: true
# Tags: other
# Type: code
bsh.transform.global.script=

# Maximum number of rows to write to file before running with 'LOAD DATA INFILE' to MySQL
#
# DatabaseOverridable: false
# Tags: other
mysql.bulk.load.max.rows.before.flush=100000

# Maximum number of bytes to write to file before running with 'LOAD DATA INFILE' to MySQL
#
# DatabaseOverridable: false
# Tags: other
mysql.bulk.load.max.bytes.before.flush=1000000000

# Whether or not files are local to client only, so we must send the file to MySQL to load.  
# If client is running on same server as MySQL, then this can be set to false to have MySQL read file directly.
#
# DatabaseOverridable: false
# Tags: other
# Type: boolean
mysql.bulk.load.local=true

# Whether or not to replace rows that already exist, based on primary key or unique key.
# If set to false, duplicates will be skipped. 
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
mysql.bulk.load.replace=true

# Allows MySQL columns of type tinyint to be sent to other platforms as boolean in ddl statements 
#
# DatabaseOverridable: true
# Tags: mysql
# Type: boolean
mysql.tinyint.ddl.to.boolean=false

# Maximum number of rows to write to file before running with "BULK INSERT" to SQL-Server
#
# DatabaseOverridable: true
# Tags: other, mssql
mssql.bulk.load.max.rows.before.flush=100000

# Whether or not triggers should be allowed to fire when bulk loading data.
#
# DatabaseOverridable: true
# Tags: other, mssql
# Type: boolean
mssql.bulk.load.fire.triggers=false

# Specify a UNC network path to the tmp\bulkloaddir directory for SQL Server to access bulk load files.
# Use this property with bulk loader when SymmetricDS is on a separate server from SQL Server. 
#
# DatabaseOverridable: true
# Tags: other, mssql
mssql.bulk.load.unc.path=

# Specify the line terminator used by the SQL Server bulk loader.  Pick something that does not exist in the
# data in your database. 
#
# DatabaseOverridable: true
# Tags: other, mssql
mssql.bulk.load.row.terminator=\\r\\n

# Specify the field terminator used by the SQL Server bulk loader.  Pick something that does not exist in the
# data in your database. 
#
# DatabaseOverridable: true
# Tags: other, mssql
mssql.bulk.load.field.terminator=||

# Automatically update data, data_event and outgoing_batch tables to allow only
# row level locking.
#
# DatabaseOverridable: true
# Tags: other, mssql
# Type: boolean
mssql.allow.only.row.level.locks.on.runtime.tables=true

# Use ntext for the data capture columns and cast to nvarchar(max) in the 
# trigger text so that nvarchar, ntext and nchar double byte data isn't lost
# when the database collation for char types isn't compatible with n char types.
#
# DatabaseOverridable: true
# Tags: other, mssql
# Type: boolean
mssql.use.ntypes.for.sync=false

# Specify the user the SymmetricDS triggers should execute as.  Possible values are
# { CALLER | SELF | OWNER | 'user_name' }
# DatabaseOverridable: true
# Tags: other, mssql
mssql.trigger.execute.as=caller

# Set the order of triggers to 'First' using sp_settriggerorder after creating triggers.
# This is needed when the user has existing custom triggers that modify data.
# The SymmetricDS triggers need to fire first and capture the first change so that order of changes is preserved.
# If the user has a trigger set as 'First', it will be changed to 'None'.
#
# DatabaseOverridable: true
# Tags: other, mssql
# Type: boolean
mssql.trigger.order.first=false

# Disables lock escalation and turns off page level locking.  May need turned off to support backup processes such as creating a bacpac file
#
# DatabaseOverridable: true
# Tags: other, mssql
# Type: boolean
mssql.lock.escalation.disabled=true

# Includes the catalog/database name within generated triggers (catalog.schema.table).  May need turned off to support backup processes such as creating a bacpac file
#
# DatabaseOverridable: true
# Tags: other, mssql
# Type: boolean
mssql.include.catalog.in.triggers=true

# For Sql Server, work around "Implicit conversion of varchar" issues by explicitly collating varchar
# columns in the database trigger.  Relevant when the default database collation does not match the
# collation of the varchar columns of a  table
#
# DatabaseOverridable: true
# Tags: other, mssql
db.master.collation=

# Spring xml configuration for extension points.  This property enables maintaining
# Spring extension point configuration in the database.  After changing this property 
# a server restart is required.
#
# DatabaseOverridable: true
# Tags: other
# Type: xml 
extensions.xml=<?xml version="1.0" encoding="UTF-8"?> \n\
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n\u0020\u0020\u0020\u0020\
       xmlns:context="http://www.springframework.org/schema/context" \n\u0020\u0020\u0020\u0020\
       xmlns:util="http://www.springframework.org/schema/util" \n\u0020\u0020\u0020\u0020\
       xsi:schemaLocation="http://www.springframework.org/schema/beans \n\u0020\u0020\u0020\u0020\
       http://www.springframework.org/schema/beans/spring-beans-3.0.xsd \n\u0020\u0020\u0020\u0020\
       http://www.springframework.org/schema/util \n\u0020\u0020\u0020\u0020\
       http://www.springframework.org/schema/util/spring-util-3.0.xsd \n\u0020\u0020\u0020\u0020\
       http://www.springframework.org/schema/context \n\u0020\u0020\u0020\u0020\
       http://www.springframework.org/schema/context/spring-context-3.0.xsd"> \n\
</beans>

# If the copy mode is enabled and the node starts up with an identity that does not match
# the configured external id, then the node will register with a special parameter that 
# indicates the registration server should copy outgoing batch to the new node id.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
node.copy.mode.enabled=false

# Maximum number of rows to write to file before copying to S3 and running with COPY statement
#
# DatabaseOverridable: true
# Tags: redshift
redshift.bulk.load.max.rows.before.flush=100000

# Maximum number of bytes to write to file before copying to S3 and running with COPY statement
#
# DatabaseOverridable: true
# Tags: redshift
redshift.bulk.load.max.bytes.before.flush=1000000000

# The S3 bucket where bulk load files will be uploaded to before bulk loading into Redshift
#
# DatabaseOverridable: true
# Tags: redshift
redshift.bulk.load.s3.bucket=

# The endpoint for the s3 bucket.  If not set it will use the default endpoint.
#
# DatabaseOverridable: true
# Tags: redshift
redshift.bulk.load.s3.endpoint=

# The AWS access key ID (aws_access_key_id) to use as credentials for uploading to S3
#
# DatabaseOverridable: true
# Tags: redshift
redshift.bulk.load.s3.access.key=

# The AWS secret access key (aws_secret_access_key) to use as credentials for uploading to S3
#
# DatabaseOverridable: true
# Tags: redshift
redshift.bulk.load.s3.secret.key=

# The value of this property will be appended to the end of the copy command when the redshift
# data loader is enabled.
#
# DatabaseOverridable: true
# Tags: redshift
redshift.append.to.copy.command=

# Whether the offline pull job is enabled for this node.
#
# Tags: jobs
# DatabaseOverridable: true
# Type: boolean
start.offline.pull.job=false

# Whether the offline push job is enabled for this node.
#
# Tags: jobs
# DatabaseOverridable: true
# Type: boolean
start.offline.push.job=false

# This is how often the offline push job will be run to schedule offline writing of batch files for nodes.
#
# DatabaseOverridable: true
# Tags: jobs
job.offline.push.period.time.ms=60000

# This is how often the offline pull job will be run to schedule offline reading of batch files from nodes.
#
# DatabaseOverridable: true
# Tags: jobs
job.offline.pull.period.time.ms=60000

# The number of threads created that will be used to read incoming offline batch data files
#
# DatabaseOverridable: true
# Tags: jobs
offline.pull.thread.per.server.count=1

# The amount of time a single offline pull worker node_communication lock will timeout after.
#
# DatabaseOverridable: true
# Tags: jobs
offline.pull.lock.timeout.ms=7200000

# The number of threads created that will be used to write outgoing offline batch data files
#
# DatabaseOverridable: true
# Tags: jobs
offline.push.thread.per.server.count=1

# The amount of time a single offline push worker node_communication lock will timeout after.
#
# DatabaseOverridable: true
# Tags: jobs
offline.push.lock.timeout.ms=7200000

# Set the node to offline mode so that outgoing and incoming data are written 
# to and read from a local directory instead of being sent over the network.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
node.offline=false

# For a node operating in offline mode, specify the local directory
# where data files should be read from.  The $(nodeGroupId) and $(nodeId)
# variables are useful when running multiple engines in the same server.
#
# DatabaseOverridable: true
# Tags: other
node.offline.incoming.dir=tmp/$(nodeGroupId)-$(nodeId)/offline/incoming

# Accept batch data files from any node in the incoming directory, regardless
# of whether or not it is considered offline.
#
# DatabaseOverridable: true
# Tags: other
node.offline.incoming.accept.all=true

# For a node operating in offline mode, specify the local directory
# where data files should be written to.  The $(nodeGroupId) and $(nodeId)
# variables are useful when running multiple engines in the same server.
#
# DatabaseOverridable: true
# Tags: other
node.offline.outgoing.dir=tmp/$(nodeGroupId)-$(nodeId)/offline/outgoing

# For a node operating in offline mode, specify the local directory
# where incoming data files should be moved to when they encounter
# an error during loading.  To guarentee order of data loading, this
# parameter should be left empty so the file is not moved.
# The $(nodeGroupId) and $(nodeId)
# variables are useful when running multiple engines in the same server.
#
# DatabaseOverridable: true
# Tags: other
node.offline.error.dir=

# For a node operating in offline mode, specify the local directory
# where incoming data files should be moved to after successfully
# loading them.  If this parameter is empty, files are removed
# after loading.
# The $(nodeGroupId) and $(nodeId)
# variables are useful when running multiple engines in the same server.
#
# DatabaseOverridable: true
# Tags: other
node.offline.archive.dir=

# Enable capturing of monitor events and syncing to other nodes.
# When disabled, monitor events are still generated, just not synced to other nodes.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
monitor.events.capture.enabled=false


# Determines if the *.DBF file headers should be validated when using the DBF Router
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
dbf.router.validate.header=true

# Enable hybrid push/pull functionality.  Allows for pull configuration, but also allows clients to report 
# their outgoing batch status so that the nodes that have data can be prioritized for pulling.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
hybrid.push.pull.enabled=false

# When hybrid.push.pull.enabled=true, how much time in millis has to go by to pull from a node that hasn't
# reported pending batches. 
#
# DatabaseOverridable: true
# Tags: other
hybrid.push.pull.timeout.ms=3600000

# This controls whether or not the ReportStatus job will buffer its status updates.  When buffered, status 
# updates will only be sent when a channel's batch to send count goes from 0 to non-zero.
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
hybrid.push.pull.buffer.status.updates=true

# On Firebird database, the varchar sizes to use during extracting the row_data, old_data, and pk_data
# from sym_data.  Specify the values as comma-separated for row, old, and pk respectively.  
# By casting to varchar and using small sizes, performance of extract is improved.
# The entire row size must be under 64K or you will get a "block size exceeds implementation restriction" error.
# If you need to extract larger sizes, then enable the contains_big_lobs on the channel. 
#
# DatabaseOverridable: true
# Tags: other, firebird
firebird.extract.varchar.row.old.pk.data=20000,20000,1000

# Check for a newer version of SymmetricDS and let the user know when one is available.
#
# DatabaseOverridable: true
# Tags: other
check.software.updates=true

# Send usage statistics to the SymmetricDS project to help improve the software.
#
# DatabaseOverridable: true
# Tags: other
send.usage.stats=true

# The hostname of the mail server
#
# DatabaseOverridable: true
# Tags: smtp
smtp.host=localhost

# The transport type to use when connecting to mail server, either smtp or smtps.
#
# DatabaseOverridable: true
# Tags: smtp
smtp.transport=smtp

# The port number of the mail server 
#
# DatabaseOverridable: true
# Tags: smtp
smtp.port=25

# The email address to use in the "from" header when sending email.
#
# DatabaseOverridable: true
# Tags: smtp
smtp.from=symmetricds@localhost

# Whether or not to authenticate with the mail server.
#
# DatabaseOverridable: true
# Type: boolean
# Tags: smtp
smtp.auth=false

# When authenticating with the mail server, the username to use.
#
# DatabaseOverridable: true
# Tags: smtp
smtp.user=

# When authenticating with the mail server, the password to use. 
#
# DatabaseOverridable: true
# Tags: smtp
smtp.password=

# Whether or not to use TLS after connecting to the mail server. 
#
# DatabaseOverridable: true
# Type: boolean
# Tags: smtp
smtp.starttls=false

# Whether or not to accept an untrusted certificate for SSL/TLS when connecting to the mail server.
#
# DatabaseOverridable: true
# Type: boolean
# Tags: smtp
smtp.allow.untrusted.cert=false

# Setting that defines when a Node should be considered "offline."  The node offline monitor uses this setting.
#
# DatabaseOverridable: true
# Tags: other
console.report.as.offline.minutes=1440

# Enables the Grouplet functionality
#
# DatabaseOverridable: true
# Tags: grouplet
# Type: boolean
grouplet.enable=false

# Whether logging is enabled for conflict resolution
#
# DatabaseOverridable: true
# Type: boolean
# Tags: load
log.conflict.resolution=false

# Whether binary fields should be treated as lobs
#
# DatabaseOverridable: false
# Type: boolean
# Tags: other
treat.binary.as.lob.enabled=true

# Whether char fields should be right trimmed
#
# DatabaseOverridable: true
# Type: boolean
# Tags: other
right.trim.char.values=false

# When executing DML statements during data load, this controls whether executeUpdate or execute is used on the PreparedStatement.  executeUpdate
# is used by default. execute() allows for unusual situations like when an application trigger generates a result set during an 
# update statement.
#
# DatabaseOverridable: true
# Type: boolean
# Tags: other
allow.updates.with.results=false

# This is the location the staging directory will be put.   If it isn't set the staging directory will be located according to java.io.tmpdir.
#
# DatabaseOverridable: false
# Tags: init
staging.dir=

# Staging directory low disk space threshold in megabytes.
# When free space goes below the threshold, requests to create staging files will receive an exception. 
# Data loading and extracting will stop and log an error until disk space becomes available.
# To disable free space checks, set to zero or negative.
#
# DatabaseOverridable: false
# Tags: init
staging.low.space.threshold.megabytes=100


# The snowflake managed stage name for internal storage
#
# DatabaseOverridable: true
# Tags: cloud, snowflake
snowflake.internal.stage.name=

# The snowflake staging type to use for bulk loading
# 
# Valid values : SNOWFLAKE_INTERNAL, AWS_S3, AZURE
#
# DatabaseOverridable: true
# Tags: cloud, snowflake
snowflake.staging.type=

# Maximum number of rows to write to file before copying to cloud storage
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, redshift
cloud.bulk.load.max.rows.before.flush=-1

# Maximum number of bytes to write to file before copying to cloud storage
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, redshift
cloud.bulk.load.max.bytes.before.flush=-1

# The S3 bucket where bulk load files will be uploaded
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, redshift
cloud.bulk.load.s3.bucket=

# The AWS access key ID (aws_access_key_id) to use as credentials for uploading to S3
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, redshift
cloud.bulk.load.s3.access.key=

# The AWS secret access key (aws_secret_access_key) to use as credentials for uploading to S3
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, redshift
cloud.bulk.load.s3.secret.key=

# The endpoint for the s3 bucket.  If not set it will use the default endpoint.
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, redshift
cloud.bulk.load.s3.endpoint=

# The AWS S3 region
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, azure
cloud.bulk.load.s3.region=us-east-1

# The Azure storage account name
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, azure
cloud.bulk.load.azure.account.name=

# The Azure storage account key
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, azure
cloud.bulk.load.azure.account.key=

# The Azure storage account blob container name
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, azure
cloud.bulk.load.azure.blob.container=symmetricds

# The Azure storage account SAS Token (Shared Access Signature)
#
# DatabaseOverridable: true
# Tags: cloud, snowflake, azure
cloud.bulk.load.azure.sas.token=

# Prefix snapshot filename with hostname to indicate which environment it came from
#
# DatabaseOverridable: true
# Tags: other
# Type: boolean
snapshot.file.include.hostname=false