Drop the copied examples, the geoip examples suffice

Author: joegallo

docs/reference/ingest/processors/ip-location.asciidoc

@@ -225,244 +225,3 @@ Which returns:
 }
 --------------------------------------------------
 // TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-[[ingest-geoip-mappings-note]]
-===== Recognizing Location as a Geopoint
-Although this processor enriches your document with a `location` field containing
-the estimated latitude and longitude of the IP address, this field will not be
-indexed as a {ref}/geo-point.html[`geo_point`] type in Elasticsearch without explicitly defining it
-as such in the mapping.
-
-You can use the following mapping for the example index above:
-
-[source,console]
---------------------------------------------------
-PUT my_ip_locations
-{
-  "mappings": {
-    "properties": {
-      "ip_location": {
-        "properties": {
-          "location": { "type": "geo_point" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/ip_location
-{
-  "description" : "Add ip geolocation info",
-  "processors" : [
-    {
-      "ip_location" : {
-        "field" : "ip"
-      }
-    }
-  ]
-}
-
-PUT my_ip_locations/_doc/1?refresh=true&pipeline=ip_location
-{
-  "ip": "89.160.20.128"
-}
-
-GET /my_ip_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "1m",
-          "geoip.location": {
-            "lon": 15.6167,
-            "lat": 58.4167
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 3,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "my_ip_locations",
-        "_id" : "1",
-        "_score" : 1.0,
-        "_source" : {
-          "ip_location" : {
-            "continent_name" : "Europe",
-            "country_name" : "Sweden",
-            "country_iso_code" : "SE",
-            "city_name" : "Linköping",
-            "region_iso_code" : "SE-E",
-            "region_name" : "Östergötland County",
-            "location" : {
-              "lon" : 15.6167,
-              "lat" : 58.4167
-            }
-          },
-          "ip" : "89.160.20.128"
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 3/"took" : $body.took/]
-////
-
-[[manage-geoip-database-updates]]
-==== Manage your own IP geolocation database updates
-
-If you can't <<geoip-automatic-updates,automatically update>> your IP geolocation databases
-from the Elastic endpoint, you have a few other options:
-
-* <<use-proxy-geoip-endpoint,Use a proxy endpoint>>
-* <<use-custom-geoip-endpoint,Use a custom endpoint>>
-* <<manually-update-geoip-databases,Manually update your IP geolocation databases>>
-
-[[use-proxy-geoip-endpoint]]
-**Use a proxy endpoint**
-
-If you can't connect directly to the Elastic GeoIP endpoint, consider setting up
-a secure proxy. You can then specify the proxy endpoint URL in the
-<<ingest-geoip-downloader-endpoint,`ingest.geoip.downloader.endpoint`>> setting
-of each node’s `elasticsearch.yml` file.
-
-In a strict setup the following domains may need to be added to the allowed
-domains list:
-
-* `geoip.elastic.co`
-* `storage.googleapis.com`
-
-[[use-custom-geoip-endpoint]]
-**Use a custom endpoint**
-
-You can create a service that mimics the Elastic GeoIP endpoint. You can then
-get automatic updates from this service.
-
-. Download your `.mmdb` database files from the
-http://dev.maxmind.com/geoip/geoip2/geolite2[MaxMind site].
-
-. Copy your database files to a single directory.
-
-. From your {es} directory, run:
-+
-[source,sh]
-----
-./bin/elasticsearch-geoip -s my/source/dir [-t target/directory]
-----
-
-. Serve the static database files from your directory. For example, you can use
-Docker to serve the files from an nginx server:
-+
-[source,sh]
-----
-docker run -v my/source/dir:/usr/share/nginx/html:ro nginx
-----
-
-. Specify the service's endpoint URL in the
-<<ingest-geoip-downloader-endpoint,`ingest.geoip.downloader.endpoint`>> setting
-of each node’s `elasticsearch.yml` file.
-+
-By default, {es} checks the endpoint for updates every three days. To use
-another polling interval, use the <<cluster-update-settings,cluster update
-settings API>> to set
-<<ingest-geoip-downloader-poll-interval,`ingest.geoip.downloader.poll.interval`>>.
-
-[[manually-update-geoip-databases]]
-**Manually update your IP geolocation databases**
-
-. Use the <<cluster-update-settings,cluster update settings API>> to set
-`ingest.geoip.downloader.enabled` to `false`. This disables automatic updates
-that may overwrite your database changes. This also deletes all downloaded
-databases.
-
-. Download your `.mmdb` database files from the
-http://dev.maxmind.com/geoip/geoip2/geolite2[MaxMind site].
-+
-You can also use custom city, country, and ASN `.mmdb` files. These files must
-be uncompressed. The type (city, country, or ASN) will be pulled from the file
-metadata, so the filename does not matter.
-
-. On {ess} deployments upload database using
-a {cloud}/ec-custom-bundles.html[custom bundle].
-
-. On self-managed deployments copy the database files to `$ES_CONFIG/ingest-geoip`.
-
-. In your `geoip` processors, configure the `database_file` parameter to use a
-custom database file.
-
-[[ingest-geoip-settings]]
-===== Node Settings
-
-The `geoip` processor supports the following setting:
-
-`ingest.geoip.cache_size`::
-
-    The maximum number of results that should be cached. Defaults to `1000`.
-
-Note that these settings are node settings and apply to all `geoip` and `ip_location` processors, i.e. there is a single cache for all such processors.
-
-[[geoip-cluster-settings]]
-===== Cluster settings
-
-[[ingest-geoip-downloader-enabled]]
-`ingest.geoip.downloader.enabled`::
-(<<dynamic-cluster-setting,Dynamic>>, Boolean)
-If `true`, {es} automatically downloads and manages updates for IP geolocation databases
-from the `ingest.geoip.downloader.endpoint`. If `false`, {es} does not download
-updates and deletes all downloaded databases. Defaults to `true`.
-
-[[ingest-geoip-downloader-eager-download]]
-`ingest.geoip.downloader.eager.download`::
-(<<dynamic-cluster-setting,Dynamic>>, Boolean)
-If `true`, {es} downloads IP geolocation databases immediately, regardless of whether a
-pipeline exists with a geoip processor. If `false`, {es} only begins downloading
-the databases if a pipeline with a geoip processor exists or is added. Defaults
-to `false`.
-
-[[ingest-geoip-downloader-endpoint]]
-`ingest.geoip.downloader.endpoint`::
-(<<static-cluster-setting,Static>>, string)
-Endpoint URL used to download updates for IP geolocation databases. For example, `https://myDomain.com/overview.json`.
-Defaults to `https://geoip.elastic.co/v1/database`. {es} stores downloaded database files in
-each node's <<es-tmpdir,temporary directory>> at `$ES_TMPDIR/geoip-databases/<node_id>`.
-Note that {es} will make a GET request to `${ingest.geoip.downloader.endpoint}?elastic_geoip_service_tos=agree`,
-expecting the list of metadata about databases typically found in `overview.json`.
-
-The downloader uses the JDK's builtin cacerts. If you're using a custom endpoint, add the custom https endpoint cacert(s) to the JDK's truststore.
-
-[[ingest-geoip-downloader-poll-interval]]
-`ingest.geoip.downloader.poll.interval`::
-(<<dynamic-cluster-setting,Dynamic>>, <<time-units,time value>>)
-How often {es} checks for IP geolocation database updates at the
-`ingest.geoip.downloader.endpoint`. Must be greater than `1d` (one day). Defaults
-to `3d` (three days).