# Problem with far future millisecond values for Date type

**URL:** <https://discuss.elastic.co/t/problem-with-far-future-millisecond-values-for-date-type/47966>\
**Category:** Elasticsearch\
**Created:** [April 20, 2016, 8:53pm UTC](https://discuss.elastic.co/t/problem-with-far-future-millisecond-values-for-date-type/47966 "2016-04-20T20:53:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_Ritchie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruce_ritchie/32/9370_2.png) [@Bruce\_Ritchie](https://discuss.elastic.co/u/Bruce_Ritchie)\
**Post date:** [April 20, 2016, 8:53pm UTC](https://discuss.elastic.co/t/problem-with-far-future-millisecond-values-for-date-type/47966/1 "2016-04-20T20:53:37Z")

</div>

This used to work in 1.3.4 but currently in 2.3.1 this seems to have broken.

```
 curl -XPUT http://localhost:9200/test -d '{
  "mappings": {
    "my_type": {
      "properties": {
        "date": {
          "type": "date"
        }
      }
    }
  }
}'

```

`curl -XPUT http://localhost:9200/test/my_type/2 -d '{"date" : 999999999999}'`

{"\_index":"test","\_type":"my\_type","\_id":"2","\_version":1,"\_shards":{"total":1,"successful":1,"failed":0},"created":true}

`curl -XPUT http://localhost:9200/test/my_type/3 -d '{"date" : 10000000000000}'`  
or for my exact data  
`curl -XPUT http://localhost:9200/test/my_type/3 -d '{"date" : 32603904000000}'`

[2016-04-20 13:44:27,278][DEBUG][action.index] [VeevaNetworkNode1] failed to execute [index {[test][my\_type][3], source[{"date" : 32603904000000}]}] on [[test][4]]  
MapperParsingException[failed to parse [date]]; nested: IllegalArgumentException[Invalid format: "32603904000000" is malformed at "3904000000"];  
at org.elasticsearch.index.mapper.FieldMapper.parse(FieldMapper.java:329)  
at org.elasticsearch.index.mapper.DocumentParser.parseObjectOrField(DocumentParser.java:309)  
at org.elasticsearch.index.mapper.DocumentParser.parseValue(DocumentParser.java:436)  
at org.elasticsearch.index.mapper.DocumentParser.parseObject(DocumentParser.java:262)  
at org.elasticsearch.index.mapper.DocumentParser.parseDocument(DocumentParser.java:122)  
at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:309)  
at org.elasticsearch.index.shard.IndexShard.prepareIndex(IndexShard.java:580)  
at org.elasticsearch.index.shard.IndexShard.prepareIndexOnPrimary(IndexShard.java:559)  
at org.elasticsearch.action.index.TransportIndexAction.prepareIndexOperationOnPrimary(TransportIndexAction.java:212)  
at org.elasticsearch.action.index.TransportIndexAction.executeIndexRequestOnPrimary(TransportIndexAction.java:224)  
at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:158)  
at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:66)  
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase.doRun(TransportReplicationAction.java:639)  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)  
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:279)  
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:271)  
at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:75)  
at org.elasticsearch.transport.TransportService$4.doRun(TransportService.java:376)  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: java.lang.IllegalArgumentException: Invalid format: "32603904000000" is malformed at "3904000000"  
at org.joda.time.format.DateTimeParserBucket.doParseMillis(DateTimeParserBucket.java:187)  
at org.joda.time.format.DateTimeFormatter.parseMillis(DateTimeFormatter.java:780)  
at org.elasticsearch.index.mapper.core.DateFieldMapper$DateFieldType.parseStringValue(DateFieldMapper.java:362)  
at org.elasticsearch.index.mapper.core.DateFieldMapper.innerParseCreateField(DateFieldMapper.java:528)  
at org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField(NumberFieldMapper.java:241)  
at org.elasticsearch.index.mapper.FieldMapper.parse(FieldMapper.java:321)  
... 21 more

It seems that far future values for millis with anything \> 13 digits it'll fail to parse. Any suggestions?

---

<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:57pm UTC](https://discuss.elastic.co/t/problem-with-far-future-millisecond-values-for-date-type/47966/2 "2017-07-05T22:57:34Z")

</div>