Cluster Block Exception - Elastic Search 7.4.2

Elastic Stack Elasticsearch
1

Elastic 7.4, The multiple types of support are deprecated !!

But it's not blocked as per the elastic documentation.

//
PUT twitter/user/kimchy
{
"name": "Shay Banon",
"user_name": "kimchy",
"email": "shay@kimchy.com"
}

it should create index with default mapping type.

now, try to create new type index with tweet as below syntax
//
PUT twitter/tweet/1
{
"user_name": "kimchy",
"tweeted_at": "2017-10-24T09:00:00Z",
"content": "Types are going away"
}

Elastic will give following error message
//
{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "Rejecting mapping update to [twitter] as the final mapping would have more than 1 type: [user, tweet]"
}
],
"type": "illegal_argument_exception",
"reason": "Rejecting mapping update to [twitter] as the final mapping would have more than 1 type: [user, tweet]"
},
"status": 400
}

and if you re-execute the same GET rest api and it does disable the index and give below error message
//
{
"error": {
"root_cause": [
{
"type": "cluster_block_exception",
"reason": "index [twitter] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"
}
],
"type": "cluster_block_exception",
"reason": "index [twitter] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"
},
"status": 403
}

Can you please provide some input here?

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.