From 852eeb106d3aca4ca1a0db1a7c934dceafec0f0c Mon Sep 17 00:00:00 2001 From: David Roberts Date: Tue, 3 Jan 2017 17:12:14 +0000 Subject: [PATCH] Remove obsolete test files Original commit: elastic/x-pack-elasticsearch@d708431007a1e94de7332da5ca2fffb5e775d447 --- .../settings/all_comment_engine_api.yml | 0 .../resources/settings/empty_engine_api.yml | 0 .../resources/settings/invalid_engine_api.yml | 15 ------ .../resources/settings/valid_engine_api.yml | 47 ------------------- 4 files changed, 62 deletions(-) delete mode 100644 elasticsearch/src/test/resources/settings/all_comment_engine_api.yml delete mode 100644 elasticsearch/src/test/resources/settings/empty_engine_api.yml delete mode 100644 elasticsearch/src/test/resources/settings/invalid_engine_api.yml delete mode 100644 elasticsearch/src/test/resources/settings/valid_engine_api.yml diff --git a/elasticsearch/src/test/resources/settings/all_comment_engine_api.yml b/elasticsearch/src/test/resources/settings/all_comment_engine_api.yml deleted file mode 100644 index e69de29bb2d..00000000000 diff --git a/elasticsearch/src/test/resources/settings/empty_engine_api.yml b/elasticsearch/src/test/resources/settings/empty_engine_api.yml deleted file mode 100644 index e69de29bb2d..00000000000 diff --git a/elasticsearch/src/test/resources/settings/invalid_engine_api.yml b/elasticsearch/src/test/resources/settings/invalid_engine_api.yml deleted file mode 100644 index 1e863da29da..00000000000 --- a/elasticsearch/src/test/resources/settings/invalid_engine_api.yml +++ /dev/null @@ -1,15 +0,0 @@ -es.cluster.name: prelert : this is invalid because there are two unquoted colons - -# Which host is the Elasticsearch node we'll connect to running on? -# es.host: localhost - -# HTTP port for Elasticsearch's REST API -# es.http.port: 9200 - -# TCP port range for Elasticsearch's transport protocol -# es.transport.tcp.port: 9300-9400 - -# Override determination of the number of processors on the machine (for the -# purpose of deciding thread pool sizes) -# es.processors: 4 - diff --git a/elasticsearch/src/test/resources/settings/valid_engine_api.yml b/elasticsearch/src/test/resources/settings/valid_engine_api.yml deleted file mode 100644 index a8ed06ad75f..00000000000 --- a/elasticsearch/src/test/resources/settings/valid_engine_api.yml +++ /dev/null @@ -1,47 +0,0 @@ -jetty.home: somewhere/jetty - -# ------------------------------------------------------------------------------ -# These settings relate to scalability/resource usage limits - -# Maximum number of anomaly records to be stored per bucket per job -# max.anomaly.records: 500 - -# Maximum number of active jobs per processor on the machine -max.jobs.factor: 6.0 - -# How often to update usage statistics (in seconds) -# usage.update.interval: 300 - -# ------------------------------------------------------------------------------ -# These settings relate to validation/rejection of suspect input - -# Reject a data upload when this percentage of records have unparseable dates -max.percent.date.errors: 26 - -# Reject a data upload when this percentage of records arrive with times outside -# the declared latency window -# max.percent.outoforder.errors: 25 - -# ------------------------------------------------------------------------------ -# These settings relate to the Elasticsearch that we're storing our results in - -# Should we use the Elasticsearch Node Client (es-node) or Transport Client -# (es-transport) to connect to the Elasticsearch cluster that stores the results? -# results.storage.client: es-node - -# Elasticsearch cluster name -# es.cluster.name: prelert - -# Which host is the Elasticsearch node we'll connect to running on? -# es.host: localhost - -# HTTP port for Elasticsearch's REST API -# es.http.port: 9200 - -# TCP port range for Elasticsearch's transport protocol -es.transport.tcp.port: 9300-9400 - -# Override determination of the number of processors on the machine (for the -# purpose of deciding thread pool sizes) -# es.processors: 4 -