We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In 0.90.6 and 0.90.5, default mappings will not be applied to newly created types if your cluster topology has separate master and data nodes.
Working case (all nodes are master/data eligible) with a two node cluster:
# create index curl -XPUT http://localhost:9200/test-index # create _default_ mapping curl -XPUT http://localhost:9200/test-index/_default_/_mapping -d'{"_default_": {"_timestamp": {"enabled": true}}}' # verify contents curl http://localhost:9200/test-index/_default_/_mapping # >> {"_default_":{"_timestamp":{"enabled":true},"properties":{}}} # add a new type curl -XPUT http://localhost:9200/test-index/new-mapping/_mapping -d'{"properties": {"foo": "string"}}' #verify contents have _default_ applied curl http://localhost:9200/test-index/new-mapping/_mapping # >> {"new-mapping":{"_timestamp":{"enabled":true},"properties":{}}}
Broken case (master/data nodes separate) with a two node cluster:
Set each node with appropriate settings:
# node1 node.master: true node.data: false # node2 node.master: false node.data: true
The same set of commands yield a mapping with defaults applied:
curl -XPUT http://localhost:9200/test-index curl -XPUT http://localhost:9200/test-index/_default_/_mapping -d'{"_default_": {"_timestamp": {"enabled": true}}}' curl http://localhost:9200/test-index/_default_/_mapping # >> {"_default_":{"_timestamp":{"enabled":true},"properties":{}}} curl -XPUT http://localhost:9200/test-index/new-mapping/_mapping -d'{"properties": {"foo": "string"}}' curl http://localhost:9200/test-index/new-mapping/_mapping # >> {"new-mapping":{"properties":{}}}
The text was updated successfully, but these errors were encountered:
_default_ mapping not applied when using separate master/data nodes
3f6e66b
fixes #4124
7fc4947
0e743ac
fixes elastic#4124
kimchy
No branches or pull requests
In 0.90.6 and 0.90.5, default mappings will not be applied to newly created types if your cluster topology has separate master and data nodes.
Working case (all nodes are master/data eligible) with a two node cluster:
Broken case (master/data nodes separate) with a two node cluster:
Set each node with appropriate settings:
The same set of commands yield a mapping with defaults applied:
The text was updated successfully, but these errors were encountered: