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

Add millisecond parser for dynamic date fields mapped from "yyyy/MM/dd" #12977

Merged
merged 1 commit into from Aug 19, 2015

Conversation

Projects
None yet
5 participants
@jasontedor
Member

jasontedor commented Aug 19, 2015

Dynamic date fields mapped from dates of the form "yyyy-MM-dd"
automatically receive the millisecond paresr epoch_millis as an
alternative parsing format. However, dynamic date fields mapped from
dates of the form "yyyy/MM/dd" do not. This is a bug since the migration
documentation currently specifies that a dynamically added date field,
by default, includes the epoch_millis format. This commit adds
epoch_millis as an alternative parser to dynamic date fields mapped from
dates of the form "yyyy/MM/dd".

Closes #12873

Add millisecond parser for dynamic date fields mapped from "yyyy/MM/dd"
Dynamic date fields mapped from dates of the form "yyyy-MM-dd"
automatically receive the millisecond paresr epoch_millis as an
alternative parsing format. However, dynamic date fields mapped from
dates of the form "yyyy/MM/dd" do not. This is a bug since the migration
documentation currently specifies that a dynamically added date field,
by default, includes the epoch_millis format. This commit adds
epoch_millis as an alternative parser to dynamic date fields mapped from
dates of the form "yyyy/MM/dd".

Closes #12873
@rjernst

This comment has been minimized.

Show comment
Hide comment
@rjernst

rjernst Aug 19, 2015

Member

LGTM

Member

rjernst commented Aug 19, 2015

LGTM

jasontedor added a commit that referenced this pull request Aug 19, 2015

Merge pull request #12977 from jasontedor/fix/12873
Add millisecond parser for dynamic date fields mapped from "yyyy/MM/dd"

@jasontedor jasontedor merged commit 66b0e7a into elastic:master Aug 19, 2015

1 check passed

CLA Commit author is a member of Elasticsearch
Details

@jasontedor jasontedor deleted the jasontedor:fix/12873 branch Aug 19, 2015

jasontedor added a commit that referenced this pull request Aug 19, 2015

Add millisecond parser for dynamic date fields mapped from "yyyy/MM/dd"
This commit backports commit 4c9327d,
the fix #12977 for #12873 from master to 2.0.

@jasontedor jasontedor removed the review label Aug 19, 2015

@brwe brwe added v2.0.0-beta1 and removed v2.0.0 labels Aug 21, 2015

@RicherdLee

This comment has been minimized.

Show comment
Hide comment
@RicherdLee

RicherdLee Nov 3, 2015

I use 1.7.2
I set mapping like this
"mappings": {
"enlink_query_record": {
"properties": {
"ordertime": {
"type": "date",
"format": "yyyy/MM/dd HH:mm:ss"
}
}
}
}

when i syn data,the ordertime still display
image
I'm not sure whether it's millisecond parser for dynamic date fields problem。
shoud id change 2.0.0
Thinks

RicherdLee commented Nov 3, 2015

I use 1.7.2
I set mapping like this
"mappings": {
"enlink_query_record": {
"properties": {
"ordertime": {
"type": "date",
"format": "yyyy/MM/dd HH:mm:ss"
}
}
}
}

when i syn data,the ordertime still display
image
I'm not sure whether it's millisecond parser for dynamic date fields problem。
shoud id change 2.0.0
Thinks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment