Mapping templates for _types (not indices)

Hi, is it possible to create templates (using wildcards) for _type (not index) mappings?
I mean something like this:

...
"mappings" : {
"foo*" : { // this is a _type
"_source" : { "enabled" : false }
}
}
...

I know the default value, but I don't want to apply mappings to all types. Instead the mapping should only be applied to dynamically created foo* _types (e.g. fooBar1, fooBar2, ...) etc.

BTW: Is it problem to use 100-1000 different types in an index? I know that a _type has some overhead (mapping settings etc.), but apart from this: Do you expect any problems with this number of _types?

Thank you.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Why do you need so many different types if they all have the same mappings?

On Thursday, April 11, 2013 10:01:26 AM UTC-4, Mil Werns wrote:

Hi, is it possible to create templates (using wildcards) for _type (not index) mappings?
I mean something like this:

...
"mappings" : {
"foo*" : { // this is a _type
"_source" : { "enabled" : false }
}
}
...

I know the default value, but I don't want to apply mappings to all types. Instead the mapping should only be applied to dynamically created foo* _types (e.g. fooBar1, fooBar2, ...) etc.

BTW: Is it problem to use 100-1000 different types in an index? I know that a _type has some overhead (mapping settings etc.), but apart from this: Do you expect any problems with this number of _types?

Thank you.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Why do you need so many different types if they all have the same mappings?

I want to partition my data on a weekly basis: cw01, cw02, ...

On Thursday, April 11, 2013 10:01:26 AM UTC-4, Mil Werns wrote:

Hi, is it possible to create templates (using wildcards) for _type (not index) mappings?
I mean something like this:

...
"mappings" : {
"foo*" : { // this is a _type
"_source" : { "enabled" : false }
}
}
...

I know the default value, but I don't want to apply mappings to all types. Instead the mapping should only be applied to dynamically created foo* _types (e.g. fooBar1, fooBar2, ...) etc.

BTW: Is it problem to use 100-1000 different types in an index? I know that a _type has some overhead (mapping settings etc.), but apart from this: Do you expect any problems with this number of _types?

Thank you.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Better to do that using multiple indices, no?

On Sun, Apr 14, 2013 at 11:13 AM, Mil Werns milwerns@gmail.com wrote:

Why do you need so many different types if they all have the same mappings?

I want to partition my data on a weekly basis: cw01, cw02, ...

On Thursday, April 11, 2013 10:01:26 AM UTC-4, Mil Werns wrote:

Hi, is it possible to create templates (using wildcards) for _type (not index) mappings?
I mean something like this:

...
"mappings" : {
"foo*" : { // this is a _type
"_source" : { "enabled" : false }
}
}
...

I know the default value, but I don't want to apply mappings to all types. Instead the mapping should only be applied to dynamically created foo* _types (e.g. fooBar1, fooBar2, ...) etc.

BTW: Is it problem to use 100-1000 different types in an index? I know that a _type has some overhead (mapping settings etc.), but apart from this: Do you expect any problems with this number of _types?

Thank you.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

... or simply add a field that stores a week.

On Sunday, April 14, 2013 6:35:01 AM UTC-4, Clinton Gormley wrote:

Better to do that using multiple indices, no?

On Sun, Apr 14, 2013 at 11:13 AM, Mil Werns <milw...@gmail.com<javascript:>

wrote:

Why do you need so many different types if they all have the same

mappings?

I want to partition my data on a weekly basis: cw01, cw02, ...

On Thursday, April 11, 2013 10:01:26 AM UTC-4, Mil Werns wrote:

Hi, is it possible to create templates (using wildcards) for _type (not index) mappings?
I mean something like this:

...

"mappings" : {
"foo*" : { // this is a _type
"_source" : { "enabled" : false }
}
}
...

I know the default value, but I don't want to apply mappings to all types. Instead the mapping should only be applied to dynamically created foo* _types (e.g. fooBar1, fooBar2, ...) etc.

BTW: Is it problem to use 100-1000 different types in an index? I know that a _type has some overhead (mapping settings etc.), but apart from this: Do you expect any problems with this number of _types?

Thank you.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.