logstash-input-elasticsearch 4.23.0 → 5.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 330a1fd55cb3fa00918a73dcd41b66e63ce81d6fc79dc68f4209385429e588d4
-  data.tar.gz: 5ba0377bcaaa9b428a4a848e32fff5019353ca7f6b3c8bb77944156d05230d6f
+  metadata.gz: b34b6c6d814152e88f320525ea0bb80bbf1e63ff962e022aaac0a2385dd087b6
+  data.tar.gz: d142df9148ad69bf838d62badeec71382118741938db61e6aad0676bdb918a37
 SHA512:
-  metadata.gz: 8be2dc35edde5b3b83c2c5711941c58c9aa3e45330e3785fef21269af134e13d031e10cdc324cf31e35b6c42a48f215f9ff2e8d58bc3a77fcc0c5a31c2084998
-  data.tar.gz: b0456a0a04f365a34e35d6b8f8040e75a4d9a0f73718a2958f3c87823e5e41a5b04308b8f1710b8d5aa57091015aba273f308c75bd79c61494fecea4baf00d8e
+  metadata.gz: 19b2b1325ded83b5b93966365f855f104ba1881f2c991ffdbe92216e08d12d18a7b3ddd4a14d755f6d55c85c98e00d12ca566188c63706d6db1f0aa5b085048b
+  data.tar.gz: ff5de17e75281d8ddd0be70167f2c4dee0a90eef328c7e486b704e79fe10db7b7108b733f77438386a7abb18d504efbef5aaf7b0f34a6c8edd62791640514b7b

data/CHANGELOG.md

@@ -1,18 +1,10 @@
-## 4.23.0
-  - ES|QL support [#235](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/235)
-
-## 4.22.0
-  - Add "cursor"-like index tracking [#205](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/205)
-
-## 4.21.2
-  - Add elastic-transport client support used in elasticsearch-ruby 8.x [#225](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/225)
-
-## 4.21.1
-  - Fix: prevent plugin crash when hits contain illegal structure [#183](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/183)
-    - When a hit cannot be converted to an event, the input now emits an event tagged with `_elasticsearch_input_failure` with an `[event][original]` containing a JSON-encoded string representation of the entire hit.
-
-## 4.21.0
-  - Add support for custom headers [#217](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/217)
+## 5.0.0
+  - SSL settings that were marked deprecated in version `4.17.0` are now marked obsolete, and will prevent the plugin from starting.
+  - These settings are:
+    - `ssl`, which should bre replaced by `ssl_enabled`
+    - `ca_file`, which should bre replaced by `ssl_certificate_authorities`
+    - `ssl_certificate_verification`, which should bre replaced by `ssl_verification_mode`
+    - [#213](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/213)
 
 ## 4.20.5
   - Add `x-elastic-product-origin` header to Elasticsearch requests [#211](https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/211)

data/docs/index.asciidoc

@@ -48,7 +48,7 @@ This would create an Elasticsearch query with the following format:
       "sort": [ "_doc" ]
     }'
 
-[id="plugins-{type}s-{plugin}-scheduling"]
+
 ==== Scheduling
 
 Input from this plugin can be scheduled to run periodically according to a specific
@@ -93,251 +93,16 @@ The plugin logs a warning when ECS is enabled and `target` isn't set.
 
 TIP: Set the `target` option to avoid potential schema conflicts.
 
-[id="plugins-{type}s-{plugin}-failure-handling"]
-==== Failure handling
-
-When this input plugin cannot create a structured `Event` from a hit result, it will instead create an `Event` that is tagged with `_elasticsearch_input_failure` whose `[event][original]` is a JSON-encoded string representation of the entire hit.
-
-Common causes are:
-
- - When the hit result contains top-level fields that are {logstash-ref}/processing.html#reserved-fields[reserved in Logstash] but do not have the expected shape. Use the <<plugins-{type}s-{plugin}-target>> directive to avoid conflicts with the top-level namespace.
- - When <<plugins-{type}s-{plugin}-docinfo>> is enabled and the docinfo fields cannot be merged into the hit result. Combine <<plugins-{type}s-{plugin}-target>> and <<plugins-{type}s-{plugin}-docinfo_target>> to avoid conflict.
-
-[id="plugins-{type}s-{plugin}-cursor"]
-==== Tracking a field's value across runs
-
-.Technical Preview: Tracking a field's value
-****
-The feature that allows tracking a field's value across runs is in _Technical Preview_.
-Configuration options and implementation details are subject to change in minor releases without being preceded by deprecation warnings.
-****
-
-Some uses cases require tracking the value of a particular field between two jobs.
-Examples include:
-
-* avoiding the need to re-process the entire result set of a long query after an unplanned restart
-* grabbing only new data from an index instead of processing the entire set on each job.
-
-The Elasticsearch input plugin provides the <<plugins-{type}s-{plugin}-tracking_field>> and <<plugins-{type}s-{plugin}-tracking_field_seed>> options.
-When <<plugins-{type}s-{plugin}-tracking_field>> is set, the plugin records the value of that field for the last document retrieved in a run into
-a file. 
-(The file location defaults to <<plugins-{type}s-{plugin}-last_run_metadata_path>>.)
-
-You can then inject this value in the query using the placeholder `:last_value`. 
-The value will be injected into the query before execution, and then updated after the query completes if new data was found.
-
-This feature works best when:
-
-* the query sorts by the tracking field,
-* the timestamp field is added by {es}, and
-* the field type has enough resolution so that two events are unlikely to have the same value.
-
-Consider using a tracking field whose type is https://www.elastic.co/guide/en/elasticsearch/reference/current/date_nanos.html[date nanoseconds].
-If the tracking field is of this data type, you can use an extra placeholder called `:present` to inject the nano-second based value of "now-30s".
-This placeholder is useful as the right-hand side of a range filter, allowing the collection of
-new data but leaving partially-searchable bulk request data to the next scheduled job.
-
-[id="plugins-{type}s-{plugin}-tracking-sample"]
-===== Sample configuration: Track field value across runs
-
-This section contains a series of steps to help you set up the "tailing" of data being written to a set of indices, using a date nanosecond field added by an Elasticsearch ingest pipeline and the `tracking_field` capability of this plugin.
-
-. Create ingest pipeline that adds Elasticsearch's `_ingest.timestamp` field to the documents as `event.ingested`:
-+
-[source, json]
-    PUT _ingest/pipeline/my-pipeline
-    {
-      "processors": [
-              {
-            "script": {
-              "lang": "painless",
-              "source": "ctx.putIfAbsent(\"event\", [:]); ctx.event.ingested = metadata().now.format(DateTimeFormatter.ISO_INSTANT);"
-            }
-          }
-      ]
-    }
-
-[start=2]
-. Create an index mapping where the tracking field is of date nanosecond type and invokes the defined pipeline:
-+
-[source, json]
-    PUT /_template/my_template
-    {
-      "index_patterns": ["test-*"],
-      "settings": {
-        "index.default_pipeline": "my-pipeline",
-      },
-      "mappings": {
-        "properties": {
-          "event": {
-            "properties": {
-              "ingested": {
-                "type": "date_nanos",
-                "format": "strict_date_optional_time_nanos"
-              }
-            }
-          }
-        }
-      }
-    }
-
-[start=3]
-. Define a query that looks at all data of the indices, sorted by the tracking field, and with a range filter since the last value seen until present:
-+
-[source,json]
-{
-  "query": {
-    "range": {
-      "event.ingested": {
-        "gt": ":last_value",
-        "lt": ":present"
-      }
-    }
-  },
-  "sort": [
-    {
-      "event.ingested": {
-        "order": "asc",
-        "format": "strict_date_optional_time_nanos",
-        "numeric_type": "date_nanos"
-      }
-    }
-  ]
-}
-
-[start=4]
-. Configure the Elasticsearch input to query the indices with the query defined above, every minute, and track the `event.ingested` field:
-+
-[source, ruby]
-    input {
-      elasticsearch {
-        id => tail_test_index
-        hosts => [ 'https://..']
-        api_key => '....'
-        index => 'test-*'
-        query => '{ "query": { "range": { "event.ingested": { "gt": ":last_value", "lt": ":present"}}}, "sort": [ { "event.ingested": {"order": "asc", "format": "strict_date_optional_time_nanos", "numeric_type" : "date_nanos" } } ] }'
-        tracking_field => "[event][ingested]"
-        slices => 5 # optional use of slices to speed data processing, should be equal to or less than number of primary shards
-        schedule => '* * * * *' # every minute
-        schedule_overlap => false # don't accumulate jobs if one takes longer than 1 minute
-      }
-    }
-
-With this sample setup, new documents are indexed into a `test-*` index.
-The next scheduled run:
-
-* selects all new documents since the last observed value of the tracking field,
-* uses {ref}/point-in-time-api.html#point-in-time-api[Point in time (PIT)] + {ref}/paginate-search-results.html#search-after[Search after] to paginate through all the data, and
-* updates the value of the field at the end of the pagination.
-
-[id="plugins-{type}s-{plugin}-esql"]
-==== {esql} support
-
-.Technical Preview
-****
-The {esql} feature that allows using ES|QL queries with this plugin is in Technical Preview.
-Configuration options and implementation details are subject to change in minor releases without being preceded by deprecation warnings.
-****
-
-{es} Query Language ({esql}) provides a SQL-like interface for querying your {es} data.
-
-To use {esql}, this plugin needs to be installed in {ls} 8.17.4 or newer, and must be connected to {es} 8.11 or newer.
-
-To configure {esql} query in the plugin, set the `query_type` to `esql` and provide your {esql} query in the `query` parameter.
-
-IMPORTANT: {esql} is evolving and may still have limitations with regard to result size or supported field types. We recommend understanding https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-limitations.html[ES|QL current limitations] before using it in production environments.
-
-The following is a basic scheduled {esql} query that runs hourly:
-[source, ruby]
-    input {
-      elasticsearch {
-        id => hourly_cron_job
-        hosts => [ 'https://..']
-        api_key => '....'
-        query_type => 'esql'
-        query => '
-          FROM food-index
-            | WHERE spicy_level = "hot" AND @timestamp > NOW() - 1 hour
-            | LIMIT 500
-        '
-        schedule => '0 * * * *' # every hour at min 0
-      }
-    }
-
-Set `config.support_escapes: true` in `logstash.yml` if you need to escape special chars in the query.
-
-NOTE: With {esql} query, {ls} doesn't generate `event.original`.
-
-[id="plugins-{type}s-{plugin}-esql-event-mapping"]
-===== Mapping {esql} result to {ls} event
-{esql} returns query results in a structured tabular format, where data is organized into _columns_ (fields) and _values_ (entries).
-The plugin maps each value entry to an event, populating corresponding fields.
-For example, a query might produce a table like:
-
-[cols="2,1,1,1,2",options="header"]
-|===
-|`timestamp` |`user_id` | `action` | `status.code` | `status.desc`
-
-|2025-04-10T12:00:00 |123 |login |200 | Success
-|2025-04-10T12:05:00 |456 |purchase |403 | Forbidden (unauthorized user)
-|===
-
-For this case, the plugin emits two events look like
-[source, json]
-[
-  {
-    "timestamp": "2025-04-10T12:00:00",
-    "user_id": 123,
-    "action": "login",
-    "status": {
-        "code": 200,
-        "desc": "Success"
-    }
-  },
-  {
-    "timestamp": "2025-04-10T12:05:00",
-    "user_id": 456,
-    "action": "purchase",
-    "status": {
-        "code": 403,
-        "desc": "Forbidden (unauthorized user)"
-    }
-  }
-]
-
-NOTE: If your index has a mapping with sub-objects where `status.code` and `status.desc` actually dotted fields, they appear in {ls} events as a nested structure.
-
-[id="plugins-{type}s-{plugin}-esql-multifields"]
-===== Conflict on multi-fields
-
-{esql} query fetches all parent and sub-fields fields if your {es} index has https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/multi-fields[multi-fields] or https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/subobjects[subobjects].
-Since {ls} events cannot contain parent field's concrete value and sub-field values together, the plugin ignores sub-fields with warning and includes parent.
-We recommend using the `RENAME` (or `DROP` to avoid warnings) keyword in your {esql} query explicitly rename the fields to include sub-fields into the event.
-
-This a common occurrence if your template or mapping follows the pattern of always indexing strings as "text" (`field`) + " keyword" (`field.keyword`) multi-field.
-In this case it's recommended to do `KEEP field` if the string is identical and there is only one subfield as the engine will optimize and retrieve the keyword, otherwise you can do `KEEP field.keyword | RENAME field.keyword as field`.
-
-To illustrate the situation with example, assuming your mapping has a time `time` field with `time.min` and `time.max` sub-fields as following:
-[source, ruby]
-    "properties": {
-        "time": { "type": "long" },
-        "time.min": { "type": "long" },
-        "time.max": { "type": "long" }
-    }
-
-The {esql} result will contain all three fields but the plugin cannot map them into {ls} event.
-To avoid this, you can use the `RENAME` keyword to rename the `time` parent field to get all three fields with unique fields.
-[source, ruby]
-    ...
-    query => 'FROM my-index | RENAME time AS time.current'
-    ...
-
-For comprehensive {esql} syntax reference and best practices, see the https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-syntax.html[{esql} documentation].
-
 [id="plugins-{type}s-{plugin}-options"]
 ==== Elasticsearch Input configuration options
 
-This plugin supports the following configuration options plus the <<plugins-{type}s-{plugin}-common-options>> and the <<plugins-{type}s-{plugin}-deprecated-options>> described later.
+This plugin supports these configuration options plus the <<plugins-{type}s-{plugin}-common-options>> described later.
+
+NOTE: As of version `5.0.0` of this plugin, a number of previously deprecated settings related to SSL have been removed.
+Please check out <<plugins-{type}s-{plugin}-obsolete-options>> for details.
+
+NOTE: As of version `5.0.0` of this plugin, a number of previously deprecated settings related to SSL have been removed.
+Please check out <<plugins-{type}s-{plugin}-obsolete-options>> for details.
 
 [cols="<,<,<",options="header",]
 |=======================================================================
@@ -354,15 +119,12 @@ This plugin supports the following configuration options plus the <<plugins-{typ
 | <<plugins-{type}s-{plugin}-ecs_compatibility>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-hosts>> |<<array,array>>|No
 | <<plugins-{type}s-{plugin}-index>> |<<string,string>>|No
-| <<plugins-{type}s-{plugin}-last_run_metadata_path>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-password>> |<<password,password>>|No
 | <<plugins-{type}s-{plugin}-proxy>> |<<uri,uri>>|No
 | <<plugins-{type}s-{plugin}-query>> |<<string,string>>|No
-| <<plugins-{type}s-{plugin}-query_type>> |<<string,string>>, one of `["dsl","esql"]`|No
 | <<plugins-{type}s-{plugin}-response_type>> |<<string,string>>, one of `["hits","aggregations"]`|No
 | <<plugins-{type}s-{plugin}-request_timeout_seconds>> | <<number,number>>|No
 | <<plugins-{type}s-{plugin}-schedule>> |<<string,string>>|No
-| <<plugins-{type}s-{plugin}-schedule_overlap>> |<<boolean,boolean>>|No
 | <<plugins-{type}s-{plugin}-scroll>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-search_api>> |<<string,string>>, one of `["auto", "search_after", "scroll"]`|No
 | <<plugins-{type}s-{plugin}-size>> |<<number,number>>|No
@@ -382,8 +144,6 @@ This plugin supports the following configuration options plus the <<plugins-{typ
 | <<plugins-{type}s-{plugin}-ssl_verification_mode>> |<<string,string>>, one of `["full", "none"]`|No
 | <<plugins-{type}s-{plugin}-socket_timeout_seconds>> | <<number,number>>|No
 | <<plugins-{type}s-{plugin}-target>> | {logstash-ref}/field-references-deepdive.html[field reference] | No
-| <<plugins-{type}s-{plugin}-tracking_field>> |<<string,string>>|No
-| <<plugins-{type}s-{plugin}-tracking_field_seed>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-retries>> | <<number,number>>|No
 | <<plugins-{type}s-{plugin}-user>> |<<string,string>>|No
 |=======================================================================
@@ -563,17 +323,6 @@ Check out {ref}/api-conventions.html#api-multi-index[Multi Indices
 documentation] in the Elasticsearch documentation for info on
 referencing multiple indices.
 
-[id="plugins-{type}s-{plugin}-last_run_metadata_path"]
-===== `last_run_metadata_path`
-
-  * Value type is <<string,string>>
-  * There is no default value for this setting.
-
-The path to store the last observed value of the tracking field, when used.
-By default this file is stored as `<path.data>/plugins/inputs/elasticsearch/<pipeline_id>/last_run_value`.
-
-This setting should point to file, not a directory, and Logstash must have read+write access to this file.
-
 [id="plugins-{type}s-{plugin}-password"]
 ===== `password`
 
@@ -600,35 +349,22 @@ environment variables e.g. `proxy => '${LS_PROXY:}'`.
   * Value type is <<string,string>>
   * Default value is `'{ "sort": [ "_doc" ] }'`
 
-The query to be executed.
-Accepted query shape is DSL or {esql} (when `query_type => 'esql'`).
-Read the {ref}/query-dsl.html[{es} query DSL documentation] or {ref}/esql.html[{esql} documentation] for more information.
+The query to be executed. Read the {ref}/query-dsl.html[Elasticsearch query DSL
+documentation] for more information.
 
 When <<plugins-{type}s-{plugin}-search_api>> resolves to `search_after` and the query does not specify `sort`,
 the default sort `'{ "sort": { "_shard_doc": "asc" } }'` will be added to the query. Please refer to the {ref}/paginate-search-results.html#search-after[Elasticsearch search_after] parameter to know more.
 
-[id="plugins-{type}s-{plugin}-query_type"]
-===== `query_type`
-
-* Value can be `dsl` or `esql`
-* Default value is `dsl`
-
-Defines the <<plugins-{type}s-{plugin}-query>> shape.
-When `dsl`, the query shape must be valid {es} JSON-style string.
-When `esql`, the query shape must be a valid {esql} string and `index`, `size`, `slices`, `search_api`, `docinfo`, `docinfo_target`, `docinfo_fields`, `response_type` and `tracking_field` parameters are not allowed.
-
 [id="plugins-{type}s-{plugin}-response_type"]
 ===== `response_type`
 
-  * Value can be any of: `hits`, `aggregations`, `esql`
+  * Value can be any of: `hits`, `aggregations`
   * Default value is `hits`
 
 Which part of the result to transform into Logstash events when processing the
 response from the query.
-
 The default `hits` will generate one event per returned document (i.e. "hit").
-
-When set to `aggregations`, a single {ls} event will be generated with the
+When set to `aggregations`, a single Logstash event will be generated with the
 contents of the `aggregations` object of the query's response. In this case the
 `hits` object will be ignored. The parameter `size` will be always be set to
 0 regardless of the default or user-defined value set in this plugin.
@@ -667,19 +403,6 @@ for example: "* * * * *" (execute query every minute, on the minute)
 There is no schedule by default. If no schedule is given, then the statement is run
 exactly once.
 
-[id="plugins-{type}s-{plugin}-schedule_overlap"]
-===== `schedule_overlap`
-
-  * Value type is <<boolean,boolean>>
-  * Default value is `true`
-
-Whether to allow queuing of a scheduled run if a run is occurring.
-While this is ideal for ensuring a new run happens immediately after the previous on finishes if there
-is a lot of work to do, but given the queue is unbounded it may lead to an out of memory over long periods of time
-if the queue grows continuously.
-
-When in doubt, set `schedule_overlap` to false (it may become the default value in the future).
-
 [id="plugins-{type}s-{plugin}-scroll"]
 ===== `scroll`
 
@@ -772,6 +495,8 @@ Enable SSL/TLS secured communication to Elasticsearch cluster.
 Leaving this unspecified will use whatever scheme is specified in the URLs listed in <<plugins-{type}s-{plugin}-hosts>> or extracted from the <<plugins-{type}s-{plugin}-cloud_id>>.
 If no explicit protocol is specified plain HTTP will be used.
 
+When not explicitly set, SSL will be automatically enabled if any of the specified hosts use HTTPS.
+
 [id="plugins-{type}s-{plugin}-ssl_key"]
 ===== `ssl_key`
   * Value type is <<path,path>>
@@ -890,28 +615,6 @@ When the `target` is set to a field reference, the `_source` of the hit is place
 This option can be useful to avoid populating unknown fields when a downstream schema such as ECS is enforced.
 It is also possible to target an entry in the event's metadata, which will be available during event processing but not exported to your outputs (e.g., `target \=> "[@metadata][_source]"`).
 
-[id="plugins-{type}s-{plugin}-tracking_field"]
-===== `tracking_field`
-
-* Value type is <<string,string>>
-* There is no default value for this setting.
-
-Which field from the last event of a previous run will be used a cursor value for the following run.
-The value of this field is injected into each query if the query uses the placeholder `:last_value`.
-For the first query after a pipeline is started, the value used is either read from <<plugins-{type}s-{plugin}-last_run_metadata_path>> file,
-or taken from <<plugins-{type}s-{plugin}-tracking_field_seed>> setting.
-
-Note: The tracking value is updated after each page is read and at the end of each Point in Time. In case of a crash the last saved value will be used so some duplication of data can occur. For this reason the use of unique document IDs for each event is recommended in the downstream destination.
-
-[id="plugins-{type}s-{plugin}-tracking_field_seed"]
-===== `tracking_field_seed`
-
-* Value type is <<string,string>>
-* Default value is `"1970-01-01T00:00:00.000000000Z"`
-
-The starting value for the <<plugins-{type}s-{plugin}-tracking_field>> if there is no <<plugins-{type}s-{plugin}-last_run_metadata_path>> already.
-This field defaults to the nanosecond precision ISO8601 representation of `epoch`, or "1970-01-01T00:00:00.000000000Z", given nano-second precision timestamps are the
-most reliable data format to use for this feature.
 
 [id="plugins-{type}s-{plugin}-user"]
 ===== `user`
@@ -924,56 +627,21 @@ option when authenticating to the Elasticsearch server. If set to an
 empty string authentication will be disabled.
 
 
-[id="plugins-{type}s-{plugin}-deprecated-options"]
-==== Elasticsearch Input deprecated configuration options
+[id="plugins-{type}s-{plugin}-obsolete-options"]
+==== Elasticsearch Input Obsolete Configuration Options
 
-This plugin supports the following deprecated configurations.
+WARNING: As of version `5.0.0` of this plugin, some configuration options have been replaced.
+The plugin will fail to start if it contains any of these obsolete options.
 
-WARNING: Deprecated options are subject to removal in future releases.
 
-[cols="<,<,<",options="header",]
+[cols="<,<",options="header",]
 |=======================================================================
-|Setting|Input type|Replaced by
-| <<plugins-{type}s-{plugin}-ca_file>> |a valid filesystem path|<<plugins-{type}s-{plugin}-ssl_certificate_authorities>>
-| <<plugins-{type}s-{plugin}-ssl>> |<<boolean,boolean>>|<<plugins-{type}s-{plugin}-ssl_enabled>>
-| <<plugins-{type}s-{plugin}-ssl_certificate_verification>> |<<boolean,boolean>>|<<plugins-{type}s-{plugin}-ssl_verification_mode>>
+|Setting|Replaced by
+| ca_file | <<plugins-{type}s-{plugin}-ssl_certificate_authorities>>
+| ssl | <<plugins-{type}s-{plugin}-ssl_enabled>>
+| ssl_certificate_verification | <<plugins-{type}s-{plugin}-ssl_verification_mode>>
 |=======================================================================
 
-[id="plugins-{type}s-{plugin}-ca_file"]
-===== `ca_file`
-deprecated[4.17.0, Replaced by <<plugins-{type}s-{plugin}-ssl_certificate_authorities>>]
-
-* Value type is <<path,path>>
-* There is no default value for this setting.
-
-SSL Certificate Authority file in PEM encoded format, must also include any chain certificates as necessary.
-
-[id="plugins-{type}s-{plugin}-ssl"]
-===== `ssl`
-deprecated[4.17.0, Replaced by <<plugins-{type}s-{plugin}-ssl_enabled>>]
-
-* Value type is <<boolean,boolean>>
-* Default value is `false`
-
-If enabled, SSL will be used when communicating with the Elasticsearch
-server (i.e. HTTPS will be used instead of plain HTTP).
-
-
-[id="plugins-{type}s-{plugin}-ssl_certificate_verification"]
-===== `ssl_certificate_verification`
-deprecated[4.17.0, Replaced by <<plugins-{type}s-{plugin}-ssl_verification_mode>>]
-
-* Value type is <<boolean,boolean>>
-* Default value is `true`
-
-Option to validate the server's certificate. Disabling this severely compromises security.
-When certificate validation is disabled, this plugin implicitly trusts the machine
-resolved at the given address without validating its proof-of-identity.
-In this scenario, the plugin can transmit credentials to or process data from an untrustworthy
-man-in-the-middle or other compromised infrastructure.
-More information on the importance of certificate verification:
-**https://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf**.
-
 [id="plugins-{type}s-{plugin}-common-options"]
 include::{include_path}/{type}.asciidoc[]
 

data/lib/logstash/inputs/elasticsearch/aggregation.rb

@@ -12,9 +12,14 @@ module LogStash
           @client = client
           @plugin_params = plugin.params
 
-          @index = @plugin_params["index"]
           @size = @plugin_params["size"]
+          @query = @plugin_params["query"]
           @retries = @plugin_params["retries"]
+          @agg_options = {
+            :index => @plugin_params["index"],
+            :size  => 0
+          }.merge(:body => @query)
+
           @plugin = plugin
         end
 
@@ -28,18 +33,10 @@ module LogStash
           false
         end
 
-        def aggregation_options(query_object)
-          {
-            :index => @index,
-            :size => 0,
-            :body => query_object
-          }
-        end
-
-        def do_run(output_queue, query_object)
+        def do_run(output_queue)
           logger.info("Aggregation starting")
           r = retryable(AGGREGATION_JOB) do
-            @client.search(aggregation_options(query_object))
+            @client.search(@agg_options)
           end
           @plugin.push_hit(r, output_queue, 'aggregations') if r
         end

data/lib/logstash/inputs/elasticsearch/paginated_search.rb

@@ -21,10 +21,9 @@ module LogStash
           @pipeline_id = plugin.pipeline_id
         end
 
-        def do_run(output_queue, query)
-          @query = query
-
+        def do_run(output_queue)
           return retryable_search(output_queue) if @slices.nil? || @slices <= 1
+
           retryable_slice_search(output_queue)
         end
 
@@ -123,13 +122,6 @@ module LogStash
         PIT_JOB = "create point in time (PIT)"
         SEARCH_AFTER_JOB = "search_after paginated search"
 
-        attr_accessor :cursor_tracker
-
-        def do_run(output_queue, query)
-          super(output_queue, query)
-          @cursor_tracker.checkpoint_cursor(intermediate: false) if @cursor_tracker
-        end
-
         def pit?(id)
           !!id&.is_a?(String)
         end
@@ -200,8 +192,6 @@ module LogStash
             end
           end
 
-          @cursor_tracker.checkpoint_cursor(intermediate: true) if @cursor_tracker
-
           logger.info("Query completed", log_details)
         end