-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Date format not accepted by ES #66
Comments
Can you post your elasticsearch mapping? ISO8601 date ranges should work regardless of the stored format as long as you're storing the field as a date object: curl -XGET 'http://localhost:9200/_mapping?pretty' |
Mapping - https://gist.github.com/Vineeth-Mohan/5525521 "TimeStamp" : { |
Hello @rashidkpc |
This should allow for you to store in one format, but query in the standard ISO8601 format. "TimeStamp" : { |
Hello @rashidkpc - This would mean i have to reindex the whole index just for sake of kibana. And i believe there would be more users who will use the date type. So would it be very hard to specify the date format , may be in config.js |
+1 there are many date types in common use and standard way of using is to map directly in the type or use dynamic which just applies the first match and then the standard types no longer understood |
json: Added json-c as git submodule
…pServer to figure out binding address Closes elastic#66
New fields for quick searches across intermediate flows
…ray, so the parameters ref wouldn't change when the array grew. also fixed isUserEntered calculation, and another inline function (elastic#66) Co-authored-by: mitodrummer <[email protected]>
… on the MVP cluster (#66) * Remove aggregations from events query - 5x speedup on MVP * Add compatibility wrappers * Speed up aggs with execution_hint: 'map' and apply compat wrappers
… on the MVP cluster (#66) * Remove aggregations from events query - 5x speedup on MVP * Add compatibility wrappers * Speed up aggs with execution_hint: 'map' and apply compat wrappers
… on the MVP cluster (#66) * Remove aggregations from events query - 5x speedup on MVP * Add compatibility wrappers * Speed up aggs with execution_hint: 'map' and apply compat wrappers
While using Kibana , i am facing this issue.
The request is going from Kibana as
{"range":{"TimeStamp":{"from":"2013-05-03T02:12:24.043Z","to":"2013-05-03T08:12:24.044Z"}}}
But timestamp in ES is in another format as told in index meta (dd-MM-yyyy HH:mm:ss)
Due to this am getting a
× Oops! TransportSerializationException[Failed to deserialize exception response from stream]
There should be some option to edit the timestamp format
The text was updated successfully, but these errors were encountered: