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

date fields with long values are not properly returned #271

Closed
costin opened this issue Sep 17, 2014 · 0 comments
Closed

date fields with long values are not properly returned #271

costin opened this issue Sep 17, 2014 · 0 comments

Comments

@costin
Copy link
Member

costin commented Sep 17, 2014

ES accepts date fields to have long values (representing the UTC milliseconds since the epoch, regardless of the format it can handle) yet when being returned the value is returned raw, not in ISO 8601 format which leads to incorrect dates.

costin added a commit that referenced this issue Sep 20, 2014
This fine-tunes the conversion as one can tell whether the source is a
number of String, which makes a difference for dates for example.
Additionally, where possible the underlying JSON parser is used to
perform the conversion to leverage the JSON context.

Relates #271
@costin costin closed this as completed in f936eb4 Sep 20, 2014
costin added a commit that referenced this issue Sep 20, 2014
costin added a commit that referenced this issue Sep 20, 2014
This fine-tunes the conversion as one can tell whether the source is a
number of String, which makes a difference for dates for example.
Additionally, where possible the underlying JSON parser is used to
perform the conversion to leverage the JSON context.

Relates #271

(cherry picked from commit 8984fc3)
costin added a commit that referenced this issue Sep 20, 2014
Relates #271

(cherry picked from commit e230951)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant