Skip to content

Commit bf74d38

Browse files
committed
Fix GeoIP custom database directory in docs (#43383)
These docs were misleading for package installations of Elasticsearch. Instead, we should refer to $ES_CONFIG/ingest-geoip as the path to place the custom database files. For non-package installations, this is the same as $ES_HOME/config, but for package installations this is not the case as the config directory for package installations is /etc/elasticsearch, and is not relative to $ES_HOME. This commit corrects the docs.
1 parent d81ce9a commit bf74d38

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/reference/ingest/processors/geoip.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ under the CCA-ShareAlike 4.0 license. For more details see, http://dev.maxmind.c
1010

1111
The `geoip` processor can run with other GeoIP2 databases from Maxmind. The files must be copied into the `ingest-geoip` config directory,
1212
and the `database_file` option should be used to specify the filename of the custom database. Custom database files must be stored
13-
uncompressed. The `ingest-geoip` config directory is located at `$ES_HOME/config/ingest-geoip`.
13+
uncompressed. The `ingest-geoip` config directory is located at `$ES_CONFIG/ingest-geoip`.
1414

1515
[[using-ingest-geoip]]
1616
==== Using the `geoip` Processor in a Pipeline

0 commit comments

Comments
 (0)