You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/developer/advanced/running-elasticsearch.asciidoc
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,10 @@ This will run a snapshot of {es} that is usually built nightly. Read more about
13
13
----
14
14
yarn es snapshot
15
15
----
16
+
By default, two users are added to Elasticsearch:
17
+
18
+
- A superuser with username: `elastic` and password: `changeme`, which can be used to log into Kibana with.
19
+
- A user with username: `kibana_system` and password `changeme`. This account is used by the Kibana server to authenticate itself to Elasticsearch, and to perform certain actions on behalf of the end user. These credentials should be specified in your kibana.yml as described in <<using-kibana-with-security>>
16
20
17
21
See all available options, like how to specify a specific license, with the `--help` flag.
18
22
@@ -115,4 +119,4 @@ PUT _cluster/settings
115
119
}
116
120
----
117
121
118
-
Follow the cross-cluster search instructions for setting up index patterns to search across clusters (<<management-cross-cluster-search>>).
122
+
Follow the cross-cluster search instructions for setting up index patterns to search across clusters (<<management-cross-cluster-search>>).
* Verify your geospatial data is correctly mapped as {ref}/geo-point.html[geo_point] or {ref}/geo-shape.html[geo_shape].
27
+
** Run `GET myIndexPatternTitle/_field_caps?fields=myGeoFieldName` in <<console-kibana, Console>>, replacing `myIndexPatternTitle` and `myGeoFieldName` with your index pattern title and geospatial field name.
28
+
** Ensure response specifies `type` as `geo_point` or `geo_shape`.
29
+
* Verify your geospatial data is correctly mapped in your <<managing-fields, Kibana index pattern>>.
30
+
** Open your index pattern in <<management, Stack Management>>.
31
+
** Ensure your geospatial field type is `geo_point` or `geo_shape`.
32
+
** Ensure your geospatial field is searchable and aggregatable.
33
+
** If your geospatial field type does not match your Elasticsearch mapping, click the *Refresh* button to refresh the field list from Elasticsearch.
34
+
* Index patterns with thousands of fields can exceed the default maximum payload size.
35
+
Increase <<settings, `server.maxPayloadBytes`>> for large index patterns.
0 commit comments