Could mapping _meta be used for each property or entire mapping only?

Could _meta be only used on mapping level or could it be specified for
every property defined in the mapping as well?
I would really like to be able to annotate my properties for application
use (i.e. displayName, whether it should be used for faceting and which of
propertie's multifields should be used for that etc)

--
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.

Meta can only be applied to the root of the type mapping. You can use
comments in your mapping at any level but the comments on not returned
when performing a GET mapping so I am not sure how useful that will be
for you.

Thanks,
Matt Weber

On Mon, Apr 22, 2013 at 8:51 AM, AlexR roytmana@gmail.com wrote:

Could _meta be only used on mapping level or could it be specified for every
property defined in the mapping as well?
I would really like to be able to annotate my properties for application use
(i.e. displayName, whether it should be used for faceting and which of
propertie's multifields should be used for that etc)

--
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.

Thanks Matt.
Maintaining a large mappings file is pretty hard but maintaining (and
syncing) properties metadata outside of the mapping structure is a real
pain. I was hoping to use _meta tag for it.
I may have to use my own meta-model to generate mappings and other
artifacts from it but it will not be dramatically more concise than ES
mappings if I want to support all mapping options so I decided against it.
Now I guess I may just go with it. The biggest benefit (in addition to be
able to store my own metadata) would be ability to have certain transforms
such as chained multifield mapping or macros that could be expanded into ES
mapping file

On Monday, April 22, 2013 12:03:43 PM UTC-4, Matt Weber wrote:

Meta can only be applied to the root of the type mapping. You can use
comments in your mapping at any level but the comments on not returned
when performing a GET mapping so I am not sure how useful that will be
for you.

https://github.com/elasticsearch/elasticsearch/issues/1394

Thanks,
Matt Weber

On Mon, Apr 22, 2013 at 8:51 AM, AlexR <royt...@gmail.com <javascript:>>
wrote:

Could _meta be only used on mapping level or could it be specified for
every
property defined in the mapping as well?
I would really like to be able to annotate my properties for application
use
(i.e. displayName, whether it should be used for faceting and which of
propertie's multifields should be used for that etc)

--
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.