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

Kibana less tolerant than Elasticsearch #1620

Closed
jimmyjones2 opened this issue Oct 9, 2014 · 1 comment
Closed

Kibana less tolerant than Elasticsearch #1620

jimmyjones2 opened this issue Oct 9, 2014 · 1 comment
Labels
notabug When the issue is closed this label Indicates that it wasn't a bug

Comments

@jimmyjones2
Copy link
Contributor

Inserting the following document (note missing quote around count):

curl -XPUT 'http://localhost:9200/test/record/1' -d '
{ "@timestamp": "2014-02-28T23:13:20Z",
  count: 1024
}'

results in a Fatal Error in the Kibana 4 Discover page. Not really sure why Elasticsearch accepted it (YAML hangover?), but if Elasticsearch is happy, maybe Kibana should be too?

@rashidkpc rashidkpc added the notabug When the issue is closed this label Indicates that it wasn't a bug label Oct 9, 2014
@rashidkpc
Copy link
Contributor

While Elasticsearch does not require valid JSON, Kibana does. This is simply the behavior of the javascript JSON parser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notabug When the issue is closed this label Indicates that it wasn't a bug
Projects
None yet
Development

No branches or pull requests

2 participants