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

Unable to update index_pattern with newly added fields. #89387

Open
lanerjo opened this issue Jan 27, 2021 · 2 comments
Open

Unable to update index_pattern with newly added fields. #89387

lanerjo opened this issue Jan 27, 2021 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@lanerjo
Copy link

lanerjo commented Jan 27, 2021

Kibana version:
7.9.1
Elasticsearch version:
7.9.1
Server OS version:
Rhel 7
Browser version:
Any

Original install method (e.g. download page, yum, from source, etc.):
Yum
Describe the bug:
Field (visit.account.details.serviceSubscriptions.voice) is type:keyword
New index created with new mapping (data exists in this field)
Refresh index pattern in Kibana
Field shows temporarily, but unable to aggregate by field

Screenshots (if relevant):
Immediately after refreshing index pattern:
Field appears
image

No cached mapping for newly added fields:
image

Unable to aggregate by newly added field:
image

After hard refresh of browser field no longer appears...
image

@lanerjo lanerjo added the bug Fixes for quality problems that affect the customer experience label Jan 27, 2021
@lanerjo
Copy link
Author

lanerjo commented Feb 11, 2021

upon further inspection I am seeing the following error in kibana logs when trying to refresh the index pattern:

{"type":"error","@timestamp":"2021-02-11T17:15:51Z","tags":[],"pid":16,"level":"error","error":{"message":"Internal Server Error","name":"Error","stack":"Error: Internal Server Error\n at HapiResponseAdapter.toError (/usr/share/kibana/src/core/server/http/router/response_adapter.js:132:19)\n at HapiResponseAdapter.toHapiResponse (/usr/share/kibana/src/core/server/http/router/response_adapter.js:86:19)\n at HapiResponseAdapter.handle (/usr/share/kibana/src/core/server/http/router/response_adapter.js:81:17)\n at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:162:34)\n at process._tickCallback (internal/process/next_tick.js:68:7)"},"url":{"protocol":null,"slashes":null,"auth":null,"host":null,"port":null,"hostname":null,"hash":null,"search":null,"query":{},"pathname":"/api/saved_objects/index-pattern/8be439c0-cd83-11e8-8da8-33f92a7b1a47","path":"/api/saved_objects/index-pattern/8be439c0-cd83-11e8-8da8-33f92a7b1a47","href":"/api/saved_objects/index-pattern/8be439c0-cd83-11e8-8da8-33f92a7b1a47"},"message":"Internal Server Error"}

@HoyluBert
Copy link

I am experiencing the same error. Did you ever find a solution for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

No branches or pull requests

2 participants