Saved "field" parameter is now invalid. Please select a new field

Hi guys, i'm a newbee on elasticsearch. When i start to "Discover" my new created index, i encountered the problem which shows,

Saved "field" parameter is now invalid. Please select a new field.
Discover: "field" is a required parameter

The details:

TypeError: "field" is a required parameter
at FieldAggParamFactory.FieldAggParam.write (http://linux:5601/bundles/kibana.bundle.js?v=14566:57:28138)
at http://linux:5601/bundles/kibana.bundle.js?v=14566:57:25226
at AggParams.forEach (native)
at AggParamsFactory.AggParams.write (http://linux:5601/bundles/kibana.bundle.js?v=14566:57:25184)
at AggConfigFactory.AggConfig.write (http://linux:5601/bundles/kibana.bundle.js?v=14566:60:14294)
at AggConfigFactory.AggConfig.toDsl (http://linux:5601/bundles/kibana.bundle.js?v=14566:60:15051)
at http://linux:5601/bundles/kibana.bundle.js?v=14566:61:3843
at Array.forEach (native)
at AggConfigsFactory.AggConfigs.toDsl (http://linux:5601/bundles/kibana.bundle.js?v=14566:61:3626)
at http://linux:5601/bundles/kibana.bundle.js?v=14566:55:23680

Below is the settings and mappings i used, which is a very simple index:

"test": {
"aliases": {},
"mappings": {
"testType": {
"properties": {
"all": {
"type": "text"
"timeStampt": {
"type": "date"
"settings": {
"index": {
"creation_date": "1484039622930",
"number_of_shards": "5",
"number_of_replicas": "1",
"uuid": "s56bpgOAQWGZmVL-vpcddw",
"version": {
"created": "5010199"
"provided_name": "test"

And i use "timeStampt" as the "time-field" when creating the index pattern. I found when i click off "Index contains time-based events ", i.e., i just create an index pattern which does not contain time-based event, the issue disappears.

Could anyone provide me some hint?

Hi @xy_xin,

several users have come across this error in Kibana 5.1.1. We are investigating the issue. You can track the progress on github.

Thanks for your information, @weltenwort!

It looks like this might be a slightly different case than the others. That error appears for a variety of reasons, but so far, it's usually because a visualization was using a field that wasn't marked as aggregatable or searchable. I haven't yet come across why it would be thrown on the Discover tab.

Thanks @Stacey_Gammon. I noted the case is indeed like what you said,

but i have no idea why no field is marked as searchable and aggregatable.

I think i got the answer. The error occurs because the time_based field is not searchable and aggregatable. As why the field is not searchable and aggregatable, it is because 1, there're some error when indexing the field which has type "date" (maybe the "format" is wrong, or the field is empty); or 2, after created index and before imported any data, i.e., it is an empty index.


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.