-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Only storing one mapping #35
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
Comments
Btw, it looks like the mapping is still enforced, you're just not merging the JSON metadata correctly |
I am not sure I understand. I indexed into type one, and indexed into type two, and then ran the _cluster/state and I do see the two mappings. By the way, the mappings returned were wrong in terms of JSON response, since I returned the same object name (mapping) for each one. I fixed it. Maybe that was the reason? |
yep, the old "json properties SHOULD..." issue - your commit fixed it. thanks |
No problem. I thought I went over all the places and fixed them, guess I missed this one. |
cool, I will close the issue then. |
Breaking changes in to EsExecutors was introduced in elasticsearch 0.90.4 Closes #35.
Adds node joining based on a simplified MasterService abstraction.
2.0 support
With this commit we measure raw event size and add it is a new field in the generated documents. Relates elastic#35
Hiya
Something weird is going on with put_mapping, eg:
or
or
Example below:
The text was updated successfully, but these errors were encountered: