Can't create a visualization in Kibana (no compatible fields) - but I have compatible fields
up vote
0
down vote
favorite
I'd appreciate any help with this, I'm really stuck.
I am trying to create a simple visualization in Kibana, a line graph based on a number value in my data (origin_file_size_bytes). When I try to add a Visualization graph, I get this error:
No Compatible Fields: The "test*" index pattern does not contain any of the following field types: number or date
My actual index does contain a field with number, as does my data.
Thank you for any help!
Andrew
Here's a sample entry from the Discover Menu:
{
"_index": "lambda-index",
"_type": "lambda-type",
"_id": "LC08_L1TP_166077.TIF",
"_version": 1,
"_score": 2,
"_source": {.
"metadata_processed": {
"BOOL": true.
},
"origin_file_name": {
"S": "LC08_L1TP_166077.TIF"
},
"origin_file_size_bytes": {
"N": "61667800"
}
}
}
My Index pattern classifies as a string, even though it isn't:
origin_file_size_bytes.N string
elasticsearch kibana asked Nov 12 at 2:16
Andrew6850
185
add a comment |
up vote
0
down vote
favorite
I'd appreciate any help with this, I'm really stuck.
I am trying to create a simple visualization in Kibana, a line graph based on a number value in my data (origin_file_size_bytes). When I try to add a Visualization graph, I get this error:
No Compatible Fields: The "test*" index pattern does not contain any of the following field types: number or date
My actual index does contain a field with number, as does my data.
Thank you for any help!
Andrew
Here's a sample entry from the Discover Menu:
{
"_index": "lambda-index",
"_type": "lambda-type",
"_id": "LC08_L1TP_166077.TIF",
"_version": 1,
"_score": 2,
"_source": {.
"metadata_processed": {
"BOOL": true.
},
"origin_file_name": {
"S": "LC08_L1TP_166077.TIF"
},
"origin_file_size_bytes": {
"N": "61667800"
}
}
}
My Index pattern classifies as a string, even though it isn't:
origin_file_size_bytes.N string
elasticsearch kibana asked Nov 12 at 2:16
Andrew6850
185
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'd appreciate any help with this, I'm really stuck.
I am trying to create a simple visualization in Kibana, a line graph based on a number value in my data (origin_file_size_bytes). When I try to add a Visualization graph, I get this error:
No Compatible Fields: The "test*" index pattern does not contain any of the following field types: number or date
My actual index does contain a field with number, as does my data.
Thank you for any help!
Andrew
Here's a sample entry from the Discover Menu:
{
"_index": "lambda-index",
"_type": "lambda-type",
"_id": "LC08_L1TP_166077.TIF",
"_version": 1,
"_score": 2,
"_source": {.
"metadata_processed": {
"BOOL": true.
},
"origin_file_name": {
"S": "LC08_L1TP_166077.TIF"
},
"origin_file_size_bytes": {
"N": "61667800"
}
}
}
My Index pattern classifies as a string, even though it isn't:
origin_file_size_bytes.N string
elasticsearch kibana asked Nov 12 at 2:16
Andrew6850
185
I'd appreciate any help with this, I'm really stuck.
I am trying to create a simple visualization in Kibana, a line graph based on a number value in my data (origin_file_size_bytes). When I try to add a Visualization graph, I get this error:
No Compatible Fields: The "test*" index pattern does not contain any of the following field types: number or date
My actual index does contain a field with number, as does my data.
Thank you for any help!
Andrew
Here's a sample entry from the Discover Menu:
{
"_index": "lambda-index",
"_type": "lambda-type",
"_id": "LC08_L1TP_166077.TIF",
"_version": 1,
"_score": 2,
"_source": {.
"metadata_processed": {
"BOOL": true.
},
"origin_file_name": {
"S": "LC08_L1TP_166077.TIF"
},
"origin_file_size_bytes": {
"N": "61667800"
}
}
}
My Index pattern classifies as a string, even though it isn't:
origin_file_size_bytes.N string
elasticsearch kibana elasticsearch kibana asked Nov 12 at 2:16
Andrew6850
185
asked Nov 12 at 2:16
Andrew6850
185
asked Nov 12 at 2:16
Andrew6850
185
asked Nov 12 at 2:16
Andrew6850
185
asked Nov 12 at 2:16
Andrew6850
185
185
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
You cannot aggregate on a string field. As seen from the screenshot above, your field has been indexed as string and NOT as a number. Elasticsearch dynamically determines mapping type of data if it is not explicitly defined. Since, you ingested the field as a string ES determined, correctly, that the field is of type string. See this link.
For ex. if you run the below to index a document with 2 fields as shown without an explicit mapping, ES creates message field as type 'string' and size field as type 'number' (long)
POST my_index_doc1
{
"message": "100",
"size": 100
}
Index your field into ES as a number instead and you should able to aggregate on it.
answered Nov 12 at 4:03
ben5556
1,602139
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
1
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You cannot aggregate on a string field. As seen from the screenshot above, your field has been indexed as string and NOT as a number. Elasticsearch dynamically determines mapping type of data if it is not explicitly defined. Since, you ingested the field as a string ES determined, correctly, that the field is of type string. See this link.
For ex. if you run the below to index a document with 2 fields as shown without an explicit mapping, ES creates message field as type 'string' and size field as type 'number' (long)
POST my_index_doc1
{
"message": "100",
"size": 100
}
Index your field into ES as a number instead and you should able to aggregate on it.
answered Nov 12 at 4:03
ben5556
1,602139
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
1
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
add a comment |
up vote
1
down vote
accepted
You cannot aggregate on a string field. As seen from the screenshot above, your field has been indexed as string and NOT as a number. Elasticsearch dynamically determines mapping type of data if it is not explicitly defined. Since, you ingested the field as a string ES determined, correctly, that the field is of type string. See this link.
For ex. if you run the below to index a document with 2 fields as shown without an explicit mapping, ES creates message field as type 'string' and size field as type 'number' (long)
POST my_index_doc1
{
"message": "100",
"size": 100
}
Index your field into ES as a number instead and you should able to aggregate on it.
answered Nov 12 at 4:03
ben5556
1,602139
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
1
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You cannot aggregate on a string field. As seen from the screenshot above, your field has been indexed as string and NOT as a number. Elasticsearch dynamically determines mapping type of data if it is not explicitly defined. Since, you ingested the field as a string ES determined, correctly, that the field is of type string. See this link.
For ex. if you run the below to index a document with 2 fields as shown without an explicit mapping, ES creates message field as type 'string' and size field as type 'number' (long)
POST my_index_doc1
{
"message": "100",
"size": 100
}
Index your field into ES as a number instead and you should able to aggregate on it.
answered Nov 12 at 4:03
ben5556
1,602139
You cannot aggregate on a string field. As seen from the screenshot above, your field has been indexed as string and NOT as a number. Elasticsearch dynamically determines mapping type of data if it is not explicitly defined. Since, you ingested the field as a string ES determined, correctly, that the field is of type string. See this link.
For ex. if you run the below to index a document with 2 fields as shown without an explicit mapping, ES creates message field as type 'string' and size field as type 'number' (long)
POST my_index_doc1
{
"message": "100",
"size": 100
}
Index your field into ES as a number instead and you should able to aggregate on it.
answered Nov 12 at 4:03
ben5556
1,602139
answered Nov 12 at 4:03
ben5556
1,602139
answered Nov 12 at 4:03
ben5556
1,602139
answered Nov 12 at 4:03
ben5556
1,602139
1,602139
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
1
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
add a comment |
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
1
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Thank you! I started researching how to do this without deleting and recreating my index but haven’t found a clear answer yet. Maybe there’s a way to create an additional index. I will keep looking. Thanks!
– Andrew6850
Nov 12 at 11:14
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Starting to make a little progress! I created a new index per these instructions, I created each mapping b hand (text and integers) elastic.co/guide/en/elasticsearch/reference/current/…. The index appears correct now, but I can't create a new index pattern (required for the visualization). Still researching.
– Andrew6850
Nov 12 at 18:40
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
Let me know if you are stuck! Glad to help
– ben5556
Nov 12 at 19:21
1
1
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
Thank you for putting me on the right track! The root cause was my input data. My input data was sent as nested JSON, so the nested pieces were interpreted as strings even when they contained numbers. I fixed this by creating a new index, and then changing what I sent to Elasticsearch. Thanks again!
– Andrew6850
Nov 13 at 0:25
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255217%2fcant-create-a-visualization-in-kibana-no-compatible-fields-but-i-have-compa%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
