<commit_before>######################### Crate Configuration File ############################

# The default configuration offers the ability to use Crate right away.
# The purpose of this file is to give operators an overview of the various
# different configuration settings. To read the full documentation go to
# <https://crate.io/docs/>

# Use this file to fine-tune your Crate cluster. If you have any questions
# you are very welcome to contact us on our Community Channel on Slack
# <https://crate.io/docs/support/slackin/>.


################################ Quick Settings ###############################

# Recommended memory settings:
# - set the environment variable CRATE_HEAP_SIZE to half of your memory
#   (e.g. 26G, but not more than ~30G to benefit from CompressedOops).
#   Depending on the OS the best place to do so is
#   '/etc/default/crate' or '/etc/sysconfig/crate'
# - disable swapping
#bootstrap.mlockall: true

# Name of the Node, e.g. '$(hostname -s)'
#node.name: "<NAME>"

# Crate can utilize multiple volumes in parallel,
# make sure to set the owner to 'crate:crate'
#path.data: /path/to/data1,/path/to/data2

# Recommended: The amount of Crate instances in the full cluster
#gateway.expected_nodes: 3

# Recommended: More then half of the Crate instances in the full cluster
#gateway.recover_after_nodes: 2
#discovery.zen.minimum_master_nodes: 2

# most cloud environments don't support multicast discovery
#discovery.zen.ping:
#  - multicast.enabled: false
#  - unicast.hosts:
#    - host1:4300
#    - host2:4300

# Enable the Elasticsearch API?
#es.api.enabled: false


################################# Full Settings ###############################

# Any element in the configuration can be replaced with environment variables
# by placing them in ${...} notation. For example:
#
#node.rack: ${RACK_ENV_VAR}


################################### Cluster ###################################

# Cluster name identifies your cluster for auto-discovery. If you're running
# multiple clusters on the same network, make sure you're using unique names.
#
#cluster.name: crate

# The graceful_stop namespace defines settings for a graceful stop
# procedure of nodes within the cluster.
#
# The minimum data availability the cluster needs to ensure when a certain node
# is shut down. By default the cluster ensures availability of primary shards
# but not replicas. Other options are "full" and "none".
#
#cluster.graceful_stop.min_availability: primaries
#
# The cluster may reallocate shards to ensure minimum data availabillity before
# a certain node shuts down.
#
#cluster.graceful_stop.reallocate: true
#
# The time to wait for the reallocation process to be finished.
#
#cluster.graceful_stop.timeout: 2h
#
# The force setting allows you to force a shutdown of a node when the graceful
# shutdown process runs into the cluster.graceful_stop.timeout.
#
#cluster.graceful_stop.force: false
#
# By default the regular stop procedure does not consider the graceful_stop
# settings, but only sending the USR2 signal to the process does.
#
# In most cases you want to allow all kinds of shards allocations.
#cluster.routing.allocation.enable = all
#
# However, you can limit shard allocations to certain kinds of shards,
# for example if you perform a rolling cluster upgrade.
#cluster.routing.allocation.enable = new_primaries

#################################### Node #####################################

# Node names are generated dynamically on startup, so you're relieved
# from configuring them manually. You can tie this node to a specific name:
#
#node.name: "<NAME>"

# Every node can be configured to allow or deny being eligible as the master,
# and to allow or deny to store the data.
#
# Allow this node to be eligible as a master node (enabled by default):
#
#node.master: true
#
# Allow this node to store data (enabled by default):
#
#node.data: true

# You can exploit these settings to design advanced cluster topologies.
#
# 1. You want this node to never become a master node, only to hold data.
#    This will be the "workhorse" of your cluster.
#
#node.master: false
#node.data: true
#
# 2. You want this node to only serve as a master: to not store any data and
#    to have free resources. This will be the "coordinator" of your cluster.
#
#node.master: true
#node.data: false
#
# 3. You want this node to be neither master nor data node, but
#    to act as a "search load balancer" (fetching data from nodes,
#    aggregating results, etc.)
#
#node.master: false
#node.data: false

# Inspect the cluster state via GUI tools
# such as Crate Admin [http://localhost:4200/admin/].

# A node can have generic attributes associated with it, which can later be
# used for customized shard allocation filtering, or allocation awareness.
# An attribute is a simple key value pair, similar to node.key: value, here is
# an example:
#
#node.rack: rack314

# By default, multiple nodes are allowed to start from the same installation
# location to disable it, set the following:
#node.max_local_storage_nodes: 1

#################################### Table ####################################

# You can set a number of options (such as shard/replica options, mapping
# or analyzer definitions, translog settings, ...) for tables globally,
# in this file.
#
# Note, that it makes more sense to configure table settings specifically for
# a certain table when creating it.

# Set the number of shards (splits) of a table (5 by default):
#
#index.number_of_shards: 5

# Set the number of replicas (additional copies) of a table (1 by default):
#
#index.number_of_replicas: 1

# Note, that for development on a local machine, with small tables, it usually
# makes sense to "disable" the distributed features:
#
#index.number_of_shards: 1
#index.number_of_replicas: 0

# Set the refresh interval of a shard in milliseconds.
#
#index.refresh_interval: 1000

# Disable/enable read-only table.
#
#index.blocks.read_only: false

# Disable/enable all the read operations.
#
#index.blocks.read: false

# Disable/enable all the write operations.
#
#index.blocks.write: false

# Disables/enables the table settings modifications.
#
#index.blocks.metadata: false

# Set the number of operations before flushing.
#
#index.translog.flush_threshold_ops: unlimited

# Sets size of transaction log prior to flushing.
#
#index.translog.flush_threshold_size: 200mb

# Sets period of no flushing after which force flush occurs.
#
#index.translog.flush_threshold_period: 30m

# Disable/enable flushing.
# Recommended to use only for small periods of time
#
#index.translog.disable_flush: false

# Controls shard allocation for a specific table.
#
#index.routing.allocation.enable: all

# Controls the total number of shards (replicas and primaries) allowed to be allocated on a single node.
#
#index.routing.allocation.total_shards_per_node: -1

# When using local gateway a particular shard is recovered only if there can be allocated quorum of it’s copies in the cluster.
#
#index.recovery.initial_shards: quorum

#disable/enable table warming. Table warming allows to run registered queries to warm up the table before it is available.
#
#index.warmer.enabled:true

# These settings directly affect the performance of table and search operations
# in your cluster. Assuming you have enough machines to hold shards and
# replicas, the rule of thumb is:
#
# 1. Having more *shards* enhances the _indexing_ performance and allows to
#    _distribute_ a big table across machines.
# 2. Having more *replicas* enhances the _search_ performance and improves the
#    cluster _availability_.
#
# The "number_of_shards" is a one-time setting for a table.
#
# Crate takes care about load balancing, relocating, gathering the
# results from nodes, etc. Experiment with different settings to fine-tune
# your setup.

# Use the Table Status API (<http://localhost:4200/A/_status>) to inspect
# the table status.


#################################### Paths ####################################

# Path to directory containing configuration (this file and logging.yml):
#
#path.conf: /path/to/conf

# Path to directory where to store table data allocated for this node.
#
#path.data: /path/to/data
#
# Can optionally include more than one location, causing data to be striped across
# the locations (a la RAID 0) on a file level, favouring locations with most free
# space on creation. For example:
#
#path.data: /path/to/data1,/path/to/data2

# Path to temporary files:
#
#path.work: /path/to/work

# Path to log files:
#
#path.logs: /path/to/logs

# Path to where plugins are installed:
#
#path.plugins: /path/to/plugins


#path:
#  - logs: /var/log/crate
#  - data: /var/lib/crate


#################################### Plugin ###################################

# If a plugin listed here is not installed for current node, the node will not start.
#
#plugin.mandatory: mapper-attachments,lang-groovy


################################### Memory ####################################

# Crate performs poorly when JVM starts swapping: you should ensure that
# it _never_ swaps.
#
# Set this property to true to lock the memory:
#
#bootstrap.mlockall: true

# Make sure that the machine has enough memory to allocate for Crate, leaving
# enough memory for the operating system itself.
# You can allocate memory for Crate as follows:
#  - Set CRATE_MIN_MEM and CRATE_MAX_MEM environment variables
#    (We recommend to set MIN and MAX to the same value).
#  - Set CRATE_HEAP_SIZE environment varaible. This sets MIN and MAX to the
#    same value for you.
#
# You should also make sure that the Crate process is allowed to lock<commit_msg>correct yaml syntax<commit_after>######################### Crate Configuration File ############################

# The default configuration offers the ability to use Crate right away.
# The purpose of this file is to give operators an overview of the various
# different configuration settings. To read the full documentation go to
# <https://crate.io/docs/>

# Use this file to fine-tune your Crate cluster. If you have any questions
# you are very welcome to contact us on our Community Channel on Slack
# <https://crate.io/docs/support/slackin/>.


################################ Quick Settings ###############################

# Recommended memory settings:
# - set the environment variable CRATE_HEAP_SIZE to half of your memory
#   (e.g. 26G, but not more than ~30G to benefit from CompressedOops).
#   Depending on the OS the best place to do so is
#   '/etc/default/crate' or '/etc/sysconfig/crate'
# - disable swapping
#bootstrap.mlockall: true

# Name of the Node, e.g. '$(hostname -s)'
#node.name: "<NAME>"

# Crate can utilize multiple volumes in parallel,
# make sure to set the owner to 'crate:crate'
#path.data: /path/to/data1,/path/to/data2

# Recommended: The amount of Crate instances in the full cluster
#gateway.expected_nodes: 3

# Recommended: More then half of the Crate instances in the full cluster
#gateway.recover_after_nodes: 2
#discovery.zen.minimum_master_nodes: 2

# most cloud environments don't support multicast discovery
#discovery.zen.ping:
#  multicast.enabled: false
#  unicast.hosts:
#    - host1:4300
#    - host2:4300

# Enable the Elasticsearch API?
#es.api.enabled: false


################################# Full Settings ###############################

# Any element in the configuration can be replaced with environment variables
# by placing them in ${...} notation. For example:
#
#node.rack: ${RACK_ENV_VAR}


################################### Cluster ###################################

# Cluster name identifies your cluster for auto-discovery. If you're running
# multiple clusters on the same network, make sure you're using unique names.
#
#cluster.name: crate

# The graceful_stop namespace defines settings for a graceful stop
# procedure of nodes within the cluster.
#
# The minimum data availability the cluster needs to ensure when a certain node
# is shut down. By default the cluster ensures availability of primary shards
# but not replicas. Other options are "full" and "none".
#
#cluster.graceful_stop.min_availability: primaries
#
# The cluster may reallocate shards to ensure minimum data availabillity before
# a certain node shuts down.
#
#cluster.graceful_stop.reallocate: true
#
# The time to wait for the reallocation process to be finished.
#
#cluster.graceful_stop.timeout: 2h
#
# The force setting allows you to force a shutdown of a node when the graceful
# shutdown process runs into the cluster.graceful_stop.timeout.
#
#cluster.graceful_stop.force: false
#
# By default the regular stop procedure does not consider the graceful_stop
# settings, but only sending the USR2 signal to the process does.
#
# In most cases you want to allow all kinds of shards allocations.
#cluster.routing.allocation.enable = all
#
# However, you can limit shard allocations to certain kinds of shards,
# for example if you perform a rolling cluster upgrade.
#cluster.routing.allocation.enable = new_primaries

#################################### Node #####################################

# Node names are generated dynamically on startup, so you're relieved
# from configuring them manually. You can tie this node to a specific name:
#
#node.name: "<NAME>"

# Every node can be configured to allow or deny being eligible as the master,
# and to allow or deny to store the data.
#
# Allow this node to be eligible as a master node (enabled by default):
#
#node.master: true
#
# Allow this node to store data (enabled by default):
#
#node.data: true

# You can exploit these settings to design advanced cluster topologies.
#
# 1. You want this node to never become a master node, only to hold data.
#    This will be the "workhorse" of your cluster.
#
#node.master: false
#node.data: true
#
# 2. You want this node to only serve as a master: to not store any data and
#    to have free resources. This will be the "coordinator" of your cluster.
#
#node.master: true
#node.data: false
#
# 3. You want this node to be neither master nor data node, but
#    to act as a "search load balancer" (fetching data from nodes,
#    aggregating results, etc.)
#
#node.master: false
#node.data: false

# Inspect the cluster state via GUI tools
# such as Crate Admin [http://localhost:4200/admin/].

# A node can have generic attributes associated with it, which can later be
# used for customized shard allocation filtering, or allocation awareness.
# An attribute is a simple key value pair, similar to node.key: value, here is
# an example:
#
#node.rack: rack314

# By default, multiple nodes are allowed to start from the same installation
# location to disable it, set the following:
#node.max_local_storage_nodes: 1

#################################### Table ####################################

# You can set a number of options (such as shard/replica options, mapping
# or analyzer definitions, translog settings, ...) for tables globally,
# in this file.
#
# Note, that it makes more sense to configure table settings specifically for
# a certain table when creating it.

# Set the number of shards (splits) of a table (5 by default):
#
#index.number_of_shards: 5

# Set the number of replicas (additional copies) of a table (1 by default):
#
#index.number_of_replicas: 1

# Note, that for development on a local machine, with small tables, it usually
# makes sense to "disable" the distributed features:
#
#index.number_of_shards: 1
#index.number_of_replicas: 0

# Set the refresh interval of a shard in milliseconds.
#
#index.refresh_interval: 1000

# Disable/enable read-only table.
#
#index.blocks.read_only: false

# Disable/enable all the read operations.
#
#index.blocks.read: false

# Disable/enable all the write operations.
#
#index.blocks.write: false

# Disables/enables the table settings modifications.
#
#index.blocks.metadata: false

# Set the number of operations before flushing.
#
#index.translog.flush_threshold_ops: unlimited

# Sets size of transaction log prior to flushing.
#
#index.translog.flush_threshold_size: 200mb

# Sets period of no flushing after which force flush occurs.
#
#index.translog.flush_threshold_period: 30m

# Disable/enable flushing.
# Recommended to use only for small periods of time
#
#index.translog.disable_flush: false

# Controls shard allocation for a specific table.
#
#index.routing.allocation.enable: all

# Controls the total number of shards (replicas and primaries) allowed to be allocated on a single node.
#
#index.routing.allocation.total_shards_per_node: -1

# When using local gateway a particular shard is recovered only if there can be allocated quorum of it’s copies in the cluster.
#
#index.recovery.initial_shards: quorum

#disable/enable table warming. Table warming allows to run registered queries to warm up the table before it is available.
#
#index.warmer.enabled:true

# These settings directly affect the performance of table and search operations
# in your cluster. Assuming you have enough machines to hold shards and
# replicas, the rule of thumb is:
#
# 1. Having more *shards* enhances the _indexing_ performance and allows to
#    _distribute_ a big table across machines.
# 2. Having more *replicas* enhances the _search_ performance and improves the
#    cluster _availability_.
#
# The "number_of_shards" is a one-time setting for a table.
#
# Crate takes care about load balancing, relocating, gathering the
# results from nodes, etc. Experiment with different settings to fine-tune
# your setup.

# Use the Table Status API (<http://localhost:4200/A/_status>) to inspect
# the table status.


#################################### Paths ####################################

# Path to directory containing configuration (this file and logging.yml):
#
#path.conf: /path/to/conf

# Path to directory where to store table data allocated for this node.
#
#path.data: /path/to/data
#
# Can optionally include more than one location, causing data to be striped across
# the locations (a la RAID 0) on a file level, favouring locations with most free
# space on creation. For example:
#
#path.data: /path/to/data1,/path/to/data2

# Path to temporary files:
#
#path.work: /path/to/work

# Path to log files:
#
#path.logs: /path/to/logs

# Path to where plugins are installed:
#
#path.plugins: /path/to/plugins


#path:
#  logs: /var/log/crate
#  data: /var/lib/crate


#################################### Plugin ###################################

# If a plugin listed here is not installed for current node, the node will not start.
#
#plugin.mandatory: mapper-attachments,lang-groovy


################################### Memory ####################################

# Crate performs poorly when JVM starts swapping: you should ensure that
# it _never_ swaps.
#
# Set this property to true to lock the memory:
#
#bootstrap.mlockall: true

# Make sure that the machine has enough memory to allocate for Crate, leaving
# enough memory for the operating system itself.
# You can allocate memory for Crate as follows:
#  - Set CRATE_MIN_MEM and CRATE_MAX_MEM environment variables
#    (We recommend to set MIN and MAX to the same value).
#  - Set CRATE_HEAP_SIZE environment varaible. This sets MIN and MAX to the
#    same value for you.
#
# You should also make sure that the Crate process is allowed to lock
{'fraction_non_alphanumeric': 0.13432062966031483, 'fraction_numerical': 0.005903065451532726, 'mean_word_length': 4.532225723288456, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2956880', 'n_tokens_mistral': 5512, 'n_tokens_neox': 5303, 'n_words': 2391}