Mapping for metadata in percolator queries

We want to store some meta data with the queries we register in a
percolator, and want to map these as not analyzed. It seems that creating
the mapping works:

curl -XPUT localhost:9200/_percolator/indexname/_mapping -d '{ ... }'

but after the first percolator query is registered in this percolator the
existing mapping is overwritten with the dynamic one, which causes all
extra fields to be analyzed. Is there a way to force these extra fields to
not be analyzed?

--

It seems the error is related to me not including the type when PUT-ing the
mapping:

curl -XPUT localhost:9200/_percolator/indexname/_mapping -d '{"properties":
{ ... }}'

is not OK, but

curl -XPUT localhost:9200/_percolator/indexname/_mapping -d '{"indexname":
{"properties": { ... }}}'

is.

On Friday, November 23, 2012 3:22:49 PM UTC+1, Christer wrote:

We want to store some meta data with the queries we register in a
percolator, and want to map these as not analyzed. It seems that creating
the mapping works:

curl -XPUT localhost:9200/_percolator/indexname/_mapping -d '{ ... }'

but after the first percolator query is registered in this percolator the
existing mapping is overwritten with the dynamic one, which causes all
extra fields to be analyzed. Is there a way to force these extra fields to
not be analyzed?

--