Mapper: date type to also allow providing values in numeric (milliseconds since epoch)
#516
Labels
Comments
|
Mapper: |
medcl
pushed a commit
to medcl/elasticsearch
that referenced
this issue
Jul 1, 2011
…econds since epoch), closes elastic#516.
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
* Bump to 6.0.0 * This switches our URI objects to the new SafeURI object which makes not leaking users/passwords easy. * Switches the proxy type to use the SafeURI type. This means that hashes * can no longer be used as proxy configs. This is a breaking change. * Fixes many tests that broke with the SafeURI change to be less flimsy * Shares URL normalization logic between the pool and the http client. * Cleanup path handling to not have double /s when joining to URLs with path set * Fix HEAD/:head discrepancy in specs, handle nil paths Fixes elastic#517 Fixes elastic#516 Fixes elastic#517 Fixes elastic#450
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On top of supporting dates formatted as string, also support providing the values as milliseconds since epoch value.
The text was updated successfully, but these errors were encountered: