Dynamic templates ignore analyzers on keyword fields silently

[clintongormley]

The following:

PUT t
{
  "mappings": {
    "t": {
      "dynamic_templates": [
        {
          "strings": {
            "match_mapping_type": "string",
            "mapping": {
              "analyzer": "english",
              "type": "keyword"
            }
          }
        }
      ]
    }
  }
}

PUT t/t/1
{
  "foo": "bar"
}

creates a keyword field without an analyzer, which is good. However, I would have expected it to throw an exception about the presence of the analyzer setting.

[jpountz]

This is an old bug apparently: dynamic templates do not check for unknown parameters, they simply ignore them. While it could be easy to fix this, this would break lots of existing templates. For instance if you have a template that matches everything and adds store: true, then it would fail on all objects since objects do not support the store property.