Skip to content

add _meta for all mapping fields #5607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

kzwang
Copy link
Contributor

@kzwang kzwang commented Mar 30, 2014

add field level _meta support for all fields in mapping

closes #2857

@imotov imotov self-assigned this Apr 30, 2014
@imotov
Copy link
Contributor

imotov commented Apr 30, 2014

Hi @kzwang,

Thanks for the pull request. I see that it adds _meta tag not only to document fields but also to all metadata fields (such as _id, _parent, _analyzer, etc.). While I can clearly see the value for having _meta tag on the field level, I am not sure I like the idea of having it (and need to maintain it) for the metadata fields. Is there a particular reason you need it there?

Igor

@clintongormley
Copy link
Contributor

Hi @kzwang - I'd be interested in hearing the use case too.

I'm assuming that the intent is to use the _meta element for some object<->es mapper, and wondering if and why meta entries are necessary on the special fields.

@clintongormley
Copy link
Contributor

Closing.

@mindbits
Copy link

mindbits commented Feb 4, 2015

I think having _meta on a field level is a great way to avoid lookup tables and use cases would range from comments to access control list information etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow _meta in mappings on a field level
4 participants