Dynamic Mapping


(Sky Stebnicki) #1

Hi all, I'm new(er) to elasticsearch but pretty experienced with
Apache Solr. In Solr there is a configuration option in solr that
allows me to create dynamic mapping with the prefix or the postfix of
a field name. For instance, if I index a field called 'myvalie_i' then
I can tell solr to always treat that field as an integer because of
the "*_i" postfix.

Is there any way to do that in ElasticSearch?

Thanks so much!

Sky


(Nick Hoffman) #2

Hey there, Sky. Have a look at dynamic templates:
http://www.elasticsearch.org/guide/reference/mapping/root-object-type.html


(Sky Stebnicki) #3

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.elasticsearch.org/guide/reference/mapping/root-object-type...


(Shay Banon) #4

When you put mapping against an index, you can specify the mapping type to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman <n...@deadorange.com (http://deadorange.com)> wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.elasticsearch.org/guide/reference/mapping/root-object-type...


(Sky Stebnicki) #5

Thanks Shay!

On Feb 7, 3:48 am, Shay Banon kim...@gmail.com wrote:

When you put mapping against an index, you can specify the mapping type to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman <n...@deadorange.com (http://deadorange.com)> wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.elasticsearch.org/guide/reference/mapping/root-object-type...


(Sky Stebnicki) #6

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:
http://www.elasticsearch.org/guide/reference/mapping/root-object-type...


(Shay Banon) #7

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebnicki@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...


(Sky Stebnicki) #8

Alright, that sounds like what I am looking for, but I cannot get it to
work. I've tried and I'm missing something.

  1. Create /config/templates/template1.yml

template : "",
mappings :
default :
dynamic_templates :
templ_int :
match : "
_i"
mapping :
type : "integer"
index : "not_analyzed"
store : "yes"

I also tried
template_1 :
template : "",
mappings :
default :
dynamic_templates :
templ_int :
match : "
_i"
mapping :
type : "integer"
index : "not_analyzed"
store : "yes"

But neither of them are applying. http://localhost:9200/_all/_mapping
reveals:

{"test":{"customer":{"properties":{"owner_id_i":{"type":"date","format":"dateOptionalTime"}}}}}

After entering multiple items with fields that match *_i in the "test" index

And is there any reason I would not want to store int? I was just going off the mapping base types.

Thanks,

Sky

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebnicki@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebnicki@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebnicki@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...


(Radu Gheorghe) #9

AFAIK, if you put templates there, they should be in JSON, not YML:

Please note that the template is added when it matches an index. So I
couldn't see my configured template when I checked the cluster state,
as opposed to how I see them when I just put them via HTTP.

On Apr 13, 4:35 pm, Sky Stebnicki sky.stebni...@gmail.com wrote:

Alright, that sounds like what I am looking for, but I cannot get it to
work. I've tried and I'm missing something.

  1. Create /config/templates/template1.yml

template : "",
mappings :
default :
dynamic_templates :
templ_int :
match : "
_i"
mapping :
type : "integer"
index : "not_analyzed"
store : "yes"

I also tried
template_1 :
template : "",
mappings :
default :
dynamic_templates :
templ_int :
match : "
_i"
mapping :
type : "integer"
index : "not_analyzed"
store : "yes"

But neither of them are applying.http://localhost:9200/_all/_mapping
reveals:

{"test":{"customer":{"properties":{"owner_id_i":{"type":"date","format":"dateOptionalTime"}}}}}

After entering multiple items with fields that match *_i in the "test" index

And is there any reason I would not want to store int? I was just going off the mapping base types.

Thanks,

Sky

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebni...@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebni...@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to have the
int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki sky.stebni...@gmail.comwrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that possible?
For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping type
to be default, and it will apply to any mapping type in that index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**typehttp://www.elasticsearch.org/guide/reference/mapping/root-object-type
...


(Sky Stebnicki) #10

Hmm, the json document is not being applied either. However, I have decided
to just create the template though the API every time the index is created
and that appears to be working really well. Thanks for all your help, the
dynamic templates are exactly what I needed!

On Saturday, April 14, 2012 9:58:26 AM UTC-7, Radu Gheorghe wrote:

AFAIK, if you put templates there, they should be in JSON, not YML:
https://github.com/elasticsearch/elasticsearch/issues/1703

Please note that the template is added when it matches an index. So I
couldn't see my configured template when I checked the cluster state,
as opposed to how I see them when I just put them via HTTP.

On Apr 13, 4:35 pm, Sky Stebnicki sky.stebni...@gmail.com wrote:

Alright, that sounds like what I am looking for, but I cannot get it to
work. I've tried and I'm missing something.

  1. Create /config/templates/template1.yml

template : "",
mappings :
default :
dynamic_templates :
templ_int :
match : "
_i"
mapping :
type : "integer"
index : "not_analyzed"
store : "yes"

I also tried
template_1 :
template : "",
mappings :
default :
dynamic_templates :
templ_int :
match : "
_i"
mapping :
type : "integer"
index : "not_analyzed"
store : "yes"

But neither of them are applying.http://localhost:9200/_all/_mapping
reveals:

{"test":{"customer":{"properties":{"owner_id_i":{"type":"date","format":"dateOptionalTime"}}}}}

After entering multiple items with fields that match *_i in the "test"
index

And is there any reason I would not want to store int? I was just going
off the mapping base types.

Thanks,

Sky

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to
have the

int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki <
sky.stebni...@gmail.com>wrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that
possible?

For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping
type

to be default, and it will apply to any mapping type in that
index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**type<
http://www.elasticsearch.org/guide/reference/mapping/root-object-type>

...

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to
have the

int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki <
sky.stebni...@gmail.com>wrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that
possible?

For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping
type

to be default, and it will apply to any mapping type in that
index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**type<
http://www.elasticsearch.org/guide/reference/mapping/root-object-type>

...

On Friday, April 13, 2012 5:25:02 AM UTC-7, kimchy wrote:

Not in elasticsearch.yml, but you can create an index template
configuration, with a template matching *. Btw, why do you need to
have the

int stored?

On Thu, Apr 12, 2012 at 5:39 PM, Sky Stebnicki <
sky.stebni...@gmail.com>wrote:

Sorry to resurrect such an old thread, but I had one simple follow-up
question. If I wanted to set this in a configuration file is that
possible?

For example:

/config/elasticsearch.yml

mappings :
default :
dynamic_templates :
templ_int :
match : "*_i"
mapping :
type : "int"
index : "not_analyzed"
store : "yes"

Thanks again for your help!

Sky

On Tuesday, February 7, 2012 3:48:01 AM UTC-8, kimchy wrote:

When you put mapping against an index, you can specify the mapping
type

to be default, and it will apply to any mapping type in that
index.

On Tuesday, February 7, 2012 at 7:31 AM, SkyStebnicki wrote:

Thanks for taking the time to write. That is definitely looking like
what I will need. Do you know if there is any way to set the dynamic
mapping template for an entire index rather than for each type?

So I would basically just create a new template for each type right?
For example:

{
"customer" :
{
"dynamic_templates" : [
{
"template_int" : {
"match" : "_i",
"mapping" : {
"type" : "integer"
}
}
},
{
"template_str" : {
"match" : "
_s",
"mapping" : {
"type" : "string"
}
}
}
]
}
}

On Feb 2, 11:03 am, Nick Hoffman n...@deadorange.com wrote:

Hey there, Sky. Have a look at dynamic templates:http://www.**
elasticsearch.org/guide/**reference/mapping/root-object-**type<
http://www.elasticsearch.org/guide/reference/mapping/root-object-type>

...


(system) #11