# Mapping issue about date in elasticsearch 2.3.3

**URL:** <https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092>\
**Category:** Elasticsearch\
**Created:** [June 17, 2016, 5:57am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092 "2016-06-17T05:57:14Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sunil\_G.C](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@Sunil\_G.C](https://discuss.elastic.co/u/Sunil_G.C)\
**Post date:** [June 17, 2016, 5:57am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/1 "2016-06-17T05:57:14Z")

</div>

After upgrading **elasticsearch** to 2.3.3 i have mapping as:

" **startDate**": {  
"type": "date"  
},

" **endDate**" : {  
"type": "date"  
}

While writing on ES through hadoop,hadoop job failed with log as:  
`org.apache.hadoop.mapred.YarnChild: Exception running child : java.lang.RuntimeException: Error while indexing: failure in bulk execution:MapperParsingException[failed to parse [endDate]]; nested: IllegalArgumentException[Invalid format: "253402214400000" is malformed at "02214400000" MapperParsingException[failed to parse [endDate]]; nested: IllegalArgumentException[Invalid format: "253402214400000" is malformed at "02214400000"]; MapperParsingException[failed to parse [endDate]]; nested: IllegalArgumentException[Invalid format: "253402214400000" is malformed at "02214400000"]; MapperParsingException[failed to parse [endDate]]; nested: IllegalArgumentException[Invalid format: "253402214400000" is malformed at "02214400000"]; MapperParsingException[failed to parse [endDate]]; nested: IllegalArgumentException[Invalid format: "253402214400000" is malformed at "02214400000"]; MapperParsingException[failed to parse [endDate]]; nested: IllegalArgumentException[Invalid format: "253402214400000" is malformed at "02214400000"];`

If i change **endDate** type to long it works. Both **startDate** and **endDate** have same type of value and mapping, **startDate** doesn't have this issue. What might be the reason behind the issue?

---

<div class="post-metadata">

**Author:** ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)\
**Post date:** [June 17, 2016, 6:19am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/2 "2016-06-17T06:19:01Z")

</div>

The reason might be the field values.

Any idea what they were?

---

<div class="post-metadata">

**Author:** ![Sunil\_G.C](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@Sunil\_G.C](https://discuss.elastic.co/u/Sunil_G.C)\
**Post date:** [June 17, 2016, 6:57am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/3 "2016-06-17T06:57:05Z")

</div>

Fields value are date eg. 2016-06-14.

---

<div class="post-metadata">

**Author:** ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)\
**Post date:** [June 17, 2016, 12:54pm UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/4 "2016-06-17T12:54:45Z")

</div>

Yes. It's clearly a date field.

What is the value that causes the exception?

---

<div class="post-metadata">

**Author:** ![Sunil\_G.C](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@Sunil\_G.C](https://discuss.elastic.co/u/Sunil_G.C)\
**Post date:** [June 24, 2016, 8:23am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/6 "2016-06-24T08:23:14Z")

</div>

Exception was due to date field value 9999. In Es 2.3.3 it is mention that it only support date up to [2286.Is](http://2286.Is) there any way to make es 2.3.3 support date up to 9999?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 24, 2016, 8:45am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/7 "2016-06-24T08:45:19Z")

</div>

Why are you setting a date in 9999?

---

<div class="post-metadata">

**Author:** ![Sunil\_G.C](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@Sunil\_G.C](https://discuss.elastic.co/u/Sunil_G.C)\
**Post date:** [June 24, 2016, 9:57am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/8 "2016-06-24T09:57:15Z")

</div>

Data from vendor have future date value 9999.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 24, 2016, 10:11am UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/9 "2016-06-24T10:11:21Z")

</div>

Well. Change this before sending that to elasticsearch. Put it to `null` instead (don't provide the date).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:40pm UTC](https://discuss.elastic.co/t/mapping-issue-about-date-in-elasticsearch-2-3-3/53092/10 "2017-07-05T22:40:46Z")

</div>