Date type automapping in 0.17.5

Looks like auto type mapping is not working for date types in 0.17.5,
it shows up as "string":

# check version
$ elasticsearch -v
ElasticSearch Version: 0.17.5 (2011-08-12T12:13:16), JVM: 20.1-b02

# index something
$ curl -XPOST 'localhost:9200/twitter/tweet/' -d ' { "message" :

"hello world", "post_date" : "2011/08/12 01:23:45" }'

# check mappings
$ curl -XGET http://localhost:9200/twitter/tweet/_mapping?pretty=true

{
  "tweet" : {
    "properties" : {
      "message" : {
        "type" : "string"
      },
      "post_date" : {
        "type" : "string"
      }
    }
  }
}

Try it in 0.17.4:

# check version
$ elasticsearch -v
ElasticSearch Version: 0.17.4 (2011-08-04T20:57:57), JVM: 20.1-b02

# index something
$ curl -XPOST 'localhost:9200/twitter/tweet/' -d ' { "message" :

"hello world", "post_date" : "2011/08/12 01:23:45" }'

# check mappings
$ curl -XGET http://localhost:9200/twitter/tweet/_mapping?pretty=true

{
  "tweet" : {
    "properties" : {
      "message" : {
        "type" : "string"
      },
      "post_date" : {
        "format" : "yyyy/MM/dd HH:mm:ss||yyyy/MM/dd",
        "type" : "date"
      }
    }
  }
}

Hiya

On Fri, 2011-08-12 at 20:55 -0700, Tom Le wrote:

Looks like auto type mapping is not working for date types in 0.17.5,
it shows up as "string":

I've opened an issue:

clint

Yea., thats a problem. Damn..., a 0.17.6 is on the way...

On Sat, Aug 13, 2011 at 11:22 AM, Clinton Gormley clint@traveljury.comwrote:

Hiya

On Fri, 2011-08-12 at 20:55 -0700, Tom Le wrote:

Looks like auto type mapping is not working for date types in 0.17.5,
it shows up as "string":

I've opened an issue:
Date detection for `YYYY/MM/dd` or `YYYY/MM/dd HH:mm:ss` without timezones now broken · Issue #1241 · elastic/elasticsearch · GitHub

clint