Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

K4 docs: Add a note on dynamic mappings #3499

Closed
tbragin opened this issue Apr 1, 2015 · 4 comments
Closed

K4 docs: Add a note on dynamic mappings #3499

tbragin opened this issue Apr 1, 2015 · 4 comments
Assignees

Comments

@tbragin
Copy link
Contributor

tbragin commented Apr 1, 2015

We require that Elasticsearch "dynamic mapping" on fields is enabled (which is the default):
http://www.elastic.co/guide/en/elasticsearch/guide/current/dynamic-mapping.html

If not, the user will manually need to provide mappings for new fields to correct types for Kibana to correctly use them in visualizations.

In addition, dynamic mapping is required for ongoing management of the .kibana index.

@maharg101
Copy link

Could you include the relevant mapping in the documentation please.

@tbragin
Copy link
Contributor Author

tbragin commented Apr 27, 2015

In addition to clarifying that dynamic indexing needs to be enabled for .kibana index on an ongoing basis (which is the default globally), we should document the process for setting dynamic indexing to true just for the .kibana index, if someone chooses to override the global setting. Something like this, maybe:

Assumptions:
* .kibana index does not exist yet
* elasticsearch.yml has the following setting: "index.mapper.dynamic": false

1. Start elasticsearch

2. Create the .kibana index with the dynamic mapping setting set to true:
PUT .kibana
{
  "index.mapper.dynamic": true
}

3. Start kibana, access the web UI - you should not get any error messages related to dynamic mapping. 

@nellicus
Copy link

+1

@palecur
Copy link

palecur commented May 28, 2015

Added to docs in 46ee3ab for PR#3813.

@palecur palecur closed this as completed May 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants