Elasticsearch 1.2.1 exception: Root type mapping not empty after parsing

Question

After updating to Elasticsearch 1.2.1 I keep getting the following exception on the following mapping:

{
    "tags": {
        "properties": {
            "tags": {
                "type": "string",
                "index": "not_analyzed"
            }
        }
    }
}

This is the exception:

Caused by: org.elasticsearch.index.mapper.MapperParsingException: Root type mapping not empty after parsing! Remaining fields: [tags : {properties={tags={index=not_analyzed, type=string}}}]
    at org.elasticsearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:265)
    at org.elasticsearch.index.mapper.DocumentMapperParser.parseCompressed(DocumentMapperParser.java:189)
    at org.elasticsearch.index.mapper.MapperService.parse(MapperService.java:387)
    at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:253)
    at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$2.execute(MetaDataCreateIndexService.java:363)

Why is that?

John Petrone · Accepted Answer · 2014-06-19 19:59:18Z

11

@Mark this appears to be a bug in 1.2.X. There have been multiple others that have reported similar issues, I'll link to the tickets below. Basically it appears that they tightened up on syntax for mappings in 1.2.X but they appear to have caused some problems with previously valid mappings. Yours is one example.

I'd suggest you open a bug report - more power in numbers. Happy to chime in saying "me too" if you open a ticket, as I've recreated the problem on 1.2.1 .

For now I've been able to the following to work which I believe gives you the same desired result:

curl -XPUT localhost:9200/yourindexname -d 
'{
   "mappings":
   {
    "tags":
      {
       "properties":
         {
          "tags":
            {
             "type":"string",
             "index":"not_analyzed"
            }
          }
        }
    }
}'

Tickets:

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

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

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

edited Jun 19, 2014 at 19:59

answered Jun 17, 2014 at 16:23

John Petrone

27.5k6 gold badges68 silver badges69 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Kartikeya Sinha Over a year ago

When I try what you have suggested, I get "{"error":"IndexAlreadyExistsException[[indexName] already exists]","status":400}". Any idea?

Anglepoise Over a year ago

@KartikeyaSinha you probably try to create a new index with an already existing name.

dieend · Accepted Answer · 2015-01-16 09:05:43Z

7

This will help you

you will get want you want to do

curl -XPUT localhost:9200/new_index -d '
{
  "mappings": { 
    "tags": {
      "properties": {
        "tags": { 
           "type":"string",
           "index":"not_analyzed"
        }
      }
    }
  }
}'

or you can also do this way

curl -XPUT localhost:9200/new_index/new_index_type/_mappings -d '
{
  "new_index_type": {
    "properties": {
      "tags": {
        "type": "string",
        "index": "not_analyzed"
      }
    }
  }
}'

edited Jan 16, 2015 at 9:05

dieend

2,3191 gold badge24 silver badges30 bronze badges

answered Jun 17, 2014 at 11:50

Akash Yadav

8717 silver badges11 bronze badges

Comments

c-toesca · Accepted Answer · 2015-07-11 17:21:01Z

1

I had the same problem because I had mappings with same type in the elastic config/mappings directory. Removing the mapping file solded my problem.

answered Jul 11, 2015 at 17:21

c-toesca

1,0171 gold badge12 silver badges15 bronze badges

1 Comment

CrazyPyro Over a year ago

This fixed it for me on 1.7 as well. I had only one mapping in the config as above, but I was also setting the same one explicitly in the template parameter of the elasticsearch output in my logstash config.

Collectives™ on Stack Overflow

Elasticsearch 1.2.1 exception: Root type mapping not empty after parsing

3 Answers 3

2 Comments

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related